Skip to main content
Accessibility Field Guide

WCAG 2.1 A/AA Map

A plain-language orientation map for the 50 WCAG 2.1 Level A and AA success criteria, grouped by principle.

Documents spread out on a table.
Photo: Documents on a Table via Pexels — https://www.pexels.com/photo/documents-on-a-table-7731348/
View full screen Download image

WCAG can be hard to approach if you start with the standard first.

The language is precise for a reason, but precise does not always mean easy to learn from. If you are new to accessibility, a criterion number like 2.4.7 may not tell you what to look for on a real screen, what question to ask in a meeting, or what issue might create rework later.

This map is here to help.

It gives every WCAG 2.1 Level A and AA success criterion a place in the Accessibility Field Guide.

That scope matters. WCAG 2.1 includes 78 success criteria across Levels A, AA, and AAA. This map covers the 50 criteria needed for Level A/AA orientation and intentionally leaves Level AAA criteria out of the main map.

The goal is not to replace the official standard.

The goal is to connect the standard to plain-language explanations, practical topics, examples, checklists, roles, and skill tree branches.

How to use this map

Use this page when:

  • you know a WCAG number and want to understand the practical issue
  • you want to see how a topic connects to the standard
  • you are planning collection coverage
  • you are following a campaign post and want the deeper trail markers
  • you want to understand what WCAG 2.1 A/AA covers overall

Coverage check for this page:

  • Perceivable: 20 Level A/AA criteria
  • Operable: 17 Level A/AA criteria
  • Understandable: 10 Level A/AA criteria
  • Robust: 3 Level A/AA criteria
  • Total: 50 WCAG 2.1 Level A/AA success criteria

Each criterion page should eventually answer:

  • What does this mean in plain language?
  • Why does it matter?
  • What are common trail hazards?
  • Who should pay attention to it?
  • What topics, examples, and checklists connect to it?
  • What should teams ask earlier?

The four WCAG principles

WCAG is organized around four broad principles.

Perceivable

People need to be able to perceive the information.

That includes text alternatives, captions, structure, contrast, zoom, reflow, and making sure information is not only communicated through color, sound, shape, or position.

Operable

People need to be able to operate the interface.

That includes keyboard access, focus order, avoiding traps, giving people enough time, avoiding flashing content, and helping people navigate.

Understandable

People need to be able to understand the content and what will happen.

That includes page language, predictable behavior, consistent navigation, labels, instructions, and error recovery.

Robust

The interface needs to work with current and future user agents and assistive technologies.

That includes valid structure, accessible names, roles, values, and status messages.

Perceivable criteria

1.1 Text Alternatives

  • 1.1.1 Non-text Content (Level A) — Images, icons, charts, controls, and other non-text content need appropriate alternatives.

1.2 Time-based Media

  • 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) — Prerecorded audio-only or video-only content needs an alternative.
  • 1.2.2 Captions (Prerecorded) (Level A) — Prerecorded video with audio needs captions.
  • 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) — Prerecorded video needs audio description or another media alternative when visual information matters.
  • 1.2.4 Captions (Live) (Level AA) — Live audio in synchronized media needs captions.
  • 1.2.5 Audio Description (Prerecorded) (Level AA) — Prerecorded video needs audio description when important visual information is not available in the audio.

1.3 Adaptable

  • 1.3.1 Info and Relationships (Level A) — Visual structure and relationships need to be available programmatically.
  • 1.3.2 Meaningful Sequence (Level A) — Content needs to make sense in a meaningful reading order.
  • 1.3.3 Sensory Characteristics (Level A) — Instructions should not rely only on shape, color, size, visual location, orientation, or sound.
  • 1.3.4 Orientation (Level AA) — Content should not require a single screen orientation unless that orientation is essential.
  • 1.3.5 Identify Input Purpose (Level AA) — Common input fields should expose their purpose so browsers and assistive technologies can help users.

1.4 Distinguishable

  • 1.4.1 Use of Color (Level A) — Color should not be the only way information is conveyed.
  • 1.4.2 Audio Control (Level A) — Audio that plays automatically for more than three seconds needs a way to pause, stop, or control it.
  • 1.4.3 Contrast (Minimum) (Level AA) — Text needs enough contrast against its background.
  • 1.4.4 Resize Text (Level AA) — Text should resize up to 200 percent without loss of content or functionality.
  • 1.4.5 Images of Text (Level AA) — Avoid using images of text when real text can do the job.
  • 1.4.10 Reflow (Level AA) — Content should reflow at narrow widths without forcing two-direction scrolling for most content.
  • 1.4.11 Non-text Contrast (Level AA) — Important UI components and graphical objects need enough contrast.
  • 1.4.12 Text Spacing (Level AA) — Content should remain usable when users adjust text spacing.
  • 1.4.13 Content on Hover or Focus (Level AA) — Content that appears on hover or focus needs to be dismissible, hoverable, and persistent when appropriate.

Operable criteria

2.1 Keyboard Accessible

  • 2.1.1 Keyboard (Level A) — Functionality should be available from a keyboard.
  • 2.1.2 No Keyboard Trap (Level A) — Keyboard users should not get trapped in part of the page.
  • 2.1.4 Character Key Shortcuts (Level A) — Single-character shortcuts need safeguards so they do not interfere with users.

2.2 Enough Time

  • 2.2.1 Timing Adjustable (Level A) — Users need ways to turn off, adjust, or extend time limits unless an exception applies.
  • 2.2.2 Pause, Stop, Hide (Level A) — Moving, blinking, scrolling, or auto-updating content needs controls when it could distract or interfere.

2.3 Seizures and Physical Reactions

  • 2.3.1 Three Flashes or Below Threshold (Level A) — Content should not flash in a way that exceeds the threshold.

2.4 Navigable

  • 2.4.1 Bypass Blocks (Level A) — Users need a way to bypass repeated content.
  • 2.4.2 Page Titled (Level A) — Pages need titles that describe their topic or purpose.
  • 2.4.3 Focus Order (Level A) — Focus should move in an order that preserves meaning and operability.
  • 2.4.4 Link Purpose (In Context) (Level A) — Link purpose should be clear from the link text or its context.
  • 2.4.5 Multiple Ways (Level AA) — Users need more than one way to find pages within a set of pages, unless an exception applies.
  • 2.4.6 Headings and Labels (Level AA) — Headings and labels should describe topic or purpose.
  • 2.4.7 Focus Visible (Level AA) — Keyboard focus needs to be visible.

2.5 Input Modalities

  • 2.5.1 Pointer Gestures (Level A) — Multipoint or path-based gestures need a single-pointer alternative unless essential.
  • 2.5.2 Pointer Cancellation (Level A) — Pointer actions should be designed so users can avoid accidental activation.
  • 2.5.3 Label in Name (Level A) — The accessible name should include the visible label text.
  • 2.5.4 Motion Actuation (Level A) — Functionality triggered by device or user motion needs an alternative and a way to disable accidental activation.

Understandable criteria

3.1 Readable

  • 3.1.1 Language of Page (Level A) — The default language of the page should be identified.
  • 3.1.2 Language of Parts (Level AA) — Changes in language should be identified when needed.

3.2 Predictable

  • 3.2.1 On Focus (Level A) — Moving focus to something should not unexpectedly change context.
  • 3.2.2 On Input (Level A) — Changing a field value should not unexpectedly change context unless users are warned.
  • 3.2.3 Consistent Navigation (Level AA) — Repeated navigation should appear in a consistent order.
  • 3.2.4 Consistent Identification (Level AA) — Components with the same function should be identified consistently.

3.3 Input Assistance

  • 3.3.1 Error Identification (Level A) — Input errors should be identified and described in text.
  • 3.3.2 Labels or Instructions (Level A) — Users need labels or instructions when content requires input.
  • 3.3.3 Error Suggestion (Level AA) — When possible, users should get suggestions for fixing input errors.
  • 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) — Important submissions need safeguards such as review, confirmation, reversibility, or checking.

Robust criteria

4.1 Compatible

  • 4.1.1 Parsing (Level A) — Markup should be structured in a way user agents and assistive technologies can parse reliably.
  • 4.1.2 Name, Role, Value (Level A) — User interface components need accessible names, roles, states, and values.
  • 4.1.3 Status Messages (Level AA) — Status messages should be available to assistive technologies without moving focus.

How this connects to the Field Guide

Each criterion should eventually link to:

  • a plain-language criterion page
  • one or more topic field notes
  • examples or spot-the-issue cards
  • relevant checklists
  • role guidance
  • skill tree branches
  • campaign months where the topic may appear

For example:

  • 2.4.7 Focus Visible connects to keyboard and focus, visual conditions, QA checks, and examples of missing or low-contrast focus indicators.
  • 3.3.1 Error Identification connects to forms and errors, content clarity, QA form checks, and before/after error message examples.
  • 4.1.2 Name, Role, Value connects to components, ARIA, accessible names, custom widgets, and developer/QA guidance.

What is not included here

This page is focused on Level A and Level AA because that is the working scope for this Field Guide map.

WCAG 2.1 also includes Level AAA success criteria. Those are useful to know about, but they are not part of this first A/AA map:

  • 1.2.6 Sign Language (Prerecorded)
  • 1.2.7 Extended Audio Description (Prerecorded)
  • 1.2.8 Media Alternative (Prerecorded)
  • 1.2.9 Audio-only (Live)
  • 1.3.6 Identify Purpose
  • 1.4.6 Contrast (Enhanced)
  • 1.4.7 Low or No Background Audio
  • 1.4.8 Visual Presentation
  • 1.4.9 Images of Text (No Exception)
  • 2.1.3 Keyboard (No Exception)
  • 2.2.3 No Timing
  • 2.2.4 Interruptions
  • 2.2.5 Re-authenticating
  • 2.2.6 Timeouts
  • 2.3.2 Three Flashes
  • 2.3.3 Animation from Interactions
  • 2.4.8 Location
  • 2.4.9 Link Purpose (Link Only)
  • 2.4.10 Section Headings
  • 2.5.5 Target Size
  • 2.5.6 Concurrent Input Mechanisms
  • 3.1.3 Unusual Words
  • 3.1.4 Abbreviations
  • 3.1.5 Reading Level
  • 3.1.6 Pronunciation
  • 3.2.5 Change on Request
  • 3.3.5 Help
  • 3.3.6 Error Prevention (All)

A note about the official standard

This map is an orientation tool.

For formal requirements, always refer back to the official WCAG documentation and any applicable review process.

The Field Guide helps explain the trail.

The standard is still the map of record.

Practical Field Guide pages for common criteria

Use these pages when a WCAG criterion points to a practical design, content, or QA question:

  • Accessibility Glossary — for plain-language definitions of common accessibility terms used across this guide.

What to do next