The WCAG 2.1 Checklist Every Business Website Needs in 2026
WCAG 2.1 AA is the accessibility standard courts apply in ADA cases. Here's a practical checklist of the most critical requirements — and which ones most sites fail.
Why WCAG 2.1 Matters for Business Websites
WCAG 2.1 (Web Content Accessibility Guidelines) Level AA is the international standard for web accessibility — and the standard US courts apply when determining ADA compliance. In the UK, it's required under the Equality Act 2010 for service providers. In the EU, it forms the basis of the European Accessibility Act requirements taking effect in 2025.
Beyond legal risk, accessibility improvements benefit all users: better contrast helps people in bright sunlight, keyboard navigation helps power users, captions help people in noisy environments. The business case and the compliance case point in the same direction.
Perceivable: Can Everyone Access Your Content?
- 1.1.1 Alt text for images — Every informative image needs descriptive alt text. Decorative images need an empty alt attribute (
alt=""). This is the most commonly cited issue in ADA demand letters. - 1.3.1 Semantic structure — Use proper HTML: headings as H1/H2/H3 (not bold paragraphs styled to look like headings), lists as ul/ol, tables with th headers.
- 1.4.3 Colour contrast — body text — Text must have at least 4.5:1 contrast ratio against its background. Light grey on white fails. Use the WebAIM Contrast Checker to verify.
- 1.4.4 Text resize — Text must remain readable when scaled to 200% in the browser without horizontal scrolling.
- 1.4.11 Non-text contrast — UI components (buttons, form borders, icons) need 3:1 contrast against adjacent colours.
Operable: Can Everyone Use Your Interface?
- 2.1.1 Keyboard navigation — Every interactive element (links, buttons, form fields, modals) must be reachable and operable using only a keyboard. Test by pressing Tab through your entire page.
- 2.1.2 No keyboard traps — Keyboard focus must never get stuck inside a component. Modals must be escapable with the Esc key.
- 2.4.3 Focus order — When tabbing through a page, focus must move in a logical reading order. Custom CSS or JavaScript reordering the visual layout can break this.
- 2.4.4 Link purpose — Link text must describe the destination. "Click here" and "Read more" fail. "Read our accessibility guide" passes.
- 2.5.3 Label in name — Buttons with visible text must have that text in their accessible name. Icon-only buttons need an aria-label.
Understandable: Is Your Interface Predictable?
- 3.1.1 Language of page — The HTML lang attribute must be set correctly (
<html lang="en">). Screen readers use it to select the right voice. - 3.3.1 Error identification — Form validation errors must be described in text, not just through colour. "This field is required" is compliant. A red border alone is not.
- 3.3.2 Labels or instructions — Every form field needs a visible label. Placeholder text alone doesn't count — it disappears when the user starts typing.
Robust: Does Your Site Work with Assistive Technology?
- 4.1.2 Name, role, value — Custom interactive components (dropdowns, tabs, accordions, sliders) must expose their role and state to screen readers via ARIA attributes.
- 4.1.3 Status messages — Dynamic content updates (form confirmations, error messages, cart updates) must be communicated to screen readers via aria-live regions.
The Issues Most Sites Actually Fail
Based on automated accessibility audits across thousands of business websites, the five most common failures are:
- Missing alt text on images (especially background images set via CSS)
- Form fields without associated labels
- Insufficient colour contrast on body text or placeholder text
- Keyboard navigation breaking at modals or dropdown menus
- Buttons with no accessible name (icon-only buttons without aria-label)
A free accessibility audit will surface these issues automatically, ranked by severity and with fix guidance. Most critical failures can be addressed by a developer in a single day.
FREQUENTLY ASKED QUESTIONS
What is WCAG 2.1 AA?+
WCAG 2.1 AA (Web Content Accessibility Guidelines) is the internationally recognised standard for web accessibility. It defines requirements across four principles: Perceivable, Operable, Understandable, and Robust. Level AA is the standard applied in US ADA cases, the UK Equality Act, and the EU's European Accessibility Act.
Is WCAG 2.1 compliance legally required?+
In the US, courts consistently apply WCAG 2.1 AA as the standard for ADA compliance. In the UK, the Equality Act 2010 requires reasonable accessibility for service providers. In the EU, the European Accessibility Act requires WCAG 2.1 AA for most digital services.
How do I test my website for WCAG 2.1 compliance?+
Free automated tools like WAVE (wave.webaim.org) and axe DevTools (browser extension) will surface the most common failures. A full accessibility audit combines automated scanning with manual testing of keyboard navigation, screen reader compatibility, and colour contrast. Most critical issues can be found automatically.
FREE 60-SECOND AUDIT
SEE HOW YOUR SITE SCORES ACROSS ALL 5 PILLARS
Performance · SEO · Accessibility · Security · AI Visibility — with a revenue impact estimate. No sign-up required.
RUN FREE AUDIT →