Principle 1: Perceivable
Information and user interface components must be presentable to users in ways they can perceive. This means content must be available to at least one of their senses.
1.1.1 Non-text Content (A): All non-text content has text alternatives that serve the same purpose
1.2.1 Audio-only and Video-only (A): Alternatives provided for prerecorded audio-only and video-only content
1.2.2 Captions (Prerecorded) (A): Captions provided for all prerecorded audio content in synchronized media
1.2.3 Audio Description or Media Alternative (A): Alternative or audio description provided for prerecorded video
1.2.4 Captions (Live) (AA): Captions provided for all live audio content in synchronized media
1.2.5 Audio Description (Prerecorded) (AA): Audio description provided for all prerecorded video content
1.3.1 Info and Relationships (A): Information and relationships conveyed through presentation can be programmatically determined
1.3.2 Meaningful Sequence (A): Correct reading sequence can be programmatically determined
1.3.3 Sensory Characteristics (A): Instructions don't rely solely on sensory characteristics
1.3.4 Orientation (AA): Content not restricted to single display orientation
1.3.5 Identify Input Purpose (AA): Input field purposes can be programmatically determined
1.4.1 Use of Color (A): Color is not the only visual means of conveying information
1.4.2 Audio Control (A): Mechanism to pause or stop audio that plays automatically
1.4.3 Contrast (Minimum) (AA): Text has contrast ratio of at least 4.5:1 (3:1 for large text)
1.4.4 Resize Text (AA): Text can be resized up to 200% without loss of content or functionality
1.4.5 Images of Text (AA): Text used rather than images of text where possible
1.4.10 Reflow (AA): Content can reflow without horizontal scrolling at 320px width
1.4.11 Non-text Contrast (AA): UI components and graphics have 3:1 contrast ratio
1.4.12 Text Spacing (AA): No loss of content when text spacing is adjusted
1.4.13 Content on Hover or Focus (AA): Additional content appearing on hover/focus is dismissible, hoverable, and persistent
Principle 2: Operable
User interface components and navigation must be operable. Users must be able to operate the interface regardless of the input method they use.
2.1.1 Keyboard (A): All functionality available from keyboard
2.1.2 No Keyboard Trap (A): Keyboard focus can be moved away from any component
2.1.4 Character Key Shortcuts (A): Single-key shortcuts can be turned off or remapped
2.2.1 Timing Adjustable (A): Time limits can be turned off, adjusted, or extended
2.2.2 Pause, Stop, Hide (A): Moving, blinking, scrolling, or auto-updating content can be controlled
2.3.1 Three Flashes or Below (A): No content flashes more than three times per second
2.4.1 Bypass Blocks (A): Mechanism to bypass blocks of repeated content
2.4.2 Page Titled (A): Pages have descriptive titles
2.4.3 Focus Order (A): Focus order preserves meaning and operability
2.4.4 Link Purpose (In Context) (A): Link purpose determinable from link text or context
2.4.5 Multiple Ways (AA): More than one way to locate pages within a site
2.4.6 Headings and Labels (AA): Headings and labels describe topic or purpose
2.4.7 Focus Visible (AA): Keyboard focus indicator is visible
2.5.1 Pointer Gestures (A): Multi-point or path-based gestures have alternatives
2.5.2 Pointer Cancellation (A): Single-pointer functions can be cancelled
2.5.3 Label in Name (A): Accessible name contains visible label text
2.5.4 Motion Actuation (A): Motion-triggered functions have alternatives and can be disabled
Principle 3: Understandable
Information and the operation of the user interface must be understandable. Content must be readable and predictable, with input assistance provided.
3.1.1 Language of Page (A): Default language of page is programmatically determined
3.1.2 Language of Parts (AA): Language of parts differing from page language is identified
3.2.1 On Focus (A): Components don't change context when receiving focus
3.2.2 On Input (A): Changing settings doesn't cause change of context unless user is advised
3.2.3 Consistent Navigation (AA): Navigation mechanisms occur in same relative order
3.2.4 Consistent Identification (AA): Components with same function are identified consistently
3.3.1 Error Identification (A): Input errors are identified and described to user
3.3.2 Labels or Instructions (A): Labels or instructions provided for user input
3.3.3 Error Suggestion (AA): Suggestions provided when input errors are detected
3.3.4 Error Prevention (Legal, Financial, Data) (AA): Submissions are reversible, verified, or confirmed
Principle 4: Robust
Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.
4.1.2 Name, Role, Value (A): All UI components have accessible name and role; states and values are programmatically set
4.1.3 Status Messages (AA): Status messages can be programmatically determined without receiving focus
How to Use This Checklist
This checklist covers all WCAG 2.1 Level A and AA success criteria. Work through each criterion systematically, testing each page template and major feature. Use automated testing tools like A11yScan for approximately 30% of criteria, but remember that most criteria require manual testing. Document your testing methodology and results for each criterion.