ADA lawsuits up 4,600+ in 2023  ·  Most target small businesses  ·  Run your free scan now →
← All Articles
Compliance Guide 12 min read

WCAG 2.1 AA Compliance Checklist for Websites: The 2026 Complete Guide

This WCAG 2.1 AA compliance checklist covers every success criterion your website needs to meet to satisfy the standard most commonly applied in ADA website lawsuits. Use it to audit your current site, guide remediation, and verify compliance.

Perceivable: Text Alternatives (1.1)

Every non-text content item must have a text alternative. For images: meaningful images need descriptive alt text that conveys the same information. Decorative images should have empty alt="" so screen readers skip them. Complex images like charts need either detailed alt text or a long description in the page. Form inputs that use images as buttons need alt text describing the function. This is the most commonly violated WCAG criterion and the most frequently cited in ADA lawsuits.

Perceivable: Color Contrast (1.4.3)

Normal text must have a contrast ratio of at least 4.5:1 against its background. Large text (18pt or 14pt bold) needs at least 3:1. This applies to text in images too. The most common failure is light gray text on white backgrounds — very popular in modern design but often failing the 4.5:1 threshold. Use a contrast checker tool to verify every text/background combination on your site.

Perceivable: No Color-Only Information (1.4.1)

Color alone cannot be used to convey information. If you mark required form fields only with a red border and no text indicator, that fails. If error states are communicated only through color changes, that fails. Add text labels, icons, or patterns alongside color to ensure information is perceivable by users who cannot distinguish colors.

Operable: Keyboard Navigation (2.1)

All functionality must be operable via keyboard alone — no mouse required. Every interactive element (links, buttons, form fields, dropdowns, modals) must be reachable and activatable via Tab, Enter, and arrow keys. Custom JavaScript components are a common failure point — carousels, modals, and dropdown menus often trap keyboard focus or are completely unreachable by keyboard.

Operable: Focus Visible (2.4.7)

Keyboard focus must be visible. When a user navigates via keyboard, they must be able to see which element currently has focus. Many designers remove the default browser focus outline (that blue ring) for aesthetic reasons — this creates a WCAG violation. If you remove the default outline, you must replace it with a visible alternative. This is one of the most common violations and one of the easiest to fix.

Understandable: Form Labels (3.3)

Every form input must have an associated, descriptive text label. Placeholder text is not a label — it disappears when the user starts typing. Labels must be programmatically associated with their input via the for/id relationship or ARIA labeling. Error messages must identify the specific field in error and describe how to fix it. This is the second most common WCAG violation category after missing alt text.

Robust: HTML Validity (4.1)

HTML must be valid and parseable by assistive technologies. Common failures include duplicate IDs (each ID must be unique per page), unclosed tags, and invalid ARIA attributes. Run your pages through an HTML validator and an ARIA validator. Invalid HTML confuses screen readers and creates unpredictable behavior for users with disabilities.

Protect Your Business

Run a Free WCAG 2.1 AA Scan

Find every ADA violation on your website in 60 seconds. No signup required.

Free Scan → Plans from $39/mo
Frequently Asked Questions
How many WCAG 2.1 AA success criteria are there?
WCAG 2.1 AA includes 50 success criteria across the four principles (Perceivable, Operable, Understandable, Robust). Level A has 30 criteria, and Level AA adds 20 more. A free ADAWebPro scan checks your site against these criteria automatically.
Which WCAG violations are most common in ADA lawsuits?
The most commonly cited violations in ADA website lawsuits are: missing image alt text, insufficient color contrast, missing form labels, keyboard navigation barriers, and missing focus indicators. ADAWebPro prioritizes these high-risk violations in scan reports.
Does every page need to be WCAG compliant?
Yes — WCAG compliance applies to all pages of your website, not just the homepage. Plaintiff attorneys often test contact forms, checkout pages, and deep-linked pages rather than just homepages. ADAWebPro monitoring scans multiple pages to provide site-wide coverage.
Is WCAG 2.2 different from WCAG 2.1?
WCAG 2.2 adds 9 new success criteria to WCAG 2.1, primarily focused on cognitive accessibility and mobile users. All WCAG 2.1 AA criteria are included in WCAG 2.2 AA. US courts have primarily applied WCAG 2.1 AA in cases to date. ADAWebPro scans against WCAG 2.1 AA as the current legal standard.
Free Scan

Find Out If Your Website Is at Risk

Free WCAG 2.1 AA scan. Results in 60 seconds. No signup required.

Run Free Scan → View Plans from $39/mo