Skip to content

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.

The layers you can't see

Scroll to lift the visible form off the layers a keyboard or screen-reader user meets: contrast, semantics, focus order and target size.

AAcme✕

Create your account

Email
Password

At least 8 characters, one number.

Email me updates
→
15.8:13.1:1 placeholder2.3:1
img · no altdiv · not a headingedit text · no labeledit text · no labelbutton · no name
16 px16 px
  1. What a mouse user sees

    A tidy sign-up form. Nothing looks wrong, which is why these problems ship.

  2. Contrast

    Helper text measures 2.3:1 against its background. WCAG 2.2 AA asks for 4.5:1.

  3. Semantics

    What a screen reader hears: “Edit text. Edit text. Button.” No labels, and the submit button has no name.

  4. Focus order

    Tab goes from Email straight to the submit button, then back up to Password. The close icon never gets focus.

  5. Target size

    The checkbox and the close icon are 16 px. WCAG 2.2 asks for at least 24 px.

What we check in an accessibility audit

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

  1. 01

    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.

  2. 02

    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.

  3. 03

    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

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.

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.

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.

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.

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.