Capabilities · Accessibility
Find the barriers. Give your team a way to fix them.
For teams responsible for public information and services: an accessibility assessment that names the affected journey, shows the evidence, and explains how a fix will be verified.
WCAG 2.1.1 · A
The original control
<div onclick="submitForm()">Register</div>A clickable element without native button behavior can leave keyboard users unable to submit. This original is shown as code.
Interactive sample
Research briefing
Try the corrected form using only your keyboard.
Use Tab to move, then Enter to submit.
View the finding & verification steps
WCAG 2.1.1 Keyboard, Level A. Verify the complete form journey, errors, focus, and confirmation. Record the tested environments.
<button type="submit">Register</button>- Automated + manual
- Complementary checks
- User journeys
- Test the complete task
- Retesting
- Document the correction
An expert assessment is a separately scoped, paid engagement. The free public audit is an automated first pass and does not include a manual review.
Engagement details
Agree what is being tested.
The assessment
Pages and complete journeys
Identify representative templates and important tasks such as registering, searching, or requesting a service. State how authenticated areas, documents, media, and third-party tools are covered.
Automated and manual checks
Use automated checks alongside keyboard, focus, screen-reader, form, and content review. Record the testing environments. An automated score, including 100, does not establish conformance.
A report your team can use
Receive affected locations, user impact, relevant criteria, reproduction steps, priorities, and recommended fixes. Coverage and limitations are stated with the findings.
Verification after remediation
Have your team or vendor make the changes, or request a fixed remediation quote. Agree retest coverage. Ongoing automated monitoring can catch some regressions; manual verification remains necessary.
From assessment to verified change.
- Scope
Name the requirement
Bring the applicable contract or organizational standard, priority journeys, and known complaints. Agree the target, sample, deliverables, and fee.
- Assess
Explain the evidence
Review findings with the people responsible for the site. Separate shared template defects, content work, and third-party dependencies so responsibility is clear.
- Retest
Close findings with evidence
Verify agreed changes in the relevant journeys and document remaining limitations. Keep the report useful as the site and its content change.
WCAG, Title II, and Section 508 have distinct requirements.
State and local public entities
The DOJ’s Title II web rule specifies WCAG 2.1 AA. Compliance dates are April 26, 2027 for entities with populations of 50,000 or more, and April 26, 2028 for smaller entities and special district governments.
Read DOJ’s current guidanceFederal Section 508
The Revised 508 Standards incorporate WCAG 2.0 Level A and AA and contain additional ICT requirements. A contract may specify further requirements, including a later WCAG version. We agree the applicable scope before testing.
Read the U.S. Access Board standardsStart with the journey your visitors need to complete.
Bring the requirement and the site. We will discuss assessment coverage, responsibilities, and what your team needs from the findings.