ADA Website Compliance in 2026: A Practical WCAG Checklist

Can I be sued if my website is not ADA compliant?

Yes. Title III of the Americans with Disabilities Act covers businesses open to the public, such as stores, restaurants, medical and dental offices, contractors, and law firms. The DOJ's position, stated in its [web accessibility guidance, is that the ADA applies to all the goods and services a public accommodation offers, including those offered on the web.

Under federal law, a private plaintiff who wins a Title III case gets a court order to fix the barriers plus an award of attorney's fees, not money damages. That fee-shifting is what drives the volume. Many disputes never reach a courtroom at all and begin as a demand letter from a plaintiff's attorney, which still costs money and time to resolve.

The numbers are not slowing down. According to Seyfarth Shaw's tracking, plaintiffs filed 3,117 website accessibility lawsuits in federal court in 2025, up 27% from 2,452 in 2024, making up 36% of all ADA Title III federal filings. UsableNet, which also counts state court cases, reviewed more than 5,000 digital accessibility lawsuits in 2025 and found that 64% of the companies sued had annual revenue under $25 million. Small businesses are not off the radar.

What about New Jersey businesses?

New Jersey is not a top filing state. Seyfarth counted 22 federal website accessibility suits in New Jersey in 2025, compared with 1,021 in New York and 137 in Pennsylvania. But many North Jersey businesses serve New York customers, and these figures exclude state court cases and demand letters, so the low local number is not a shield.

Two other points matter here. First, the Third Circuit (which covers New Jersey) has held that ADA public accommodations are limited to physical places, so a website tied to a physical office or store is where the clearest exposure sits. Second, New Jersey's own Law Against Discrimination separately prohibits disability discrimination by places open to the public, including stores, restaurants, and doctors' offices.

Title II vs. Title III: which ADA rules apply to your website?

The ADA treats government websites and business websites very differently. Knowing which side you are on tells you whether you have a hard deadline or a litigation risk to manage.

The Title II deadlines were extended in April 2026

DOJ published its Title II web and mobile app rule on April 24, 2024. The original deadlines were April 24, 2026 for larger entities and April 26, 2027 for smaller ones. On April 20, 2026, four days before the first deadline, DOJ issued an interim final rule that moved each deadline back one year, to April 26, 2027 and April 26, 2028.

The extension did not change the technical standard, which is still WCAG 2.1 AA, and DOJ said it fully anticipates implementing the rule at the new dates. It also stated that public entities keep their existing Title II obligation to make digital services accessible in the meantime. A New Jersey township or school district should treat the extra year as time to finish the work, not to start it.

Healthcare providers have a separate rule to track. HHS's Section 504 rule requires recipients of HHS federal financial assistance, which likely includes practices that accept Medicare or Medicaid, to meet WCAG 2.1 AA. HHS issued its own extension in May 2026, moving the compliance dates to May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller ones. See our medical website design page for what that means for a practice site.

The WCAG 2.1 AA checklist: what to fix first

WCAG 2.1 has dozens of success criteria, but most real-world failures cluster in a few areas. The WebAIM Million 2026 study found detectable WCAG failures on 95.9% of the top one million home pages, and six issue types (low contrast text, missing alt text, missing form labels, empty links, empty buttons, and missing page language) accounted for about 96% of detected errors. Start there.

A few practical notes. Alt text should describe what the image communicates, not its file name. Contrast failures often hide in light gray body copy, text over photos, and placeholder text. Focus outlines are frequently removed by a designer's CSS reset, so check that they come back. And PDFs you link to (menus, intake forms, price sheets) count as part of your site's content.

Why accessibility overlays and widgets are not a fix

Overlays are third-party scripts that add an accessibility toolbar or try to repair a page automatically. They are sold as a one-line fix. They are not.

The [Overlay Fact Sheet, signed by more than 1,000 accessibility professionals and disabled users, states plainly that full compliance cannot be achieved with an overlay. Automated alt text, form label repair, error handling, and focus management are all unreliable when done after the fact by a script.

Regulators agree. In January 2025 the FTC alleged that accessiBe misrepresented its AI tool's ability to make any website WCAG compliant, and in April 2025 it finalized an order requiring the company to pay $1 million and barring it from making such claims without evidence. Meanwhile, UsableNet's 2025 report found that companies using widgets were named in roughly 95 to 155 new lawsuits every month. The widget does not change the underlying HTML that a plaintiff's tester is looking at.

How to test whether your website is ADA compliant

No single tool can tell you a site is compliant. Automated scanners only catch issues that a machine can detect, so a clean scan is a starting point, not a certificate. Use all three layers below.

1. Automated scans

• Run WAVE (from WebAIM) or the axe DevTools browser extension on your home page, top service pages, contact page, and any forms.
• Run Lighthouse in Chrome DevTools for a quick accessibility score and a list of failed audits.
• Scan templates, not just pages. If your service page template fails, every service page fails.

2. Manual keyboard testing

• Unplug your mouse. Press Tab from the top of the page and try to reach and use every link, menu, button, and form field.
• Confirm you can always see where focus is, that focus never gets trapped, and that modals and cookie banners can be closed with the keyboard.
• Zoom the browser to 200% and narrow the window to phone width. Nothing should be cut off or overlap.

3. Screen reader testing

• Use NVDA (free) on Windows or VoiceOver (built in) on Mac and iPhone.
• Listen to how images, buttons, and form fields are announced. 'Button' with no name, or 'image' with a file name, is a failure.
• Submit a form with errors and confirm the errors are announced and tied to the right fields.

A step-by-step remediation plan

Whether you are responding to a demand letter or getting ahead of one, this is the order that reduces risk fastest.

1. Audit. Combine automated scans with manual keyboard and screen reader testing across your key templates and user flows: home, services, contact form, booking or checkout, and any login.
2. Prioritize by impact. Fix anything that blocks a task first: forms that cannot be submitted, menus that cannot be opened by keyboard, checkout or booking steps that fail. Then fix site-wide issues in shared components, such as contrast in the header or a missing skip link.
3. Fix the source. Make changes in templates, components, and the CMS so the fix applies everywhere and stays fixed. Replace inaccessible PDFs with HTML pages where you can.
4. Train content editors. Most regressions come from new content: images uploaded without alt text, headings chosen for size, videos posted without captions. A one-page editor guide prevents most of them.
5. Retest and document. Retest with the same methods and keep a dated record of what you found and fixed.
6. Publish an accessibility statement. State your target (WCAG 2.1 AA or 2.2 AA), known limitations, and a phone number and email so users can report problems and get help.
7. Monitor. Schedule recurring scans and a manual spot check whenever you launch a new page type or feature.

On older sites built from page builders and stacked plugins, remediation can cost more than rebuilding, because every fix fights the theme. When we build custom websites, we code semantic HTML, keyboard-ready components, and accessible color palettes from the first commit, which is far cheaper than retrofitting them later. If you are weighing a rebuild, our guide to website costs in New Jersey covers typical market ranges.

Accessibility is also good for SEO and conversions

Much of WCAG overlaps with what search engines and AI systems need to understand a page: descriptive alt text, real headings, meaningful link text, captions and transcripts, and content rendered as text rather than baked into images. Accessible forms are also easier for everyone to complete, which means more calls and booked appointments.

If you want your site to be found as well as usable, pair accessibility work with technical and local SEO. We cover how that same foundation helps you appear in Google's AI features in our guide to AI SEO and AI Overviews.

WebBits is a senior-led web development team in Union, NJ, building custom-coded sites for New Jersey businesses since 2014. If you want an accessibility review of your current site or a rebuild designed to WCAG from day one, book a free consultation and we will give you a clear quote.

Frequently asked questions