Accessibility audits + fixes to hit WCAG 2.1 AA.
Real accessibility work — not "install this overlay widget and hope no one sues you."
Fifteen percent of people have a disability that affects how they use the web, ADA lawsuits over inaccessible sites are up sharply, and the EU now mandates accessibility for many businesses. Real accessibility work makes your site usable by everyone — and it's nothing like the overlay-widget scam.
Why accessibility matters beyond compliance
15% of the world has some form of disability that affects how they use the web. Accessible sites are usable by everyone — screen readers, keyboard-only users, low-vision users, people on slow connections, people on tiny mobile screens, older users. And yes: US ADA lawsuits against inaccessible business websites are up 300% in 5 years. EU EAA requires accessibility for many B2C sites by 2025.
Why overlay widgets are a scam
AccessiBe, UserWay, Equal Web, "add this line of JS and you're WCAG compliant." Every legitimate accessibility auditor and disability advocacy group has publicly denounced these tools. They don't make sites accessible — they add fake toolbars that mostly break the sites for actual screen-reader users. And they don't protect against lawsuits (courts have ruled overlay-equipped sites still non-compliant). Real accessibility takes real work.
What real accessibility work looks like
Automated scan (Axe, WAVE, Lighthouse) for the low-hanging fruit — color contrast, missing alt text, missing labels. Manual audit with a screen reader (NVDA on Windows, VoiceOver on Mac/iOS). Keyboard-only navigation test. Focus management review. Form error announcement check. Live-region setup for dynamic content. Skip-link + semantic landmark check. Then we fix everything found.
Why overlay widgets are a scam
AccessiBe, UserWay, and the rest promise WCAG compliance from one line of JavaScript. Every serious accessibility auditor and disability advocacy group has publicly denounced them. They don't make sites accessible — they bolt on fake toolbars that often break the site for actual screen-reader users, and courts have ruled overlay-equipped sites still non-compliant. They're a false sense of safety, not a solution.
What real remediation looks like
An automated scan (Axe, WAVE, Lighthouse) for the obvious wins — contrast, missing alt text, missing labels. Then a manual audit with a real screen reader (NVDA, VoiceOver), keyboard-only navigation testing, focus-management review, form-error announcement checks, live-region setup for dynamic content, and semantic landmark checks. Then we actually fix everything found, in the code, where it stays fixed.
Compliance and the business case
Beyond avoiding lawsuits, accessible sites are simply more usable — for screen-reader and keyboard users, yes, but also for older users, people on slow connections, and anyone on a phone in bright sun. We finish with a re-test and a WCAG 2.1 AA compliance letter you can put on file. The fixes live in your code, so they don't evaporate the moment you cancel a subscription.
Overlay widget
- $490/yr subscription
- Zero real accessibility improvement
- Actively harms screen-reader users
- No lawsuit protection
- Removed = site is bad again
Real remediation
- One-time fixed cost
- Actually accessible
- Helps screen-reader users
- Real lawsuit defense
- Fixes stay in the code
What's included
- Automated + manual accessibility audit
- Screen-reader testing (NVDA + VoiceOver)
- Keyboard-only navigation test
- Detailed remediation report with severity
- Fix implementation
- Re-test + WCAG 2.1 AA compliance letter
Often paired with accessibility (wcag)
Questions people ask about accessibility (wcag)
Isn't an accessibility widget cheaper and easier?
It's cheaper and worse — widgets don't make sites accessible, often harm screen-reader users, and don't hold up in court. Real remediation costs more once but actually works and stays fixed.
What standard do you aim for?
WCAG 2.1 AA, which is the benchmark referenced by the ADA, the EU Accessibility Act, and most procurement requirements. You get a compliance letter at the end.
Do you test with real screen readers?
Yes — NVDA on Windows and VoiceOver on Mac and iOS, plus keyboard-only navigation. Automated tools catch maybe a third of issues; the rest need manual testing.
Will the fixes stay after the project ends?
Yes — they're implemented in your actual code, not bolted on via a subscription widget. Cancel nothing; the accessibility stays.
Ready to get started with accessibility (wcag)?
Send us what you're thinking. Free quote within 4 hours. No pressure, no upsell.