Website Accessibility in 2026: ADA, WCAG 2.2 and the European Accessibility Act Explained for Small Businesses

Website accessibility has moved from “nice to have” to a real business risk. In 2026, US public entities have firm deadlines under ADA Title II, the European Accessibility Act (EAA) is enforceable across the EU, and private businesses in the US continue to receive accessibility demand letters and lawsuits every year.

This guide explains the rules in plain English, what they mean for a small or mid-sized business website, and the practical steps we recommend to reduce risk while improving the experience for every visitor.

Note: this article is general information, not legal advice. Speak with a qualified attorney about your specific obligations.

The 2026 accessibility landscape

ADA Title II: public entities (and their vendors)

The Department of Justice’s 2024 rule requires state and local governments’ websites and mobile apps to meet WCAG 2.1 Level AA. On April 20, 2026, the DOJ published an Interim Final Rule extending the compliance dates by one year: April 26, 2027 for entities serving 50,000 people or more, and April 26, 2028 for smaller entities and special districts. Jackson Lewis has a clear summary of the change.

If your business builds or maintains websites, apps or documents for schools, cities, counties or transit agencies, these requirements flow down to your work too.

ADA Title III: private businesses

Businesses open to the public, including e-commerce and service businesses, fall under Title III. There is no specific technical rule or deadline, but several thousand federal website accessibility lawsuits are filed each year, plus many more demand letters that settle privately. Courts and plaintiffs routinely point to WCAG 2.1 AA as the standard. E-commerce sites are the most frequent targets, and small businesses are sued far more often than most owners expect.

The European Accessibility Act (EAA)

Since June 2025, the EAA requires many products and services sold to EU consumers, including e-commerce, banking, transport and e-books, to be accessible. The technical reference is the European standard EN 301 549, which aligns with WCAG. If you sell online to EU customers, check whether you are in scope; micro-enterprises providing services have some exemptions.

WCAG 2.1 vs. WCAG 2.2

WCAG 2.1 AA is the legal benchmark in most US contexts, but WCAG 2.2 is the current W3C recommendation. It adds criteria such as focus not being hidden behind sticky headers, minimum target sizes for buttons and links, alternatives to dragging, consistent help and more accessible authentication. Building to WCAG 2.2 AA today future-proofs your site.

The most common accessibility failures

Large-scale audits of popular homepages repeatedly find the same handful of problems on the vast majority of sites:

• Low color contrast between text and background.
• Missing alternative text on meaningful images.
• Unlabelled form fields, especially in contact, booking and checkout forms.
• Empty links and buttons, such as icon-only buttons with no accessible name.
• Keyboard traps and invisible focus states in menus, sliders and pop-ups.
• Missing document language and poor heading structure.

The good news: these are also some of the easiest issues to fix, and fixing them improves usability and SEO at the same time.

Why accessibility overlays don’t protect you

One-line “accessibility widgets” promise instant compliance. They cannot fix underlying code problems such as missing labels, broken keyboard navigation or inaccessible PDFs, and businesses using them continue to be sued. Overlays have also drawn regulatory scrutiny over misleading claims. Treat them as, at best, a minor convenience, never as your compliance strategy.

A practical accessibility plan for small businesses

1. Run an automated scan. Tools like WAVE, axe DevTools or Lighthouse catch roughly a third to half of issues and give you a quick baseline.
2. Test manually. Navigate your key pages using only the keyboard, then try a screen reader such as NVDA (Windows) or VoiceOver (Mac/iOS).
3. Fix the big four first: contrast, alt text, form labels and link and button names.
4. Fix templates, not just pages. In WordPress, most issues live in the theme, header, footer and page-builder templates. Fixing them once fixes every page.
5. Check key user journeys: contact forms, booking flows, checkout, account login and downloadable documents.
6. Publish an accessibility statement with a way for users to report problems, and respond quickly when they do.
7. Make it ongoing. Add accessibility checks to every redesign, new page and plugin update.

Accessibility is good business, not just compliance

Around 1.3 billion people worldwide live with a disability, and many more benefit from accessible design: older users, people on small screens, people in bright sunlight or noisy environments. Accessible sites tend to be faster, clearer and easier to use, which improves conversions. Clean semantic markup also helps search engines and AI systems understand your content, supporting both traditional SEO and generative engine optimization.

Accessibility also shapes modern design choices. It is one of the key themes in our 2026 web design trends roundup, and WordPress itself keeps improving accessibility in core, as covered in our WordPress 7.0 & 7.1 guide.

Frequently asked questions

Is my small business legally required to have an accessible website?

If you are a business open to the public in the US, courts have widely applied ADA Title III to websites, even without a specific technical regulation. If you sell to EU consumers, the EAA may apply. Consult an attorney for your exact situation, but building to WCAG 2.1 or 2.2 AA is the safest path.

How much does it cost to make a website accessible?

It depends on the size and age of the site. Many small business sites can fix the most common issues in days rather than months, especially when problems are fixed at the template level. Complex e-commerce or custom apps require more testing.

Can I rely on an automated scanner alone?

No. Automated tools miss many issues, including keyboard problems, confusing content and screen-reader behavior. Combine automated scans with manual testing.