WCAG 2.x AA

Web application audit and remediation

Automated scanners catch a minority of accessibility barriers — the ones expressible as a rule about markup. The rest need a person operating the interface the way an assistive-technology user would.

What we test

Every applicable Level A and AA success criterion in WCAG 2.1 and 2.2, including the criteria added in 2.2: focus appearance and focus not obscured, target size, dragging alternatives, consistent help, redundant entry and accessible authentication.

Testing is manual and assistive-technology led. Keyboard-only traversal, screen reader passes, 200% text resize, 400% reflow at 320 pixels, contrast measurement, and behaviour under reduced-motion and high-contrast settings. Automated tooling is used to sweep for the mechanical issues, not to produce the report.

How findings are written

Each finding names the success criterion, the element, the assistive technology that exposed it, the user impact, and what specifically to change. Issues are ranked so a team with limited sprint capacity knows what to fix first — barriers that block a task entirely come before those that make it awkward.

Where a fix has design consequences, we say so rather than pretending it is a one-line change.

Remediation and re-test

We can hand findings to your engineers, or work alongside them to implement the changes. Either way the engagement ends with a re-test that confirms each issue is genuinely resolved rather than closed on assertion.

Send us a title and a deadline

Tell us the format you have and the format you need. We will tell you plainly whether the source converts cleanly, and what it takes.

Open the contact form