Service · Updated
ADA Website Compliance and Accessibility Remediation
Webvello audits websites against WCAG 2.1 and 2.2 Level AA, fixes what fails in your source code, and rebuilds sites where that is the cheaper path. State and local governments now have dated obligations under the ADA Title II rule; businesses face the same expectation through Title III. We test with automated tools and people, and we never sell a plug-in as a fix.
Why this is urgent now
The Justice Department’s 2024 rule requires state and local government websites and apps to meet WCAG 2.1 AA. An interim final rule on April 20, 2026 moved the deadlines to April 26, 2027 for entities serving 50,000 or more people and April 26, 2028 for smaller entities and special districts; the standard did not change (Federal Register).
The gap is real. When we tested 95 California county and city homepages in October 2026, 66.3% had at least one automatically detectable WCAG 2.1 A or AA failure (full study). Across the wider web, WebAIM found detectable failures on 95.9% of the top one million home pages in 2026 (WebAIM Million).
Which rule applies to you
A short map of who is covered by what. Each row links to the guide that explains it with sources.
| Who | Rule | Standard and dates | Guide |
|---|---|---|---|
| State and local governments, special districts, public schools and colleges | ADA Title II web rule (28 CFR part 35, subpart H) | WCAG 2.1 AA; compliance dates April 26, 2027 (50,000+ population) and April 26, 2028 (smaller entities and special districts) | Title II guide |
| Businesses open to the public | ADA Title III, per DOJ guidance of March 18, 2022 | No technical regulation; DOJ names WCAG and the Section 508 Standards as helpful guidance | Business websites |
| Federal agencies and the vendors that sell to them | Section 508 of the Rehabilitation Act | WCAG 2.0 A and AA (Revised 508 Standards, E205.4) | Section 508 vs ADA vs WCAG |
| Companies selling covered products or services to EU consumers | European Accessibility Act, Directive (EU) 2019/882 | Applies to covered products and services after June 28, 2025; microenterprises providing services are exempt | EAA for US businesses |
General information, not legal advice.
How an engagement works
1. Audit
Automated scanning with axe-core across your templates, then manual testing with keyboard only, a screen reader and 200% and 400% zoom. Every finding is recorded against its WCAG 2.2 success criterion, with the page, the element and the fix.
2. Remediate in the source
We fix templates and components in your code, not with a script that rewrites the page in the browser. Fixing the header, navigation, forms and article layout clears most issues on every page that uses them.
3. Rebuild where it is cheaper
When a theme or page builder makes accessible markup impractical, we rebuild in custom code with accessibility as a build requirement, keeping every URL that earns traffic. See our migration paths.
4. Monitor
Automated checks on new and changed pages, a monthly manual spot check, and a published accessibility statement with a working contact for people who hit a barrier.
Rebuild paths: WordPress, Drupal, Wix and other platforms.
What you get
- Findings report organized by template and by WCAG 2.2 success criterion, with severity and the exact element
- Remediation in your codebase, or a prioritized fix list for your developers
- Retest after fixes, with before-and-after automated results
- Accessibility statement and feedback route, drafted for your review
- Guidance for PDFs and documents that are still used to access services
- Procurement and content-authoring guidance so new work does not reintroduce failures
Find out where your site stands
The free audit runs automated checks on your key templates and tells you what a full audit and remediation would involve.
Why we fix the source, not the browser
Overlay widgets run after a page loads. They cannot rewrite your templates, your PDFs or the third-party tools you embed. In April 2025 the FTC finalized an order requiring one overlay vendor to pay $1 million over claims that its plug-in could make any website WCAG compliant (FTC). The details are in what the FTC found.
Guides, tools and research
- The ADA Title II web rule: deadlines, requirements, exceptions
- The Title II deadline moved to 2027: what did not change
- WCAG 2.2 AA checklist: all 55 criteria
- Free accessibility checker
- Study: 95 California government homepages
- WCAG 2.1 vs 2.2
- Does the ADA apply to business websites?
- Section 508 vs ADA vs WCAG
- The European Accessibility Act for US businesses
- Accessibility and AI search
- What is WCAG?
- What is a VPAT?
Common questions
Can you guarantee ADA compliance?
No one can honestly guarantee that. Compliance depends on your obligations, your content and how the site keeps changing. What we can do is test against WCAG 2.1 and 2.2 AA, fix what fails in your code, document what we tested, and set up monitoring so new work does not slip. This page is general information, not legal advice.
Which WCAG version do you test against?
WCAG 2.2 Level AA. It includes everything in WCAG 2.1 AA, which the ADA Title II rule requires, except 4.1.1 Parsing, which W3C removed as obsolete, plus six newer Level A and AA criteria such as target size and accessible authentication.
Why not use an accessibility overlay or widget?
An overlay runs in the browser after the page loads and cannot change your templates, documents or third-party content. In April 2025 the FTC finalized an order against one overlay vendor over claims that its plug-in could make any website WCAG compliant. We fix the source instead.
How long does remediation take?
It depends on how many templates, forms and documents you have and how they were built. The audit gives a dated plan. Template fixes usually clear most findings quickly; documents and third-party embeds take longer.
Do you work with government agencies?
Yes. Public entities have dated obligations under the Title II rule, and content provided through contractors is covered. We audit, remediate and rebuild public-sector sites and can work within procurement requirements.
Is our own site accessible?
We test webvello.com with the same automated tools we use for clients. On October 17, 2026 that testing found color contrast failures, which we fixed across the site the same day. Our accessibility statement explains how to report a barrier.
Have a deadline coming?
Tell us your platform, page count and date. We will tell you what an audit and remediation would take.
Book a Free Call