Website Accessibility in 2026: A Practical WCAG 2.2 Guide for Businesses
A practical guide to website accessibility for US and international businesses, covering WCAG 2.2, the ADA, the European Accessibility Act, the most common accessibility failures, and how to test and fix them.
By Cinnamon Digital ·
An accessible website works for everyone, including people who use screen readers, keyboards, voice control, magnification, or captions. It is also increasingly a legal expectation in the United States, the European Union, and beyond. The good news is that most accessibility failures are common, well understood, and fixable.
This article is general information, not legal advice. Accessibility laws vary by country and sector, so confirm your obligations with counsel.
Why accessibility matters now
- Customers: A large share of people live with a disability, and many more have temporary or situational limitations, such as a broken arm, bright sunlight, or a noisy room.
- United States: Courts have applied the Americans with Disabilities Act to websites, and website accessibility lawsuits are common. The Department of Justice's 2024 rule for state and local governments adopts WCAG 2.1 Level AA as the technical standard.
- European Union: The European Accessibility Act has applied since June 28, 2025 to many consumer products and services, including e-commerce, and can apply to companies outside the EU that sell to EU consumers.
- Business results: Accessible sites tend to be clearer, faster to use, and better structured, which also helps search engines and AI assistants understand them.
The standard: WCAG 2.2 Level AA
The Web Content Accessibility Guidelines are organized around four principles: content must be perceivable, operable, understandable, and robust. Level AA is the target most laws and policies reference.
WCAG 2.2 added several criteria that matter for modern interfaces, including:
- Target size (minimum): Click and tap targets should be at least 24 by 24 CSS pixels, or have enough spacing.
- Focus not obscured: Sticky headers, cookie banners, and chat widgets should not hide the element that has keyboard focus.
- Dragging movements: Anything that requires dragging should have a single-pointer alternative.
- Accessible authentication: Logins should not rely on memory or puzzle tests without an alternative, such as allowing password managers and paste.
- Redundant entry and consistent help: Do not make users re-enter information unnecessarily, and keep help options in a consistent place.
The most common failures and fixes
| Problem | Fix |
|---|---|
| Low color contrast | Body text needs a contrast ratio of at least 4.5:1, and large text at least 3:1 |
| Missing image alt text | Describe meaningful images; mark decorative images with empty alt text |
| Unlabeled form fields | Every input needs a visible, programmatically associated label |
| Empty links and buttons | Icon-only controls need an accessible name |
| Keyboard traps and missing focus styles | Every interactive element must be reachable and visibly focused with a keyboard |
| Poor heading structure | Use one H1 and logical H2/H3 headings |
| Videos without captions | Provide accurate captions and transcripts |
| Errors that are not explained | Identify the field in error and describe how to fix it |
How to test your site
- Run automated checks with tools such as axe, Lighthouse, or WAVE on your key templates.
- Navigate with only a keyboard. Use Tab, Shift+Tab, Enter, Space, and arrow keys through your main journeys, such as signing up, checking out, or submitting a form.
- Try a screen reader, such as VoiceOver on Mac and iOS or NVDA on Windows, on your most important pages.
- Zoom to 200% and 400% and check that content reflows without horizontal scrolling or overlap.
- Test with people with disabilities for your most important journeys. They find issues tools and checklists miss.
Building accessibility into your process
- Use an accessible design system with tested components for buttons, forms, dialogs, and menus.
- Include accessibility criteria in design reviews and pull request checklists.
- Add automated accessibility tests to your CI pipeline.
- Train content editors to write alt text, use headings correctly, and caption videos.
- Publish an accessibility statement with a way for users to report problems, and respond to reports.
Avoid overlay shortcuts
Toolbar widgets that promise instant compliance do not fix the underlying code and cannot make an inaccessible site accessible. Invest in fixing the site itself.
Where to start
Pick your three most important user journeys and test them with a keyboard and an automated checker this week. Those results usually show the highest-impact fixes. If you want an expert audit and a prioritized remediation plan, our UX research and human-centered design team can test your product, including with real users, and our frontend engineering team can implement the fixes.