Accessibility audit
keyboard, contrast, alt text, forms, structure and screen-reader testing, prioritized and actionable.
accessibility · ada · section 508
US web accessibility is enforced mainly through the ADA, and the practical technical benchmark is WCAG. I audit your site, fix issues in the code rather than with an overlay, and provide an accessibility statement, for businesses and public entities alike.
Substance for the web.
Does my website need to be ADA compliant? In most cases, yes. US courts treat business websites as places of public accommodation under the ADA, and the practical standard is WCAG 2.1 Level AA. State and local government sites must meet WCAG 2.1 AA under the DOJ's 2024 Title II rule, with compliance due by April 2027 or 2028.
The ADA itself does not list technical rules for the private sector, but courts and the Department of Justice consistently treat WCAG as the yardstick. In practice that means WCAG 2.1 Level AA: content that is perceivable, operable, understandable and robust. Building to WCAG 2.2 AA is the safer choice, since 2.2 fully includes 2.1.
Three different rules share one technical core. The ADA is a civil-rights law that courts apply to business and government websites. Section 508 covers federal agencies and their vendors and references WCAG 2.0 AA. WCAG is the underlying guideline all of them point to. A VPAT documents how a product conforms, which matters above all in procurement.
> Pull quote: The question is not whether your site looks good, but whether everyone can use it, by keyboard, screen reader or with low vision.
The DOJ's 2024 Title II rule requires state and local government websites and apps to meet WCAG 2.1 AA. After an extension in April 2026, large entities (population of 50,000 or more) must comply by April 26, 2027, and smaller entities and special districts by April 26, 2028.
Accessibility overlays and widgets that load over a page do not reliably create compliance and are frequently named in lawsuits. Real accessibility is solved in the code, which is also what holds up if your site is challenged.
keyboard, contrast, alt text, forms, structure and screen-reader testing, prioritized and actionable.
fixed to WCAG 2.2 AA in the code, not with an overlay. Durable and defensible.
a clear statement of your accessibility status with a way to report barriers.
accessibility stays tested, with VPAT documentation where procurement requires it.
assess the current state, prioritize barriers.
fix in the code to WCAG 2.2 AA.
publish an accessibility statement.
keep it tested over time.
Lawsuit risk is real. Web accessibility demand letters and lawsuits remain common in the US, and overlays are often cited rather than accepted as a defense. Fixing issues in the code is the reliable path.
For most consumer-facing businesses, yes. US courts widely treat business websites as places of public accommodation under ADA Title III, and the practical benchmark is WCAG 2.1 Level AA, even though there is no codified web standard for the private sector yet.
ADA Title II (government) requires WCAG 2.1 AA. Section 508 references WCAG 2.0 AA. For the private sector, WCAG 2.1 AA is the de facto benchmark. Building to WCAG 2.2 AA covers all of these because 2.2 includes 2.1 and 2.0.
No. Overlays that load over your site rarely create real conformance and are often named in lawsuits. Accessibility needs to be solved in the code.
A Voluntary Product Accessibility Template, a document that reports how a product conforms to standards such as Section 508 and WCAG. It is commonly requested in procurement.
Large public entities must comply by April 26, 2027, and smaller entities and special districts by April 26, 2028, following the April 2026 extension.
Yes. It documents your accessibility status and gives users a way to report barriers. It is good practice and signals genuine effort, though it does not replace actual conformance.
I will check it and tell you plainly what to fix, realistically and without scare tactics.
Get an accessibility audit