June 23, 2026
Most business owners hear “ADA compliance,” picture a quick scan and a green checkmark, and move on. Then a demand letter shows up. The first question the other side’s attorney asks is simple: did you already know your site had accessibility problems? If you ran an audit and did nothing with it, the honest answer is yes — and now there’s a document that proves it.
Here’s the part most providers skip: an audit that lists problems without a plan to fix them isn’t a compliance win. It’s evidence. Before you spend a dollar on an audit for your website, the real question to answer is what happens after the report lands. Who fixes the issues, in what order, and by when? Get that wrong and you’ve paid to document your own liability.
This guide breaks down what a proper accessibility audit actually covers, what WCAG 2.1 AA means without the legal fog, and how to make sure the work leaves your site genuinely better — not just better documented.
What WCAG 2.1 AA Actually Means
If you’re going to invest in accessibility, you should understand the standard you’re being measured against — without needing a law degree to get there.
WCAG stands for the Web Content Accessibility Guidelines. Version 2.1 at the AA level is the benchmark that accessibility laws in the US, UK, EU, and Canada point to when deciding whether a website is accessible. When a court or regulator evaluates a complaint, this is the measuring stick they reach for.
It’s a Standard, Not a Certificate
There’s a common misconception worth clearing up early: there is no official “WCAG 2.1 AA certificate.” No governing body hands out a badge, and there’s no annual renewal to register for. It’s a set of criteria your site either meets or it doesn’t. Meeting them means a person using assistive technology can perceive, navigate, and use your content without running into barriers a non-disabled visitor would never notice.
The Four Principles Behind Every Requirement
Every WCAG rule traces back to one of four ideas. Frame it this way and the standard stops feeling like an arbitrary hurdle:
- Perceivable — people can’t use what they can’t detect (think alt text on images, captions on video)
- Operable — every function has to work without a mouse, using a keyboard alone
- Understandable — content and behavior should be predictable, not surprising
- Robust — built to work with the screen readers and assistive tools people actually use today
Alt text, keyboard navigation, color contrast, clear form labels — every specific requirement is just one of those four principles in action.
What a Real Accessibility Audit Covers
This is where a lot of “audits” quietly underdeliver, because the word can mean wildly different things. A surface scan and a real audit produce very different findings — and only one of them holds up when it matters.
A complete audit has two layers: automated testing and manual testing. Most cheap audits stop at the first one.
What Automated Tools Catch
Automated scanners are excellent at flagging structural issues: missing alt attributes, poor color contrast, form fields with no labels, pages with no declared language. These are real problems that affect real users, and the tools find them reliably.
The catch is coverage. Industry research consistently shows automated scanners catch only about 30–40% of the accessibility issues on a given site. That isn’t a knock on the tools — it’s the nature of what software can check versus what takes human judgment.
What Only Manual Testing Finds
Manual testing means a real person navigating your site the way someone with a disability would — using screen readers like NVDA, JAWS, or VoiceOver, getting through it with the keyboard alone, and testing zoom and magnification. This is how you learn whether your site actually works, not just whether it passes a checklist. Questions a scanner simply can’t answer include:
- Does the screen reader read elements in an order that makes sense?
- Can a keyboard-only user fill out your contact form without getting trapped?
- Do your error messages explain what went wrong in a way that’s actually helpful?
Why Custom Features Need Their Own Testing
Standard HTML elements — buttons, links, native form fields — come with accessibility behavior that browsers and screen readers already understand. Custom-built features don’t inherit any of that for free. A custom dropdown, a popup, a date picker, a slider: each one has to be deliberately built with the right keyboard controls, focus handling, and ARIA attributes to work for everyone. If your site has a lot of custom interactive pieces, a real audit tests each of them by hand against the WAI-ARIA Authoring Practices. There’s no automated rule that can tell you whether your bespoke menu works for a screen reader user.
Why the Report Alone Won’t Protect You
This is the conversation that protects you, and most providers have it after the audit — which is too late.
An audit report is a prioritized list of problems. It tells you what’s broken and how badly. It doesn’t fix anything, doesn’t assign anyone to fix it, and doesn’t tell you how long it’ll take. That’s the work that comes next, and if nobody has agreed who’s doing it, the report just sits in a folder.
A business that receives a report full of documented failures and acts on none of it is in a worse legal position than before the audit existed. You now have written proof you knew. That’s exactly the document a plaintiff’s attorney wants to find. This is why fixing the issues — remediation — has to be part of the plan from day one, not an optional add-on once the PDF is delivered.
Scope the Fix Before You Run the Audit
Getting this right upfront is what separates a complete accessibility service from an audit-and-walk-away approach. Here’s how we work through it before any testing starts.
Decide Who Owns the Fixes
The arrangement varies by project, and any of these can work as long as it’s agreed on before the audit begins:
- We handle remediation directly, with development access to your site
- Your internal team takes the report and works through it
- A third-party developer owns the codebase and gets looped in from the start
Handing a detailed report to a business with no developer and no budget for fixes doesn’t move you closer to compliance. It hands you a documented liability with no way forward.
Fix What Matters Most First
Not every issue carries the same weight. Smart remediation triages by two things: how severe the issue is under WCAG, and how much it actually affects people trying to do something real on your site. The order generally looks like this:
- Critical journeys first — checkout, account creation, contact and lead forms
- High-severity issues on your most-visited pages
- Lower-impact issues in later passes
That way you have a defensible position early, and progress is visible from the start instead of all-or-nothing at the end.
Accessibility Isn’t “Set It and Forget It”
Here’s the part that catches most businesses off guard. Every time you publish a blog post, launch a promotion, or update a plugin, accessibility can quietly break again. A new image with no alt text. A banner built outside your normal templates. A plugin update that changes how a popup handles keyboard focus. None of it takes carelessness — it just takes a site that keeps moving.
Keeping a site accessible is a mix of process and tooling:
- Automated checks built into your workflow to catch structural issues before they go live
- Simple editorial guidelines for whoever updates the site — how to write alt text, how to structure headings, what makes a link label useful
- Periodic manual testing, quarterly for most sites, to catch what automation misses and confirm new features hold up
The Bottom Line on Accessibility Audits
An accessibility audit is a starting line, not a finish line. It’s a thorough look at what’s broken and how badly — and on its own, that’s all it is. The businesses that come out of this in genuinely better shape are the ones whose partner helped them understand the findings, agreed on who was fixing what, and put a process in place to keep the site accessible as it kept growing.
That’s a very different thing than sending a PDF and moving on. It’s also far more defensible — for your business and for the people trying to use your site.
Ready to find out where your website stands? Contact Sidekick Digital for a free accessibility review and a clear, prioritized plan to get — and stay — compliant. As part of our Compliance Assurance service, we handle the audit, the fixes, and the ongoing upkeep, so you’re protected without the guesswork.
