Accessibility

Website accessibility requirements come down to one technical standard, WCAG 2.1 Level AA, and a patchwork of laws that decide whether it is legally binding on you or merely the benchmark a court will measure you against. If you run a private business in the United States, no federal regulation currently tells you exactly what your site must do. That does not mean you are safe. It means the standard gets applied to you after someone sues, not before.

Here is what the rules say in 2026, which ones reach your business, a five step plan, and what the work costs. One correction up front: the Department of Justice extended its Title II deadline in April 2026. If you read that the deadline already passed, that source is out of date.

What Do Website Accessibility Requirements Actually Say?

Website accessibility requirements are built on the Web Content Accessibility Guidelines, or WCAG, published by the World Wide Web Consortium. Nearly every US law points to WCAG 2.1 Level AA, which requires that content be perceivable, operable, understandable, and reliable with assistive technology. Level AA is the tier regulators cite.

In practice that means checkable things. Every image carries alt text describing its purpose. Text contrast hits at least 4.5 to 1. Every form field has a label a screen reader can announce. Every function works from a keyboard alone. Video carries captions. Headings run in logical order instead of being picked for their size. Nothing important is signalled by color alone.

Version numbers matter more than people expect. WCAG 2.1 became a W3C Recommendation in June 2018 and remains the version written into US regulation. WCAG 2.2 arrived in October 2023 and is the better target for new work, but no federal rule requires it. WCAG 3.0 is still a working draft years from completion. A vendor selling you WCAG 3.0 compliance today is selling conformance to a document still being written.

Which Accessibility Rules Apply to Your Website?

Which law reaches you depends on what kind of organization you are, and most owners assume the wrong one applies. Private companies fall under ADA Title III, which has no technical regulation. Government entities fall under Title II, which now has a very specific one.

Rule Who it covers Standard and date
ADA Title III Private businesses open to the public No regulation. WCAG applied through case law and DOJ guidance
ADA Title II State and local government WCAG 2.1 AA. April 26, 2027 for populations of 50,000 and up, April 26, 2028 below that
Section 504 (HHS) Healthcare providers taking HHS funding, including many private practices WCAG 2.1 AA. May 11, 2027 for 15 or more employees
Section 508 Federal agencies, and vendors through procurement WCAG 2.0 AA, one version behind Title II
European Accessibility Act Anyone selling to EU consumers, including US ecommerce In force since June 28, 2025

The Title II dates are worth reading twice. DOJ published the rule in April 2024 with a first deadline of April 24, 2026, then issued an interim final rule six days before it landed, pushing both dates back a year. The National Federation of the Blind sued in May 2026, arguing the extension skipped required notice and comment. No court has ruled, so the extension stands today and could still be undone.

For a private business, the absence of a regulation is not the protection it sounds like. DOJ’s own guidance says the department has no regulation setting detailed standards and that businesses can choose how they make services accessible. Plaintiffs’ firms fill that gap with WCAG, and courts have gone along.

Seyfarth Shaw counted 3,117 federal website accessibility lawsuits in 2025, up 27 percent from 2,452 the year before. UsableNet, which also tracks New York and California state courts, put the total above 5,000 and found that 64 percent of defendants had under $25 million in annual revenue. This is not a Fortune 500 problem.

The Five Step Website Accessibility Requirements Playbook

Meeting website accessibility requirements is a sequence, not a single project. Run it in this order, because fixing templates before you know what is broken means paying twice. We use this sequence with clients, and a typical 25 page site moves through it in six to ten weeks.

01 Run an automated scan, then discount it. Free tools like WAVE or axe DevTools take about an hour on a small site and surface contrast failures, missing alt text, and unlabeled form fields. Automated testing catches roughly a third of WCAG issues. Treat the report as your starting inventory, never as a passing grade.
02 Test the paths that make you money. Unplug the mouse and complete your contact form, checkout, and booking flow using only Tab, Enter, and the arrow keys, then repeat with a screen reader. This half day of manual work finds the issues that produce lawsuits, because a blocked checkout is a denial of service in a way a low contrast footer is not.
03 Fix the theme before the pages. Most failures live in templates, not content. Correcting contrast in your color variables, adding a visible keyboard focus outline, and repairing heading order in your header and footer can clear hundreds of individual errors in one pass. On client sites this step alone typically removes 60 to 80 percent of the reported issues.
04 Work through content page by page. Alt text, captions, descriptive link text, and PDFs. PDFs are the item everyone forgets and they are covered too. A scanned menu or price sheet with no text layer is unreadable to a screen reader, and remediating one runs $50 to $150 per document.
05 Publish a statement and hold the line. Post an accessibility statement naming your target standard, the date you last audited, and a real email address for reporting problems. DOJ guidance specifically mentions giving people a way to report barriers. Then add an accessibility check to your publishing process, because a compliant site drifts within a year.

Where most sites stall

Steps one and two are genuinely DIY. Step three is where teams stall, because it means editing the theme rather than the content, and a bad fix breaks the layout. That is where handing it to a developer costs less than the second attempt.

Our website design and development team handles accessibility remediation on existing sites and builds it into new ones. Book a discovery call and we will tell you which of the five steps you actually need help with.

How Much Does Meeting Website Accessibility Requirements Cost?

Remediating an existing small business site to WCAG 2.1 AA generally runs $3,000 to $15,000, while building accessibility into a new site adds roughly 5 to 10 percent to the project. That gap is the whole argument for handling it during a rebuild rather than after.

Scope Typical range What it includes
Audit only $1,500 to $5,000 Automated scan plus manual keyboard and screen reader testing, prioritized report
Remediation, small site $3,000 to $8,000 Under 25 pages, template and content fixes, retest
Remediation, larger site $8,000 to $25,000 Ecommerce or 100 plus pages, custom components, PDF remediation
Built in during a rebuild 5 to 10 percent of project Accessible components and testing folded into design and build
Defending one lawsuit $15,000 to $50,000 plus Settlement, legal fees, and the remediation you still have to do

That last row changes minds. Settling one claim usually costs more than fixing the site would have, and the settlement requires the fix anyway. If a rebuild is already on your roadmap, folding this in beats treating it as a separate project later, the same math we walk through in our guides to what a website costs and what a website redesign should cost.

Should You Use an Accessibility Overlay Widget?

No, not as your compliance strategy. Overlay widgets are the one shortcut here with a real evidence trail against them. In April 2025 the FTC finalized a $1 million order against accessiBe over claims that its widget could make any website WCAG compliant, and over reviews presented as independent that were not. The order bars unsupported claims that automated products achieve conformance.

UsableNet’s data shows roughly 1,400 lawsuits filed in 2025 against companies already running an accessibility widget, about 28 percent of its tracked caseload. Over 1,000 accessibility professionals, including editors of the WCAG and ARIA specifications, have signed a public factsheet stating that no overlay can bring a site into full conformance. Buying one does not end the exposure.

Do this Skip this
Fix contrast and focus states in the theme A widget that restyles the page on the visitor’s side
Manual keyboard and screen reader testing on key flows An automated score treated as proof of conformance
Write real alt text for meaningful images AI generated alt text left unreviewed
Target WCAG 2.1 AA, move to 2.2 on your next build Paying for WCAG 3.0 conformance, which does not exist yet

One more reason to do the work properly: the same fixes help everyone. Semantic headings, descriptive links, and keyboard friendly pages overlap with technical SEO and with website speed optimization. The scale of the problem is the opportunity: WebAIM’s 2026 study of a million home pages detected WCAG failures on 95.9 percent of them, averaging 56.1 errors per page, and both numbers got worse than the year before. Most of your competitors have not done this.

Frequently Asked Questions About Website Accessibility Requirements

Do websites legally have to be accessible?

For state and local government, yes, with a specific WCAG 2.1 AA rule and dated deadlines. For private businesses, there is no federal regulation naming a standard, but courts have repeatedly applied the ADA to websites and thousands of suits are filed each year. In practice the requirement is real even though the regulation is missing.

What WCAG version do I need to meet in 2026?

Target WCAG 2.1 Level AA. That is what the Title II rule and the HHS Section 504 rule require, and it is the version plaintiffs cite. WCAG 2.2 is a sensible target for a new build since it adds a handful of criteria, and WCAG 3.0 is still a draft with no legal force.

Did the ADA website deadline pass in April 2026?

No. DOJ extended it by a year in an interim final rule published April 20, 2026. Public entities serving 50,000 people or more now have until April 26, 2027, and smaller ones until April 26, 2028. That extension is being challenged in court, so treat the later date as a floor rather than a promise.

Will an accessibility widget protect me from a lawsuit?

The evidence says no. About 1,400 suits were filed in 2025 against companies already running one, and the FTC fined a major overlay vendor $1 million over its compliance claims. A widget can sit alongside real remediation, but it is not a substitute for fixing the underlying site.

How long does accessibility remediation take?

A 25 page business site usually takes six to ten weeks: about a week to audit, three to five weeks of template and content fixes, and a retest at the end. Ecommerce sites take longer because checkout and filtering need testing on every change.

Does the European Accessibility Act apply to a US company?

It can. The act has applied since June 28, 2025 and reaches services offered to consumers in the EU regardless of where the company sits, so a US store shipping to EU customers is in scope. Enforcement runs through individual member states, and very small service providers are exempt.

Next step

Find out where your site actually stands

We will run your site against WCAG 2.1 AA, test the pages that bring you customers, and give you a prioritized list with real costs attached. You will know what has to be fixed, what can wait, and whether it belongs in a remediation project or your next rebuild.

Book a Discovery Call

In this article

— Keep reading

Related articles