An audit that reads your site the way your users do.
Automated scanners see the markup. We also listen to it, tab through it, zoom it to 400%, and try to finish a purchase with the screen turned off. Then we tell you exactly what to fix first, and why.
Most websites fail in the same six ways. Yours probably fails in a seventh.
The 2026 WebAIM Million found that 95.9% of the top one million home pages had detectable WCAG failures, averaging 56.1 errors each. Low-contrast text, missing alternative text, and unlabeled form fields lead the list every year, and a scanner will find most of them in seconds.
The barriers that actually stop people are usually somewhere a scanner can't follow: a date picker that traps keyboard focus, a cart drawer that never announces itself, an error message that appears visually but says nothing to a screen reader. Those failures live in journeys, not pages. So that is how we test.
How the audit runs
A typical WCAG 2.2 AA audit takes three to four weeks from kickoff to readout.
Scope the sample
We map your templates and pick a representative sample: every unique layout, every interactive component, and the two or three journeys that matter most, such as checkout, account creation, or a patient intake form.
Automated sweep
We crawl the sample with axe-core and our own rules to catch the mechanical failures quickly, so the manual time goes where judgment is needed.
Manual and assistive-technology testing
An analyst works through each template against all 55 WCAG 2.2 A and AA success criteria using a keyboard alone, 200% and 400% zoom, text-spacing overrides, and screen readers: NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android.
Rank and write up
Every finding is tied to a success criterion, a component, and a fix. We rank by who is blocked and how often they hit it, not by how alarming the rule name sounds.
Readout and retest
We walk your team through the findings, answer the hard questions, and retest fixed issues within 90 days at no extra cost.
What you receive
- An executive summary in plain English, written for the people who approve budgets
- A findings register in a spreadsheet or your issue tracker, with severity, location, success criterion, and screenshots
- Code-level remediation guidance for every issue, with an accessible pattern your developers can copy
- A component view showing which shared components cause the most failures, so one fix clears many pages
- A recorded screen-reader walkthrough of your critical journey, before fixes
- A retest of fixed issues within 90 days, documented in the same register
Scanner report or audit?
An automated scan
- Checks the rules a machine can decide
- Finds missing labels, contrast, and empty links
- Can't tell whether alt text is accurate or a focus order makes sense
- Produces long lists sorted by rule, not by impact
A Baclion audit
- Covers all 55 A and AA criteria in WCAG 2.2
- Tests journeys end to end with four screen readers
- Judges meaning: names, order, announcements, and errors
- Ranks fixes by who is blocked, and groups them by component
Two ways to start
Rapid Accessibility Snapshot
Starting at
$1,450
Up to 8 key templates, automated and manual checks, a ranked findings list, and a 60-minute readout.
Request a quoteWCAG 2.2 AA Audit
Starting at
$4,800
Up to 15 unique templates and 2 critical journeys, tested with keyboard, zoom, and four screen readers.
Request a quoteLarger platforms, native apps, and multi-site estates are scoped individually. Every engagement starts with a free 30-minute scoping call.
Questions we hear before every audit
Do you test against WCAG 2.1 or 2.2?
Both. WCAG 2.2 is the current W3C Recommendation and includes every 2.1 criterion except 4.1.1 Parsing, which was removed. The Department of Justice rule for state and local governments references WCAG 2.1 AA, so for public entities we report against 2.1 and flag the six newer 2.2 A and AA criteria separately.
Will an audit make my website compliant with the ADA?
An audit tells you where you stand and what to fix; the fixes are what change your position. We report conformance with WCAG, which is the technical standard courts and regulators reference. Whether a site meets a legal obligation is a question for your attorney, and we are glad to work alongside them.
Do you need access to our code?
No. We test the rendered site, the same way your users experience it. Read access to a staging environment helps us test logged-in areas and unreleased features without touching production data.
How is this different from the free scans online?
Free scanners are useful, and we use them too. They can only evaluate the criteria a machine can decide, so they miss barriers like a confusing focus order, inaccurate alt text, or an error message that never reaches a screen reader. An audit adds the human judgment.
Can you fix what you find?
Yes. Our remediation team ships fixes as reviewed pull requests or theme changes, and we can work alongside your developers if you would rather fix in-house.
Keep reading
Tell us what your website needs to do.
Send a link and a sentence about your deadline. You will hear back from a person within one business day, usually with a short list of questions and a proposed scope.