Skip to main content
Skip to results

WCAG Explorer (beta)

This resource is designed for anyone eager to master digital accessibility. Explore WCAG success criteria through clear, easy-to-understand descriptions. We owe a special "hat tip" to Johannes Lehner’s WCAG Card Deck, which served as the inspiration for this project.

We plan to expand this library over time, so please check back regularly for updates.

32 success criteria found for Level A

Success criterion 1.1.1 Non-text Content

Level Level A, WCAG principle: Perceivable

Assigned to the following themes: CODE AND LABELS SENSORY WORDING

All images and other non-text content (like icons, charts, audio, CAPTCHAs, or controls) must have a descriptive text alternative that conveys their meaning. Purely decorative content can be hidden from assistive technologies (e.g. using an empty alt attribute).

Success criterion 1.2.2 Captions (Prerecorded)

Level Level A, WCAG principle: Perceivable

Assigned to the following themes: SENSORY WORDING

Prerecorded videos with audio must have synchronised captions that include:

  • all speech and
  • relevant sound effects (like music, alarms, or laughter)

Success criterion 1.3.1 Info and Relationships

Level Level A, WCAG principle: Perceivable

Assigned to the following themes: CODE AND LABELS WORDING

Visual information and relationships (like labels, headings, or groupings) must also be conveyed in the code using:

  • semantic HTML (e.g. <label for="">, <ul>, <h1>), or
  • ARIA attributes (e.g. aria-describedby, role="group"),

so that assistive technologies can understand the structure.

Success criterion 1.3.2 Meaningful Sequence

Level Level A, WCAG principle: Perceivable

Assigned to the following themes: CODE AND LABELS WORDING

Content must follow a logical and meaningful order in the code so it can be understood correctly by assistive technologies even if the visual layout differs.

Success criterion 1.3.3 Sensory Characteristics

Level Level A, WCAG principle: Perceivable

Assigned to the following themes: FORMS SENSORY WORDING

Instructions and descriptions must not rely on sensory features alone, like color, shape, size, visual location, or sound.

Always provide additional text to clarify meaning.

Success criterion 1.4.1 Use of Color

Level Level A, WCAG principle: Perceivable

Assigned to the following themes: SENSORY

Colour must not be the only way to convey information.

Always provide an additional visual cue, like icon, text label, underline, shape, or pattern (e.g. striped, solid).

Success criterion 1.4.2 Audio Control

Level Level A, WCAG principle: Perceivable

Assigned to the following themes: SENSORY

If audio plays automatically for more than 3 seconds, it must be possible to:

  • pause the audio,
  • stop the audio, or
  • adjust the volume,

without using system-wide controls.

Success criterion 2.1.1 Keyboard

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

All functionality must be operable using a keyboard alone, unless the task requires freehand input (e.g. drawing).

Success criterion 2.1.2 No Keyboard Trap

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

It must always be possible to move focus into and out of any component using a keyboard alone (e.g. [tab], [shift]+[tab], [enter], [esc]), without getting stuck.

Success criterion 2.1.4 Character Key Shortcuts [2.1 and 2.2]

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

Keyboard shortcuts should use modifier keys like [ctrl], [cmd], or [alt/option]. If single-key shortcuts are used (e.g. 'S' for save), it must be possible to:

  • turn them off,
  • remap them with a modifier key, or
  • restrict them to when the relevant element is focused

Success criterion 2.2.1 Timing Adjustable

Level Level A, WCAG principle: Operable

Assigned to the following themes: FORMS SENSORY

Time limits must be avoided unless essential for the task (e.g. exams, auctions). If time limits are used, it must be possible to:

  • turn them off,
  • adjust them to at least 10× the default, or
  • extend them by at least 10×.

Success criterion 2.2.2 Pause, Stop, Hide

Level Level A, WCAG principle: Operable

Assigned to the following themes: SENSORY

If content moves, scrolls, blinks, or updates automatically for more than 5 seconds, it must be possible to:

  • pause it,
  • stop it, or
  • hide it

Success criterion 2.3.1 Three Flashes or Below Threshold

Level Level A, WCAG principle: Operable

Assigned to the following themes: SENSORY

Content must not flash, blink, or flicker more than three times per second, unless it stays within safety limits designed to avoid visual overload and reduce the risk of seizures.

Success criterion 2.4.1 Bypass Blocks

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

It must be possible to skip repeated blocks of content (e.g. navigation, header) and jump directly to the main part of the page.

Success criterion 2.4.2 Page Titled

Level Level A, WCAG principle: Operable

Assigned to the following themes: CODE AND LABELS WHOLE SITE WORDING

Each page must have a unique and descriptive <title> that reflects its topic or purpose.

Success criterion 2.4.3 Focus Order

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

Focus must follow a logical and meaningful order that preserves relationships and matches how the page is naturally read, regardless of layout or language direction.

Success criterion 2.5.3 Label in Name [2.1 and 2.2]

Level Level A, WCAG principle: Operable

Assigned to the following themes: CODE AND LABELS FORMS

The visible text of a button, link, or form field must also be part of its accessible (programmatic) name.

Success criterion 2.5.4 Motion Actuation [2.1 and 2.2]

Level Level A, WCAG principle: Operable

Assigned to the following themes: GESTURES

If an action can be triggered by motion (like shaking or tilting the device), it must also:

  • work without motion, and
  • be possible to turn off motion-based input

Success criterion 3.1.1 Language of Page

Level Level A, WCAG principle: Understandable

Assigned to the following themes: CODE AND LABELS WORDING

Each page must have a <html lang=""> attribute that matches the main language of the page.

Success criterion 3.2.1 On Focus

Level Level A, WCAG principle: Understandable

Assigned to the following themes: KEYBOARD

No unexpected changes must happen when an element receives focus (like open a popup, move focus, submit a form).

Success criterion 3.2.2 On Input

Level Level A, WCAG principle: Understandable

Assigned to the following themes: CODE AND LABELS FORMS KEYBOARD

No unexpected changes must happen when a field value changes (like auto-submit, reload, open new page).

Success criterion 3.3.1 Error Identification

Level Level A, WCAG principle: Understandable

Assigned to the following themes: FORMS WORDING

Errors and validation must be clearly identified and described in text, not just visually (like color or highlighting).

Success criterion 3.3.2 Labels or Instructions

Level Level A, WCAG principle: Understandable

Assigned to the following themes: CODE AND LABELS FORMS

Form fields must have clear labels or instructions to avoid confusion and help complete the input correctly.

Success criterion 3.3.7 Redundant Entry (2.2 only)

Level Level A, WCAG principle: Understandable

Assigned to the following themes: FORMS

Don't ask for the same information twice in the same process.

Provide pre-filled fields or selection options if the information was already given.

Success criterion 4.1.1 Parsing [Obsolete]

Level Level A, WCAG principle: Robust

Assigned to the following themes: CODE AND LABELS

This used to require HTML with proper structure and no critical markup errors (like missing tags or duplicate IDs).
The requirement is removed but still helps with compatibility.

Success criterion 4.1.2 Name, Role, Value

Level Level A, WCAG principle: Robust

Assigned to the following themes: CODE AND LABELS FORMS KEYBOARD

Interactive elements must have:

  • a clear name (what it is),
  • the correct role (what it does), and
  • any current value or state,

so that assistive technologies can interpret and interact with them correctly.