Services · Audit
Accessibility audit
A WCAG 2.2 audit of your website or app, with every issue located, explained and paired with a fix.
Automated scanners catch only part of what blocks disabled users. We combine scans with manual testing: keyboard-only navigation, screen readers such as NVDA, VoiceOver and TalkBack, zoom to 400 percent, colour contrast and form errors. Each issue is mapped to a WCAG 2.2 success criterion, shown with a screenshot and given a concrete fix your developers can apply.
What you get
- An agreed sample of pages and user journeys that covers every template
- An issue register mapped to WCAG 2.2 success criteria at levels A and AA
- Screenshots, code locations and a recommended fix for every issue
- Results of keyboard, screen reader, zoom and reflow testing per journey
- Issues prioritised by their impact on users and how many pages they affect
- A retest of fixed issues and an updated register showing what now passes
How it works
- 01
Sample
We pick representative pages and complete journeys, such as sign-up, search and checkout, to cover every template.
- 02
Scan
Automated tools such as axe check every sampled page for the issues machines can detect reliably.
- 03
Test
Testers use keyboard only, screen readers, zoom and contrast tools to find what scanners cannot.
- 04
Report
Every issue is logged against its criterion with a fix, and we retest once your team has made changes.
Scope it now.
Answer a few questions and we prepare the email for you. Nothing is sent until you press send in your own email app.
Prefer to write freely? hello@clockborn.com
Questions
Can an automated scan replace this audit?
No. Scanners reliably find issues like missing alt text and low contrast, but cannot judge whether alt text is meaningful, whether focus order makes sense or whether a screen reader user can finish checkout. Those need people.
What changed in WCAG 2.2?
It added criteria including focus that is not hidden behind other content, a minimum target size for controls, alternatives to dragging, consistent help, no forced re-entry of information and sign-in that does not depend on memory or puzzle tests.
Will you certify our site as accessible?
No one can certify a whole site permanently. We report how the tested sample conforms on the test date and can help you write an accessibility statement. New content and releases need their own checks.