Website Accessibility and the ADA: A WCAG 2.2 Checklist for US Business Websites and Apps
Accessibility means people with disabilities can use your website or app, including people who are blind and use screen readers, people who navigate by keyboard, people with low vision or colour blindness, and people with hearing or cognitive disabilities. For US businesses it is also a legal and commercial issue: website accessibility lawsuits under the Americans with Disabilities Act (ADA) are filed in large numbers every year, and accessible sites tend to be easier for everyone to use.
This article is general information, not legal advice. Consult an attorney about your specific obligations.
The ADA and WCAG: how they relate
- Title III of the ADA covers businesses open to the public. Courts have frequently applied it to websites and apps, although the statute does not name a specific technical standard for private businesses.
- Title II covers state and local governments. In 2024 the Department of Justice issued a rule adopting WCAG 2.1 Level AA as the technical standard for their web content and mobile apps, with compliance dates phased in by entity size.
- WCAG (Web Content Accessibility Guidelines) from the W3C is the widely accepted benchmark. WCAG 2.2, published in 2023, is the current version, and Level AA is the usual target.
A practical WCAG 2.2 AA checklist
Perceivable
- Meaningful images have descriptive alt text; decorative images have empty alt attributes.
- Videos have captions; audio content has transcripts.
- Text has sufficient colour contrast: at least 4.5:1 for normal text and 3:1 for large text and key interface elements.
- Information is not conveyed by colour alone, for example form errors also use text or icons.
- Content reflows on small screens and at 200% zoom without horizontal scrolling.
- Headings, lists and tables use proper semantic markup.
Operable
- Everything works with a keyboard alone, with a logical tab order and no keyboard traps.
- Focus indicators are clearly visible, and focused elements are not hidden behind sticky headers or banners (new in WCAG 2.2).
- A “skip to main content” link is provided.
- Functions that use dragging have a single-pointer alternative (new in WCAG 2.2).
- Touch and click targets are at least 24 by 24 CSS pixels or adequately spaced (new in WCAG 2.2).
- Moving, auto-playing or time-limited content can be paused or extended.
Understandable
- The page language is declared.
- Form fields have visible labels and clear instructions.
- Errors are identified in text with suggestions for fixing them.
- Users are not asked to re-enter information they already provided in the same process (new in WCAG 2.2).
- Login does not rely solely on cognitive tests such as remembering or transcribing codes, and supports password managers and copy-paste (new in WCAG 2.2).
- Help options appear in a consistent location (new in WCAG 2.2).
Robust
- Custom components such as menus, modals, tabs and accordions expose correct names, roles and states to assistive technology, using native HTML elements or ARIA correctly.
- Status messages, such as “item added to cart”, are announced to screen readers.
Why overlay widgets are not enough
Accessibility overlays, the toolbar plugins that promise one-line compliance, cannot fix underlying problems in code such as missing labels, broken keyboard navigation or inaccessible custom components. Many accessibility advocates and users criticise them, and they have not prevented lawsuits. Real compliance comes from fixing the site itself.
How to approach remediation
- Automated scan with tools such as axe, WAVE or Lighthouse to find common issues quickly. Automated tools catch only part of the problems.
- Manual testing with keyboard-only navigation and screen readers (NVDA, JAWS, VoiceOver, TalkBack).
- Prioritize critical user journeys: navigation, search, product pages, forms, checkout, booking and login.
- Fix in the design system so components are accessible everywhere they are used.
- Publish an accessibility statement with contact details for reporting issues.
- Test continuously by adding automated accessibility checks to CI and reviewing new features.
Key takeaways
Treat WCAG 2.2 AA as your target, fix issues in code rather than relying on overlays, focus first on the journeys that matter most to customers, and build accessibility into your design and development process so it stays fixed.
Frequently asked questions
Does the ADA apply to my business website?
Many courts have applied ADA Title III to websites of businesses open to the public, especially where the site is connected to goods or services. Consult an attorney about your specific situation.
What WCAG level should we target?
WCAG 2.2 Level AA is the widely accepted target for business websites and apps, and AA is the level referenced by most regulations and settlements.
Do accessibility overlay plugins make a site compliant?
No. Overlays cannot fix underlying code issues, and businesses using them have still faced lawsuits. Remediating the site itself is the reliable approach.
How long does an accessibility remediation take?
A focused audit takes one to three weeks. Remediation depends on site size and how many issues sit in shared components; fixing a design system often resolves many issues at once.
We audit and remediate websites and apps against WCAG 2.2 AA, and build accessibility into new projects. See our web development services or book a free consultation.
