Government evaluation brief

Braillia Government Accessibility Capability Brief

A concise, printable overview of how Braillia helps state and local governments evaluate barriers, transform public information, support accessible delivery, and define a reviewable first implementation.

For: Government program, accessibility, digital, IT, security, legal, and procurement teams
Decision this supports: Should Braillia advance into a scoped Government accessibility evaluation?
Format: 8 minute review

The Government accessibility responsibility

A resident may begin on an agency website and continue into a document, form, payment service, records system, vendor portal, or individualized communication. Every step contributes to whether the public service is independently usable.

Current technical standard

The Department of Justice Title II web and mobile rule establishes WCAG 2.1 Level AA for covered state and local government web content and mobile apps, subject to the rule's defined exceptions and agency-specific legal analysis.

Current compliance dates

The current dates are April 26, 2027 for public entities with populations of 50,000 or more, and April 26, 2028 for smaller public entities and special district governments.

Continuing operating responsibility

Websites change, documents are published, forms are updated, systems generate new communications, and vendors release new experiences. Accessibility therefore belongs in the ongoing information workflow.

Where Braillia can enter

Websites and digital services

Identify rule-based barriers, affected experiences, user consequences, repair priorities, and validation evidence across an authorized scope.

Documents and public records

Reconstruct document structure and create appropriate outputs such as HTML, accessible PDF, EPUB, eBraille, and TXT for familiar systems and assistive technology.

Individual and time-sensitive communication

Transform eligible notices, bills, determinations, instructions, and deadline-bearing information on demand, with independent outputs and approved delivery options.

Government platforms and vendors

Define a source-specific implementation around the existing system of record when a civic platform, case system, permitting tool, billing system, records product, or provider controls part of the public experience.

What distinguishes the evaluation

The resident outcome and blocked action are defined before selecting technology
Website findings connect technical requirements to navigation, understanding, and action
Document work can produce structured information for more than one accessible destination
Current information can be improved while eligible older information is transformed when needed
Agency-controlled and vendor-controlled responsibilities are separated and assigned
The proposed workflow includes evidence, known limitations, and acceptance criteria

Information to request during evaluation

A demonstration using synthetic or approved representative information
The accessibility methodology and role of automated and human review
Expected source types, accessible outputs, delivery paths, and known exclusions
Security, privacy, identity, access, data movement, retention, and audit boundaries
Agency, Braillia, vendor, and shared implementation responsibilities
Acceptance evidence tied to what the resident must receive, navigate, understand, and complete
Commercial scope, volume assumptions, service level, support, and change conditions

A practical first workstream

Public-service workflow: Space for customer-provided information
Responsible department and executive sponsor: Space for customer-provided information
Affected residents and required action: Space for customer-provided information
Agency-controlled systems and information: Space for customer-provided information
Vendor-controlled systems and responsible provider: Space for customer-provided information
Website, document, form, notice, or communication in scope: Space for customer-provided information
Required accessible outputs and delivery path: Space for customer-provided information
Security, legal, accessibility, and procurement reviewers: Space for customer-provided information
Evidence required for acceptance: Space for customer-provided information
Decision required after evaluation: Space for customer-provided information