What the audit covers
Two dimensions, assessed together because a keyboard user and a phone user often trip on the same broken component:
- Accessibility, against WCAG 2.1 and 2.2 at level AA: an automated scan first, then a manual pass — keyboard-only navigation, screen-reader traversal, focus order, color contrast in context rather than in isolation.
- Compatibility, across the browsers, devices and orientations your actual traffic uses — not an assumed matrix. Desktop, tablet and mobile, portrait and landscape: a layout that holds at 1024px wide can still break at 1024px on a tablet turned sideways, and that gap only shows up when someone measures it.
Why an automated scanner is not enough
A scanner such as axe or Lighthouse catches missing alt text, insufficient contrast, and malformed markup reliably and fast. What it structurally cannot tell you: whether a screen-reader user can actually complete your checkout, whether a modal traps keyboard focus with no way out, or whether a "Skip to content" link goes anywhere real.
Automated tools flag roughly a third of real accessibility issues. The rest require a person driving the product without a mouse. We run both passes, and we say which finding came from which — so you know what a re-scan will catch and what it will not.
What you get
A written report, findings sorted by severity — blocking, degrading, cosmetic — not by the order the scanner happened to output them. Each finding is reproducible: exact steps, the WCAG success criterion it fails, and which viewport or assistive technology it was caught on.
Each finding also carries a rough remediation-effort estimate, so triage is possible on day one instead of after a second meeting to size the backlog.
How it runs
The scoping session is free and lasts an hour: what prompted the audit, which flows matter most, and whether a legal deadline (ADA, Section 508, the European Accessibility Act) is driving the timeline.
The audit runs the automated pass first, then the manual pass across the breakpoints and assistive technologies agreed in scoping. A few days for a focused flow, up to two weeks for a full product, depending on surface.
What this is not
We are not a law firm. We tell you, with evidence, where the product fails a WCAG success criterion and what it would take to fix it — we do not issue a legal compliance certificate, and anyone who does without a lawyer in the room should be treated with suspicion.
For reference: this site is itself built and continuously checked against WCAG 2.1/2.2 AA, automated and manual — see our own accessibility statement. We hold our own work to the standard we audit yours against.
Before and after
If accessibility and compatibility are one symptom among several — flaky releases, no test strategy, unclear ownership — the broader quality audit is the better starting point. If you already know the product needs systematic testing across devices going forward, not just once, that becomes a test strategy question.