Website accessibility readiness
Make critical website tasks usable before the deadline.
Evolved Designs helps public entities and organizations turn accessibility requirements into representative task paths, a prioritized remediation backlog, responsible owners, and evidence a team can verify.
Prepared and reviewed by Evolved Designs, the organization responsible for this implementation-readiness resource.
This page is implementation guidance, not legal advice or a compliance certification. Confirm legal obligations, exceptions, dates, and the applicable standard with qualified counsel.
The current public-sector target
Plan around people, tasks, and repeatable evidence.
The U.S. Department of Justice’s current Title II guidance identifies WCAG 2.1 Level AA as the technical standard and, after the April 2026 interim rule, points covered entities to April 2027 or April 2028 dates depending on entity size and type. A responsible implementation plan still has to connect the standard to the services people actually use.
Inventory complete journeys
Map the pages, forms, documents, authentication steps, payments, maps, media, and third-party tools behind tasks such as applying, paying, registering, reporting, or requesting help.
Test beyond a scan
Use automated checks as one input, then verify keyboard operation, focus order, headings, labels, instructions, errors, zoom, contrast, alternatives, and representative assistive-technology paths.
Assign fixes and owners
Separate template, component, content, document, vendor, and policy work so every barrier has a responsible owner, acceptance check, and safe release path.
Preserve the result
Retest representative journeys, document the evidence, teach content owners, and add release checks so accessibility does not disappear with the next update.
Acceptance evidence
Close the phase with checks a team can repeat.
Choose a small set of high-value journeys and define what must work before remediation begins. The result should be understandable to owners, procurement, developers, content teams, and the people who use the service.
- Task record: URL, user goal, components, documents, third parties, and owner.
- Barrier record: observed issue, affected interaction, severity, and reproducible evidence.
- Acceptance record: expected behavior, test method, result, date, and responsible reviewer.
- Operating record: content guidance, regression check, escalation path, and revisit trigger.
A practical acceptance answer
What should website accessibility acceptance evidence include?
For each representative task, record the expected behavior, test method, observed result, date, responsible reviewer, and the change that should trigger regression testing. Automated scans can support the record, but they do not replace keyboard, content, form, error, zoom, contrast, and representative assistive-technology checks.
Scan versus acceptance
Use automation to find conditions. Use task acceptance to prove a journey works.
Both methods are useful, but they answer different questions. The table can be scrolled horizontally with a keyboard on narrow screens.
| Decision area | Automated scan | Task-based acceptance |
|---|---|---|
| Method | Runs repeatable rules against rendered output. | Has a representative reviewer reproduce a complete task with keyboard, zoom, content, errors, and relevant assistive technology. |
| Coverage | Surfaces conditions the selected rules can detect. | Covers the end-to-end pages, forms, documents, and third-party steps behind a real service journey. |
| Evidence | Records the rule, issue, location, and repeatable scan result. | Records expected behavior, method, result, date, reviewer, and the change that triggers regression testing. |
| Best use | Provides a fast, repeatable input to prioritization and release checks. | Supports a decision about whether a priority task actually works for the people expected to use it. |
Private browser chooser
Choose the first readiness outcome.
Nothing is submitted or saved. Select the condition closest to the work in front of you.
Choose a starting condition to see the smallest responsible first phase.
Review the first phase with Evolved DesignsTask-based acceptance record
Turn findings into evidence another reviewer can repeat.
Use one representative journey to record the observed barrier, the observable outcome that must work, a combined tool-and-human test method, the responsible owner, and the change that should trigger regression testing. The builder stays in the browser and does not claim certification.
Planning a broader public-site project?
Connect accessibility to the full resident journey.
Use the municipal modernization framework when the work also includes content ownership, search, integrations, security, support, and procurement acceptance.