Templates Compliance Regulatory Website Accessibility Audit Checklist - WCAG 2.1 Level AA
Website Accessibility Audit Checklist - WCAG 2.1 Level AA
Ready to Edit

WEBSITE ACCESSIBILITY AUDIT CHECKLIST

WCAG 2.1 Level AA Compliance


AUDIT INFORMATION

Organization Name: _______________________

Website URL(s):

URL Description
_____________________ Primary Website
_____________________ _____________________
_____________________ _____________________

Mobile Application(s) (if applicable):

App Name Platform
_____________________ ☐ iOS ☐ Android
_____________________ ☐ iOS ☐ Android

Organization Type:
☐ Private Business (ADA Title III)
☐ State/Local Government (ADA Title II)
☐ Federal Agency (Section 508)
☐ Healthcare Provider
☐ Financial Institution
☐ Educational Institution
☐ Non-Profit Organization
☐ E-commerce
☐ Other: _______________________


Audit Conducted By: _______________________

Title/Organization: _______________________

Certifications: _______________________

Audit Date: _______________________

Audit Type:
☐ Full WCAG 2.1 AA Compliance Audit
☐ Targeted Assessment
☐ Pre-Litigation Review
☐ Post-Remediation Verification
☐ Annual Review


AUDIT METHODOLOGY

Testing Methods Used:

☐ Automated Testing
- Tools Used: _______________________

☐ Manual Testing
- Screen Reader(s): _______________________
- Browser(s): _______________________

☐ Keyboard-Only Navigation Testing

☐ Color Contrast Analysis

☐ User Testing with People with Disabilities

Assistive Technologies Tested:

☐ JAWS
☐ NVDA
☐ VoiceOver (macOS)
☐ VoiceOver (iOS)
☐ TalkBack (Android)
☐ Dragon NaturallySpeaking
☐ ZoomText
☐ Other: _______________________

Browsers Tested:

☐ Chrome
☐ Firefox
☐ Safari
☐ Edge
☐ Other: _______________________


EXECUTIVE SUMMARY

Overall WCAG 2.1 AA Compliance Status:
☐ Fully Conformant
☐ Substantially Conformant (minor issues)
☐ Partially Conformant (significant issues)
☐ Non-Conformant

Total WCAG Violations Found: _______________________

Critical Issues (Blocking): _______________________

High Priority Issues: _______________________

Medium Priority Issues: _______________________

Low Priority Issues: _______________________

Remediation Timeline Recommendation: _______________________


PRINCIPLE 1: PERCEIVABLE

Information and user interface components must be presentable to users in ways they can perceive.

1.1 Text Alternatives

1.1.1 Non-text Content (Level A)

Requirement: All non-text content has a text alternative that serves the equivalent purpose.

Item Pass Fail N/A Notes
Images have appropriate alt text _____
Decorative images have empty alt (alt="") _____
Complex images have long descriptions _____
Image buttons have descriptive alt text _____
Image maps have appropriate alt text _____
Form image buttons have alt text _____
CAPTCHAs have accessible alternatives _____
Icons have text alternatives _____
SVGs have accessible names _____
Background images with content have alternatives _____

Issues Found:

_____________________________________________________________________________


1.2 Time-Based Media

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Item Pass Fail N/A Notes
Audio-only has text transcript _____
Video-only has text description or audio track _____

1.2.2 Captions (Prerecorded) (Level A)

Item Pass Fail N/A Notes
All prerecorded video with audio has captions _____
Captions are synchronized with video _____
Captions include speaker identification _____
Captions include non-speech audio (music, sounds) _____
Auto-generated captions are reviewed/corrected _____

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Item Pass Fail N/A Notes
Video has audio description OR text alternative _____

1.2.4 Captions (Live) (Level AA)

Item Pass Fail N/A Notes
Live video with audio has real-time captions _____

1.2.5 Audio Description (Prerecorded) (Level AA)

Item Pass Fail N/A Notes
Video content has audio description _____

Issues Found:

_____________________________________________________________________________


1.3 Adaptable

1.3.1 Info and Relationships (Level A)

Item Pass Fail N/A Notes
Headings use proper heading tags (h1-h6) _____
Heading hierarchy is logical _____
Lists use proper list markup (ul, ol, dl) _____
Data tables have proper headers (th) _____
Tables use scope or headers attributes _____
Form fields have associated labels _____
Form field groups use fieldset/legend _____
Required fields are programmatically indicated _____
Landmarks/regions are used appropriately _____
Semantic HTML is used (nav, main, article, etc.) _____

1.3.2 Meaningful Sequence (Level A)

Item Pass Fail N/A Notes
Reading order matches visual presentation _____
DOM order matches visual order _____
CSS does not affect meaningful sequence _____

1.3.3 Sensory Characteristics (Level A)

Item Pass Fail N/A Notes
Instructions don't rely solely on shape _____
Instructions don't rely solely on size _____
Instructions don't rely solely on location _____
Instructions don't rely solely on sound _____

1.3.4 Orientation (Level AA) - WCAG 2.1

Item Pass Fail N/A Notes
Content not restricted to single orientation _____
Both portrait and landscape supported _____

1.3.5 Identify Input Purpose (Level AA) - WCAG 2.1

Item Pass Fail N/A Notes
Input fields have autocomplete attributes _____
Personal data fields are programmatically identifiable _____

Issues Found:

_____________________________________________________________________________


1.4 Distinguishable

1.4.1 Use of Color (Level A)

Item Pass Fail N/A Notes
Color is not the only means of conveying information _____
Links are distinguishable without color alone _____
Form errors indicated by more than color _____
Charts/graphs use patterns or labels with color _____

1.4.2 Audio Control (Level A)

Item Pass Fail N/A Notes
Auto-playing audio can be stopped/paused _____
Volume can be controlled independently _____

1.4.3 Contrast (Minimum) (Level AA)

Item Pass Fail N/A Notes
Normal text: 4.5:1 contrast ratio minimum _____
Large text (18pt+/14pt bold+): 3:1 minimum _____
Placeholder text meets contrast requirements _____

Contrast Test Results:

Element Foreground Background Ratio Pass/Fail
Body text _____ _____ _____ _____
Links _____ _____ _____ _____
Headings _____ _____ _____ _____
Button text _____ _____ _____ _____
Form labels _____ _____ _____ _____
Error messages _____ _____ _____ _____

1.4.4 Resize Text (Level AA)

Item Pass Fail N/A Notes
Text can be resized to 200% without loss _____
No horizontal scrolling at 200% zoom _____
Content remains visible at 200% _____

1.4.5 Images of Text (Level AA)

Item Pass Fail N/A Notes
Real text used instead of images of text _____
Logos are the only images of text (exception) _____

1.4.10 Reflow (Level AA) - WCAG 2.1

Item Pass Fail N/A Notes
Content reflows at 400% zoom (320px width) _____
No horizontal scrolling for vertical content _____
No loss of content or functionality _____

1.4.11 Non-text Contrast (Level AA) - WCAG 2.1

Item Pass Fail N/A Notes
UI components have 3:1 contrast ratio _____
Form field boundaries: 3:1 contrast _____
Focus indicators: 3:1 contrast _____
Icons: 3:1 contrast (if needed to understand) _____
Graphical objects: 3:1 contrast _____

1.4.12 Text Spacing (Level AA) - WCAG 2.1

Item Pass Fail N/A Notes
Line height 1.5x font size supported _____
Paragraph spacing 2x font size supported _____
Letter spacing 0.12x font size supported _____
Word spacing 0.16x font size supported _____
No loss of content with text spacing changes _____

1.4.13 Content on Hover or Focus (Level AA) - WCAG 2.1

Item Pass Fail N/A Notes
Hover/focus content is dismissible (Esc key) _____
Hover content can be hovered over _____
Hover/focus content persists until dismissed _____

Issues Found:

_____________________________________________________________________________


PRINCIPLE 2: OPERABLE

User interface components and navigation must be operable.

2.1 Keyboard Accessible

2.1.1 Keyboard (Level A)

Item Pass Fail N/A Notes
All functionality available via keyboard _____
Links are keyboard accessible _____
Buttons are keyboard accessible _____
Form controls are keyboard accessible _____
Menus/dropdowns work with keyboard _____
Modals/dialogs are keyboard accessible _____
Custom widgets are keyboard accessible _____
Carousels/sliders work with keyboard _____
Date pickers are keyboard accessible _____

2.1.2 No Keyboard Trap (Level A)

Item Pass Fail N/A Notes
No keyboard traps exist _____
Focus can be moved away from all elements _____
Modals can be closed with keyboard _____
Embedded content (iframes) doesn't trap focus _____

2.1.4 Character Key Shortcuts (Level A) - WCAG 2.1

Item Pass Fail N/A Notes
Single character shortcuts can be turned off _____
OR shortcuts can be remapped _____
OR shortcuts only active on focus _____

Issues Found:

_____________________________________________________________________________


2.2 Enough Time

2.2.1 Timing Adjustable (Level A)

Item Pass Fail N/A Notes
Time limits can be turned off _____
OR time limits can be adjusted _____
OR user warned before timeout _____
Session timeout warnings provided _____

2.2.2 Pause, Stop, Hide (Level A)

Item Pass Fail N/A Notes
Auto-moving content can be paused/stopped _____
Auto-updating content can be paused/stopped _____
Carousels have pause mechanism _____
Animations can be stopped _____

Issues Found:

_____________________________________________________________________________


2.3 Seizures and Physical Reactions

2.3.1 Three Flashes or Below Threshold (Level A)

Item Pass Fail N/A Notes
No content flashes more than 3 times/second _____
Flash/blink rates are within safe limits _____

Issues Found:

_____________________________________________________________________________


2.4 Navigable

2.4.1 Bypass Blocks (Level A)

Item Pass Fail N/A Notes
Skip to main content link provided _____
Skip link is visible on focus _____
Skip link is first focusable element _____
Landmark regions used appropriately _____

2.4.2 Page Titled (Level A)

Item Pass Fail N/A Notes
All pages have descriptive titles _____
Titles are unique across site _____
Titles describe page content/purpose _____

2.4.3 Focus Order (Level A)

Item Pass Fail N/A Notes
Focus order is logical and intuitive _____
Focus moves through content meaningfully _____
Modal focus is trapped appropriately _____
Focus returns to trigger after modal close _____

2.4.4 Link Purpose (In Context) (Level A)

Item Pass Fail N/A Notes
Link text describes destination/purpose _____
No generic "click here" or "read more" links _____
Links opening new windows are indicated _____
Links to files indicate file type/size _____

2.4.5 Multiple Ways (Level AA)

Item Pass Fail N/A Notes
Multiple ways to locate pages provided _____
Site has search functionality _____
Site has sitemap _____
Consistent navigation across pages _____

2.4.6 Headings and Labels (Level AA)

Item Pass Fail N/A Notes
Headings describe content below them _____
Form labels are descriptive _____
Section headings are meaningful _____

2.4.7 Focus Visible (Level AA)

Item Pass Fail N/A Notes
Keyboard focus indicator is visible _____
Focus indicator has sufficient contrast _____
Focus indicator not removed via CSS _____
Custom focus styles are visible _____

Issues Found:

_____________________________________________________________________________


2.5 Input Modalities - WCAG 2.1

2.5.1 Pointer Gestures (Level A)

Item Pass Fail N/A Notes
No multipoint gestures required _____
No path-based gestures required _____
Single pointer alternatives available _____

2.5.2 Pointer Cancellation (Level A)

Item Pass Fail N/A Notes
Down-event doesn't trigger actions _____
OR action can be aborted/undone _____
OR up-event reverses down-event _____

2.5.3 Label in Name (Level A)

Item Pass Fail N/A Notes
Visible labels included in accessible names _____
Accessible names start with visible label _____

2.5.4 Motion Actuation (Level A)

Item Pass Fail N/A Notes
Motion-triggered functions have alternatives _____
Motion response can be disabled _____

Issues Found:

_____________________________________________________________________________


PRINCIPLE 3: UNDERSTANDABLE

Information and the operation of user interface must be understandable.

3.1 Readable

3.1.1 Language of Page (Level A)

Item Pass Fail N/A Notes
Page language specified in HTML (lang attribute) _____
Language code is valid (e.g., "en", "es") _____

3.1.2 Language of Parts (Level AA)

Item Pass Fail N/A Notes
Language changes marked with lang attribute _____
Foreign phrases/words properly marked _____

Issues Found:

_____________________________________________________________________________


3.2 Predictable

3.2.1 On Focus (Level A)

Item Pass Fail N/A Notes
Focus doesn't cause unexpected context change _____
No automatic form submission on focus _____
No unexpected navigation on focus _____

3.2.2 On Input (Level A)

Item Pass Fail N/A Notes
Input doesn't cause unexpected context change _____
Form submission requires explicit action _____
Select elements don't auto-submit _____

3.2.3 Consistent Navigation (Level AA)

Item Pass Fail N/A Notes
Navigation order consistent across pages _____
Main menu position consistent _____
Repeated components in same order _____

3.2.4 Consistent Identification (Level AA)

Item Pass Fail N/A Notes
Components with same function labeled consistently _____
Icons used consistently _____
Search function labeled consistently _____

Issues Found:

_____________________________________________________________________________


3.3 Input Assistance

3.3.1 Error Identification (Level A)

Item Pass Fail N/A Notes
Form errors are identified _____
Errors are described in text _____
Error messages identify the field in error _____
Errors are announced to screen readers _____

3.3.2 Labels or Instructions (Level A)

Item Pass Fail N/A Notes
Form fields have visible labels _____
Required fields are indicated _____
Input format instructions provided _____
Labels positioned correctly (before/above input) _____

3.3.3 Error Suggestion (Level AA)

Item Pass Fail N/A Notes
Error messages suggest corrections _____
Specific guidance for fixing errors _____
Examples of valid input provided _____

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Item Pass Fail N/A Notes
Submissions are reversible _____
OR input is checked with correction opportunity _____
OR confirmation mechanism before submission _____
Review step before final submission _____

Issues Found:

_____________________________________________________________________________


PRINCIPLE 4: ROBUST

Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.

4.1 Compatible

4.1.1 Parsing (Level A) - Deprecated in WCAG 2.2

Item Pass Fail N/A Notes
HTML is well-formed _____
No duplicate IDs _____
Elements have complete start/end tags _____
Elements are nested correctly _____

4.1.2 Name, Role, Value (Level A)

Item Pass Fail N/A Notes
Custom controls have accessible names _____
ARIA roles are used correctly _____
ARIA states and properties are accurate _____
aria-expanded states are correct _____
aria-selected states are correct _____
aria-checked states are correct _____

4.1.3 Status Messages (Level AA) - WCAG 2.1

Item Pass Fail N/A Notes
Status messages are announced to screen readers _____
aria-live regions used for dynamic content _____
Alert role used for important messages _____
Success/error messages programmatically conveyed _____

Issues Found:

_____________________________________________________________________________


STATE-SPECIFIC NOTES

CALIFORNIA

  • Unruh Civil Rights Act: Website accessibility violations may trigger Unruh Act claims with $4,000 minimum statutory damages per violation.
  • CCPA Accessibility: California Consumer Privacy Act accessibility requirements may apply.
  • Leading Filing Jurisdiction: California is among the top states for website accessibility lawsuits.

TEXAS

  • Texas Human Resources Code Chapter 121: State disability rights protections.
  • Growing Litigation: Texas has seen increasing web accessibility litigation.
  • DIR Accessibility Standards: Texas state agencies must comply with Texas Department of Information Resources accessibility standards.

FLORIDA

  • High Volume Filing Jurisdiction: Florida ranks among the top states for ADA website lawsuits (487 cases in first half of 2025).
  • Tourism Industry Focus: Significant litigation targeting hospitality and tourism websites.

NEW YORK

  • Highest Filing Volume: New York leads the nation in website accessibility lawsuits (637 cases in first half of 2025).
  • NY Human Rights Law: Permits compensatory damages not available under federal ADA.
  • NYC Human Rights Law: Even broader protections within New York City.
  • Overlay Widget Litigation: Significant litigation against sites using accessibility overlays (22.6% of lawsuits in 2024 targeted sites with overlays).

REMEDIATION PRIORITY MATRIX

Critical (Blocking) - Remediate within 30 days:
- Keyboard traps
- Missing alt text on essential images
- No skip navigation
- Form labels missing
- No video captions
- Severe contrast failures

High Priority - Remediate within 60 days:
- Focus not visible
- Inadequate color contrast
- Missing error messages
- Poor heading structure
- Non-descriptive link text

Medium Priority - Remediate within 90 days:
- Missing language attribute
- Images of text
- Status messages not announced
- Minor ARIA issues
- Text spacing issues

Low Priority - Remediate within 180 days:
- Enhancement opportunities
- Best practice improvements
- Minor label issues


ISSUE LOG

# WCAG Level Page/URL Description Priority Status
1 _____ _____ _____ _____ _____ ☐ Open
2 _____ _____ _____ _____ _____ ☐ Open
3 _____ _____ _____ _____ _____ ☐ Open
4 _____ _____ _____ _____ _____ ☐ Open
5 _____ _____ _____ _____ _____ ☐ Open

CERTIFICATION

This accessibility audit was conducted in accordance with WCAG 2.1 Level AA guidelines and applicable federal and state accessibility requirements.

Auditor Signature: _______________________ Date: _______________________

Printed Name: _______________________

Certifications: _______________________

Organization: _______________________


This template reflects WCAG 2.1 Level AA requirements as of January 2026. The DOJ has adopted WCAG 2.1 Level AA as the standard for Title II entities. Automated testing catches only 30-40% of issues; manual and user testing are essential. Consult current WCAG guidelines and legal counsel for specific compliance requirements.

Ezel AI
Hi! Need help customizing this document? I can tailor every section to your specific case in minutes.
AI Legal Assistant
Ezel AI
Hi! Need help customizing this document? I can tailor every section to your specific case in minutes.

Insert Image

Insert Table

Watch Ezel in action (sample case)

All changes saved
Save
Export
Export as DOCX
Export as PDF
Generating PDF...
website_accessibility_audit_universal.pdf
Ready to export as PDF or Word
AI is editing...
Chat
Review

Customize this document with Ezel

  • Deep Legal Knowledge
    Understands case law, statutes, and legal doctrine.
  • Court-Ready Formatting
    Proper captions, certificates of service, and local rule compliance.
  • AI-Powered Editing on Your Timeline
    Edit as many times as you need. Tailor every section to your specific case.
  • Export as PDF & Word
    Download your finished document in professional PDF or DOCX format, ready to file or send.
Secure checkout via Stripe
Need to customize this document?

About This Template

Jurisdiction-Specific

This template is drafted for general use across all U.S. jurisdictions. State-specific versions with local statutory references are also available.

How It's Made

Drafted using current statutory databases and legal standards for compliance regulatory. Each template includes proper legal citations, defined terms, and standard protective clauses.

Important Notice

This template is provided for informational purposes. It is not legal advice. We recommend having an attorney review any legal document before signing, especially for high-value or complex matters.

Last updated: February 2026