An audit
A sample of key templates and user journeys, tested with keyboard, screen reader and zoom. You get a prioritised issue list, reproduction steps and a remediation estimate.
Accessibility
Around 95% of the top million home pages still have detectable WCAG failures. Most of them are fixable in a day. We audit against WCAG 2.2 AA principles, reproduce each issue, and order the fixes by who they affect.
Accessibility is not a separate project bolted onto a finished site. It is the consequence of ordinary engineering decisions: using real headings, labelling form fields, keeping contrast above a threshold, making sure a keyboard can reach everything, and not shipping a custom control that only works with a mouse.
We audit against WCAG 2.2 AA principles and report in plain English. Each issue is reproduced with the page, the element and the assistive technology or input method affected. We do not claim a site is “fully compliant” — that requires a formal conformance evaluation, and any agency claiming it without one is selling confidence rather than evidence.
Offer
A sample of key templates and user journeys, tested with keyboard, screen reader and zoom. You get a prioritised issue list, reproduction steps and a remediation estimate.
We fix the issues in your existing codebase, starting with the ones that block a task — forms, navigation, checkout, booking — rather than the cosmetic ones.
New sites are built to WCAG 2.2 AA principles from the first commit: semantic HTML, visible focus, reduced-motion support, labelled controls, and automated checks in the build.
Principles
| Principle | What it means in practice | Common failure |
|---|---|---|
| Perceivable | Text alternatives, captions, sufficient contrast, content that works at 200% zoom | Grey text on a dark background; images with no alt text |
| Operable | Everything reachable and usable by keyboard, no traps, enough time | A menu that only opens on hover; a custom dropdown with no focus state |
| Understandable | Clear labels, consistent navigation, errors explained | A form that says “invalid input” without saying which field or why |
| Robust | Valid, semantic markup that assistive technology can parse | Divs pretending to be buttons; duplicate IDs; broken ARIA |
Honesty
Questions
Public sector sites have specific regulations. Private businesses have duties under the Equality Act not to discriminate, and the practical expectation is reasonable adjustment. The safest position is a site that works for disabled users, not a legal argument after a complaint.
A five-page marketing site is typically two to three days. A booking journey or an ecommerce checkout takes longer because there are more states to test.
No. Contrast, focus states and larger tap targets can be designed well. The constraint is real, but it produces clearer interfaces rather than uglier ones.
Yes. We have no interest in finding work for ourselves; if the issues are small, we will tell you and give you the list to take to your developer.
Tell us what you are trying to achieve. We will tell you honestly whether we can help, what it would take, and roughly what it would cost — before anyone signs anything.