Accessibility audit (WCAG 2.2 AA)
A free first-pass review of your site or product against WCAG 2.2 AA — the keyboard, screen-reader, contrast and structural issues most likely to shut real people out. Delivered as a PDF report and walked through on a 30-minute call, no obligation.
The EU's Accessibility Act has applied since 28 June 2025, raising accessibility from a design preference to a requirement for many EU-facing products. We're not in a position to tell you whether or how it applies to your product — that's a question for your own legal counsel — but if WCAG 2.2 AA has become something you need to act on, this review is where to start.
Book your free accessibility auditWhat we check in an accessibility audit
Keyboard operability & focus order
Whether every interactive element — links, buttons, form controls, custom widgets — can be reached and operated using only a keyboard, in an order that follows the page's visual and logical structure, with no keyboard trap that leaves focus stuck inside a menu, carousel or modal.
Visible focus indicator
Whether a keyboard user can actually see which element is focused — an indicator that's present and contrasts clearly against whatever it lands on — rather than one suppressed entirely or left too faint to register against the surface behind it.
Screen-reader semantics & landmarks
Whether heading structure, landmarks and semantic HTML actually describe the page — so a screen-reader user can jump between sections and understand what each one is — checked by operating the page with a screen reader running, not by scanning the markup alone.
Form labels & error association
Whether every field has a label a screen reader will actually announce, and whether an error is tied to its specific field programmatically — not just a red border or a summary message a screen-reader user has no way to connect back to the field it's about.
Colour contrast & colour-only meaning
Whether text and interface components meet WCAG 2.2 AA's contrast minimums against the background they actually sit on, and whether any state — an error, a selection, an online indicator — is conveyed by colour alone rather than paired with an icon, text or pattern that doesn't depend on colour vision.
Need broader colour and design-system consistency checked too? See our UI audit
Motion & reduced-motion preferences
Whether autoplaying carousels, parallax effects and animated transitions respect a visitor's operating-system preference for reduced motion, and whether anything on the page flashes or moves in a way that risks a vestibular or seizure reaction.
Captions & media alternatives
Whether video carries accurate captions and audio-only content has a text alternative, and whether that alternative actually matches what's being said rather than an uncorrected auto-generated transcript.
Target size
Whether interactive targets — buttons, links, toggles — are large enough and spaced far enough apart to hit reliably, on any pointer or touch input, rather than crowded together in a way that turns a tap into a guess.
What you actually get
You get a PDF report of your own to keep, that walks through what we found against WCAG 2.2 AA — the specific keyboard, screen-reader, contrast and structural issues we turned up, with the fix we'd recommend for each one. It’s built to stand on its own: the report makes sense without us in the room. It's a first-pass review, not a full WCAG 2.2 AA conformance audit: the exhaustive, criterion-by-criterion testing across assistive technology that a genuine conformance evaluation takes is days of dedicated work, not something a free, 1-business-day review can be — it's the natural next step once this first pass shows you where the gaps are.
How it works
Book a slot, send your site or app
Share a link to what you'd like reviewed — a live site, staging build, or app — plus which pages or flows matter most, especially anything gated behind a login where accessibility issues tend to hide.
We review it
This first pass checks it against WCAG 2.2 AA — keyboard access, screen-reader behaviour, contrast, and the rest — combining automated checks with a manual pass, since most of what WCAG cares about can't be caught by a scanner alone. Ready within 1 business day.
You get the report
We walk you through the findings on the call, page by page, and you keep the PDF — free, with no obligation to hire us for anything else.
Auditing something other than accessibility?
This page covers accessibility and WCAG 2.2 AA specifically. If it's your website's navigation, forms or checkout you want reviewed, our website UX audit covers that instead; for a native iOS or Android app, our mobile app UX audit covers platform-specific behaviour and onboarding; and if visual consistency across your design system is the concern rather than accessibility, see our UI audit. For the general rundown of what any of these audits cover, start with our UX audit services page, or browse example audit findings to see the kind of issues we flag in practice.
What it costs
The initial accessibility review is free. A full WCAG 2.2 AA conformance audit is a separate engagement, scoped once we know what the first pass finds. If you'd like our team to help implement the fixes, that follow-on work is scoped and quoted separately, based on what you need.
Frequently asked questions
Does a clean report mean we're compliant with the European Accessibility Act?
No. Whether a product is compliant under the Act is a legal question, shaped by things a technical review can't settle on its own, and it's not a determination we're in a position to make. What this audit does is tell you, in concrete terms, where your site or product stands against WCAG 2.2 AA; whether and how the Act applies to you is a question for your own legal counsel.
Does fixing one issue you flag tend to surface others behind it?
Often, yes. Accessibility issues frequently stack — widening a touch target can expose a spacing problem with its neighbour, and fixing a missing form label can reveal that the field next to it never had one either. We call out where that's likely in the report, so a fix doesn't just trade one problem for another.
Our product is a single-page app that updates content without a page reload — does that change what you check?
Yes. Client-side route changes and dynamic content updates need their own accessibility handling — moving focus when a new view loads, announcing updates to assistive technology — that a traditional multi-page site never has to think about, and we check for it specifically on JavaScript-heavy products.
Can you review a design file, or does it need to be a working build?
A Figma file lets us catch some issues early — contrast, type size, layout. Others, like keyboard operability, focus order, and what a screen reader actually announces, only exist once there's real markup and behaviour to test, so a working build gets you the fuller picture.
We already ran an automated accessibility scanner — is this audit redundant?
Not on its own. Automated scanners are good at catching things like missing alt text or insufficient contrast, but a lot of what WCAG cares about — whether a status update gets announced without a page reload, whether a custom dropdown communicates that it's open, whether the reading order a screen reader follows actually matches what's on screen — only shows up when a person operates the page directly. That's the gap this review is built to close.
Ready for a free, no-obligation look at your site's accessibility?
Book a slot and send your site or app. We’ll review keyboard, screen-reader, contrast and focus issues before we meet, then walk you through the PDF report — completely free.
Book your free accessibility audit