Accessibility Compliance Testing in 2026: WCAG 2.2 and ADA

Accessibility compliance testing, a website examined by an automated scanner, keyboard, screen reader and magnifier

Accessibility compliance testing checks your site against WCAG using automated scans, keyboard testing and screen reader testing. Automated tools alone catch only part of the problem, so manual testing isn’t optional. Federal ADA website lawsuits rose 27% in 2025, the DOJ pushed its government deadlines to 2027 and 2028, and the European Accessibility Act has applied since June 2025. Test to WCAG 2.2 AA, build the checks into every release, and skip the overlay widgets.

Accessibility compliance testing checks a website against WCAG success criteria using automated scans, keyboard tests and screen reader tests. Automated tools found about 57% of issues in Deque’s study, so manual testing is required.

Most accessibility compliance testing starts the same way. Someone runs a free scanner, sees a green score, and assumes the job’s done. Then a demand letter arrives citing a checkout form that a screen reader can’t get through.

The gap between a passing scan and a usable site is what this guide is about. Our compliance testing team builds accessibility checks into release testing for mid-market companies, and the pattern is consistent. The scanner finds the easy half. People find the rest.

You’ll get the 2026 legal picture in one table, why most sites fail, what changed in WCAG 2.2, a test workflow your QA team can repeat every release, and what to do about overlays and VPATs.

This is practical guidance from an engineering firm, not legal advice. Talk to your attorney about your specific obligations.

The 2026 legal picture in one table

US private businesses face ADA lawsuits under Title III, with no federal technical rule. State and local governments must meet WCAG 2.1 AA under a DOJ rule, with deadlines moved to 2027 and 2028. Companies selling into the EU face the European Accessibility Act.

RuleWho it coversStandardStatus in 2026
ADA Title IIIPrivate businesses open to the publicNo federal technical rule. Courts and settlements usually reference WCAG3,117 federal website lawsuits in 2025, up 27%
ADA Title II web ruleState and local governments, and in practice the vendors whose sites and apps they useWCAG 2.1 AADeadlines moved to April 26, 2027 (50,000+ population) and April 26, 2028 (smaller entities)
Section 508Federal agencies and what they buyWCAG 2.0 AAIn force. VPATs commonly requested
European Accessibility ActCovered products and services sold in the EU, including e-commerce and bankingEN 301 549, aligned with WCAG 2.1 AAApplies since June 28, 2025

Sources: ADA.gov Title II fact sheet, Seyfarth Shaw’s 2025 lawsuit count and the European Commission’s EAA overview.

The Title II dates catch people out. The original deadline was April 2026. On April 20, 2026, the DOJ published an interim final rule pushing it back a year for large entities and to 2028 for smaller ones. Plenty of articles still quote the old date.

Private companies sometimes read that and relax. Don’t. The DOJ has long taken the position that the ADA applies to goods and services businesses offer on the web, while leaving flexibility in how they comply. Seyfarth Shaw counted 3,117 federal website accessibility lawsuits in 2025, with New York, Florida and Illinois leading. That count excludes state-court cases and demand letters, so the real number of claims is higher.

Texas note. Texas state agencies and universities follow their own accessibility rules under the Texas Administrative Code, built on Section 508. If you sell software or services to them, expect accessibility questions in procurement.

Why do most websites fail?

WebAIM’s 2026 analysis of the top one million home pages found detectable WCAG failures on 95.9% of them, up from 94.8% a year earlier, with an average of 56.1 errors per page. Not edge cases either. The same six problems show up again and again.

Web page with highlighted low-contrast text, missing image description and unlabeled form fields, the most common WCAG failures
ErrorShare of home pagesWho usually fixes it
Low-contrast text83.9%Design system and brand colors
Missing image alt text53.1%Content editors and CMS templates
Missing form input labels51%Front-end developers
Empty links46.3%Front-end developers, icon links especially
Empty buttons30.6%Front-end developers
Missing document language13.5%One line in the page template

Most common errors, WebAIM Million 2026.

Two lessons sit in that table. First, most of these are cheap fixes once someone owns them. Second, WebAIM itself warns that finding no errors doesn’t mean a page is accessible. The scanner sees code. It can’t tell whether a person can actually complete your checkout.

Who are you designing for? The CDC reports that more than 1 in 4 US adults, over 70 million people, had a disability in 2022. That’s a market, not a niche.

WCAG 2.1 or 2.2: which should you test against?

Test against WCAG 2.2 AA. It includes everything in 2.1 except one removed criterion, so meeting 2.2 AA also covers the 2.1 AA level that Title II and the EAA reference, and it keeps you ahead of the next update.

Mobile interface with large spaced buttons and a visible focus ring, representing WCAG 2.2 target size and focus criteria

W3C published WCAG 2.2 in October 2023. Of its nine new success criteria, six sit at levels A and AA, the levels that matter for compliance.

  • 2.4.11 Focus Not Obscured. When a keyboard user tabs to something, sticky headers, cookie banners and chat widgets can’t hide it.
  • Dragging Movements (2.5.7). Anything you can drag, like a slider or a sortable list, needs a click alternative.
  • 2.5.8 Target Size. Buttons and links need a minimum target of 24 by 24 CSS pixels, or enough spacing around them.
  • Consistent Help, 3.2.6. Help links, chat and contact details appear in the same place across pages.
  • 3.3.7 Redundant Entry. Don’t make people retype information they already gave in the same process.
  • And 3.3.8, Accessible Authentication. Logins can’t depend on memory puzzles or transcription without an alternative, so allow password managers and paste.

WCAG 2.2 also removed 4.1.1 Parsing, which modern browsers made obsolete. Look at that list again. Cookie banners, chat widgets and login forms are exactly the third-party pieces mid-market sites bolt on last and test least.

A test workflow your QA team can repeat every release

Run four passes. An automated scan in the build pipeline, a keyboard-only pass, a screen reader pass on key journeys, and targeted checks for the WCAG 2.2 criteria. Record results against each criterion so you have evidence, not just a score.

Website release passing four inspection stations, representing the four-pass accessibility test workflow

Pass 1. Automated scan in the pipeline

Add axe-core or Lighthouse accessibility checks to your build so new errors fail the build before they ship. This is where QA automation earns its keep, because it catches regressions every single release without anyone remembering to run it.

Be clear on the ceiling. Deque, which makes axe, analyzed more than 13,000 pages and found automated testing identified 57.38% of issues by count. Useful. Not enough. And that figure comes from a vendor with a stake in automated tools, so treat it as a best case.

Pass 2. Keyboard only

Unplug the mouse. Tab through every key journey, such as sign-up, search, checkout and the contact form. Can you reach everything? Can you see where focus is at all times? Can you escape every menu and dialog? Fifteen minutes per journey, and it finds problems no scanner will.

Pass 3. Screen reader

Test key journeys with NVDA on Windows and VoiceOver on Mac and iPhone. Listen for buttons announced as just button, images read as file names, and form errors that appear on screen but never get announced. Write short scripts for each journey so the test is repeatable, not a vibe check.

Pass 4. WCAG 2.2 spot checks

Check the six new A and AA criteria directly. Focus hidden behind sticky elements, drag-only controls, tiny tap targets on mobile, help that moves around, forms that ask twice and logins that block paste.

Then log results by WCAG criterion, with page, severity and owner. That log becomes your evidence trail, and it matters later. Our quality engineering practice treats it like any other release record, and we explained why testing belongs inside delivery in QA vs quality engineering.

What to test first when you can’t test everything

Test templates and journeys, not page counts. A site built from a dozen templates with five key journeys can be covered well by testing each template once and walking each journey end to end with a keyboard and a screen reader.

A 2,000-page website sounds like a 2,000-page audit. It almost never is. Most mid-market sites are a handful of templates repeated with different content, so the work scales with templates and journeys.

PriorityWhat to testWhy first
1Journeys that make or lose money: checkout, quote request, sign-up, login, paymentWhere lawsuits and lost customers concentrate
2Shared components: header, navigation, footer, cookie banner, chat widgetOne fix repairs every page at once
3Each page template once: home, service, product, article, contactCovers the bulk of the site through a few samples
4Documents and media: PDFs, videos, embedded formsUsually outsourced and easily forgotten

Test priority for a mid-market website.

That fourth row deserves a warning. PDFs are the quiet liability on plenty of B2B sites. Price lists, brochures and application forms uploaded years ago and never checked. If a customer needs it to do business with you, test it or replace it with an accessible web page.

Do overlay widgets make you compliant?

No. And the Federal Trade Commission has said as much about one of the best-known vendors.

Patch over a cracked panel beside engineers rebuilding it properly, representing overlays versus real accessibility fixes

In April 2025 the FTC finalized an order requiring accessiBe to pay $1 million over claims that its plug-in could make any website WCAG compliant. The order bars the company from making misleading claims of that kind.

Overlays try to patch a page after it loads. The underlying code stays broken, and disabled users who rely on their own assistive technology frequently find overlays get in the way. If a vendor promises compliance or lawsuit protection from one line of JavaScript, that’s your cue to walk away.

Bias disclosed. We sell testing and remediation, so we would say that. The FTC order is the part you don’t have to take our word for.

VPATs and ACRs: when buyers ask for one

A VPAT is a template for documenting how a product meets accessibility standards. Once completed, it’s called an Accessibility Conformance Report, or ACR. Government, education and enterprise buyers routinely ask for one during procurement.

The current template is VPAT 2.5Rev from ITI, with editions for Section 508, the EU standard, WCAG and an international version that combines them. If you sell software, a portal or a web app to cities, counties, school districts or universities, the Title II deadlines mean those buyers will be asking for one far more in 2027.

A credible ACR is built from real test results, the same criterion-by-criterion log from the workflow above. An ACR written from memory, with every row marked supports, won’t survive a buyer’s own testing.

Fixing what you find

Testing finds problems. Design and development fix them, and the cheapest fixes happen at the source.

  • Fix colors and focus styles in the design system once, rather than page by page. Our UI and UX design team starts there.
  • Build accessible components once, with labels, states and keyboard support, and reuse them everywhere
  • Give content editors an alt text field they can’t skip
  • Third-party widgets? Test them like your own code, and replace the ones that fail.

For custom portals and apps, accessibility belongs in the definition of done. Our web and mobile development team builds and tests it in from the first sprint, which costs far less than retrofitting after launch.

Keeping it accessible after the fix

Sites drift. A new campaign page ships with low-contrast text. A marketing tool adds a pop-up that traps keyboard focus. Six months after a clean audit, you’re back where you started.

Three habits stop the drift.

  • The automated scan stays in the build pipeline and fails the build on new serious errors. No exceptions for urgent launches, because urgent launches are when it slips.
  • Run a keyboard and screen reader pass on key journeys every quarter, and after any redesign
  • New third-party scripts get the same test as your own code before they go live

And name an owner. Accessibility that belongs to everyone belongs to nobody. In most mid-market companies it sits best with whoever owns release quality, with design and content as partners.

Who we are

Upen Group is a digital transformation and engineering company headquartered in Irving, Texas. Our compliance testing, QA automation, UI and UX design and web development teams help mid-market companies test against WCAG 2.2, fix what they find and keep the evidence that buyers and auditors ask for.

The short answer

Test to WCAG 2.2 AA with four passes, which are automated scans in the pipeline, keyboard testing, screen reader testing and checks for the new 2.2 criteria. Prioritize money-making journeys and shared components, log results by criterion, and fix issues at the design system level. Skip overlays. And plan around the 2027 and 2028 Title II dates if you sell to state or local governments.

Not sure where your site stands? Send us your three most important user journeys, and we’ll run all four test passes on them and send back a prioritized list of fixes mapped to WCAG 2.2.

What IT and marketing leaders ask us

Does the ADA apply to our website if we’re a private business?

The DOJ’s position is that it does for businesses open to the public, though there’s no federal technical standard for private websites. Federal courts saw 3,117 website accessibility lawsuits in 2025. Ask your attorney how it applies to you.

Did the DOJ push back the April 2026 deadline?

For state and local governments, it did. An April 2026 interim final rule moved the deadline to April 26, 2027 for entities serving 50,000 or more people and April 26, 2028 for smaller ones. The standard is still WCAG 2.1 AA.

WCAG 2.1 or 2.2?

Test to 2.2 AA. It covers what 2.1 AA requires plus six new A and AA criteria, so you meet the legal references and stay ahead of them.

Can an automated scanner tell us we’re compliant?

No. Deque found automated tools identified about 57% of issues, and WebAIM warns that zero detected errors doesn’t mean a page is accessible. Keyboard and screen reader testing cover the rest.

Will an overlay widget protect us from a lawsuit?

Don’t count on it. The FTC ordered accessiBe to pay $1 million in 2025 over claims its widget made sites WCAG compliant. Fixing the underlying code is the reliable path.

What does an accessibility audit cost?

It scales with the number of templates and user journeys, not total pages. A site built from a dozen templates with five key journeys is a much smaller job than its page count suggests.

Does the European Accessibility Act apply to a US company?

It can, if you sell covered products or services, such as e-commerce, to customers in the EU. It has applied since June 28, 2025, with an exemption for microenterprises providing services. Get EU legal advice on your specific case.