---
# System prepended metadata

title: WCAG 2.1 AA Compliance Checklist for Websites (2026)
tags: [' Accessibility', ' ADA', ' Compliance', WCAG]

---

---
tags: WCAG, Accessibility, ADA, Compliance
---

# WCAG 2.1 AA Compliance Checklist for Websites (2026)
                                                                                                                        
  A practical reference checklist for developers, designers, and business owners to audit web accessibility against WCAG
   2.1 AA — the standard referenced by the U.S. Department of Justice for ADA compliance.

  > **Quick audit:** Run a free automated scan at [WCAGsafe](https://wcagsafe.com) to catch violations instantly.

  ---

  ## 1. Images & Media

  - [ ] All `<img>` tags have descriptive `alt` text
  - [ ] Alt text is not a filename (e.g., `IMG_4021.jpg`) or generic word (e.g., `image`)
  - [ ] Decorative images use `alt=""` (empty, not missing)
  - [ ] Videos have captions (auto-captions alone don't qualify)
  - [ ] Audio content has a transcript
  - [ ] No images of text (except logos)

  ---

  ## 2. Keyboard & Focus

  - [ ] All interactive elements reachable by Tab key
  - [ ] Focus indicator is visible (not removed with `outline: none`)
  - [ ] Logical tab order matches visual layout
  - [ ] No keyboard traps (modal dialogs must be escapable)
  - [ ] Skip navigation link present ("Skip to main content")

  ---

  ## 3. Color & Contrast

  - [ ] Normal text: contrast ratio ≥ 4.5:1
  - [ ] Large text (18pt+ or 14pt bold): contrast ratio ≥ 3:1
  - [ ] UI components and focus rings: contrast ratio ≥ 3:1
  - [ ] Information is not conveyed by color alone (e.g., red = error must also have an icon or text)

  ---

  ## 4. Forms

  - [ ] Every input has a visible `<label>` (not just placeholder text)
  - [ ] Labels are programmatically associated (`for`/`id` or `aria-label`)
  - [ ] Error messages are specific ("Enter a valid email" not just "Error")
  - [ ] `autocomplete` attribute set on personal data fields (email, name, phone)
  - [ ] Required fields are indicated (not by color alone)

  ---

  ## 5. Headings & Structure

  - [ ] Page has exactly one `<h1>`
  - [ ] Headings follow logical order (no jumping from H1 to H4)
  - [ ] Headings describe the section content (not just styled text)
  - [ ] Landmark regions used: `<header>`, `<main>`, `<nav>`, `<footer>`

  ---

  ## 6. Links & Buttons

  - [ ] Link text is descriptive ("Read the ADA compliance guide" not "Click here")
  - [ ] Links that open new tabs warn users (`aria-label="... (opens in new tab)"`)
  - [ ] Buttons have accessible names (not just icons without labels)
  - [ ] No duplicate link text pointing to different destinations

  ---

  ## 7. Page & Navigation

  - [ ] `<html lang="en">` (or appropriate language code) set
  - [ ] Page title (`<title>`) is unique and descriptive per page
  - [ ] Content is readable without horizontal scroll at 320px width
  - [ ] Text can be resized to 200% without loss of content
  - [ ] No content flashes more than 3 times per second

  ---

  ## 8. Touch & Mobile

  - [ ] Touch targets are at least 44×44px (WCAG 2.5.5)
  - [ ] Sufficient spacing between interactive elements
  - [ ] No functionality requires complex gestures (pinch, swipe) without a simpler alternative

  ---

  ## Common Violations That Trigger ADA Lawsuits

  Based on 2024–2025 lawsuit data, the most frequently cited violations are:

  1. Missing or inadequate image alt text
  2. Poor color contrast
  3. Inaccessible forms (missing labels)
  4. No keyboard navigation
  5. Missing skip navigation

  ---

  ## How to Audit Your Site

  **Manual checks:** Use a keyboard only to navigate your site. If you get stuck, something is broken.

  **Screen reader test:** NVDA (Windows, free) or VoiceOver (Mac, built-in).

  **Automated scan:** Automated tools catch ~30–40% of violations. Use [WCAGsafe](https://wcagsafe.com) for a free      
  instant scan — it runs axe-core plus enhanced custom rules and explains each violation in plain English.

  **Note:** A passing automated scan does not guarantee full WCAG conformance. Use it as a starting point, not an       
  endpoint.

  ## Further Reading

  - [ADA Compliance Cost in 2026: What Businesses Actually Pay](https://wcagsafe.com/blog/ada-compliance-cost-2026)     
  - [ADA Compliance Checklist for Small Businesses](https://wcagsafe.com/blog/ada-compliance-checklist-small-business)  
  - [How to Fix WCAG Violations Step by Step](https://wcagsafe.com/blog/how-to-fix-wcag-violations)
  - [ADA Title II Deadline April 2026: What You Need to
  Know](https://wcagsafe.com/blog/ada-title-ii-deadline-april-2026)
  - [ADA Lawsuit Statistics 2024](https://wcagsafe.com/blog/ada-lawsuit-statistics)
  
  ---

  ## Useful Resources

  - [WebAIM Contrast Checker](https://webaim.org/resources/contrastchecker/)
  - [WCAG 2.1 Quick Reference](https://www.w3.org/WAI/WCAG21/quickref/)
  - [DOJ ADA Web Guidance (2022)](https://www.ada.gov/resources/web-guidance/)
  - [WCAGsafe Free Scanner](https://wcagsafe.com) — automated WCAG 2.1 AA audit
