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.

16 success criteria found for Code and labels theme

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.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 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.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 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.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.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 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.

Success criterion 2.4.6 Headings and Labels

Level Level AA, WCAG principle: Operable

Assigned to the following themes: CODE AND LABELS WORDING

Headings must describe what follows.

Labels and buttons must clearly communicate what information is needed or what action will happen.

Success criterion 3.1.2 Language of Parts

Level Level AA, WCAG principle: Understandable

Assigned to the following themes: CODE AND LABELS WORDING

Any parts of the content in a different language must be marked with the correct lang attribute.

Expressions borrowed from another language (like "déjà vu" in English) do not need this, unless pronunciation or understanding would be affected.

Success criterion 4.1.3 Status Messages [2.1 and 2.2]

Level Level AA, WCAG principle: Robust

Assigned to the following themes: CODE AND LABELS FORMS

Status updates (like "form sent" or "5 items in cart") must:

  • be coded using proper roles (like role="status" or role="alert"),
  • be detectable by assistive technologies, and
  • not require moving focus

Success criterion 2.4.10 Section Headings

Level Level AAA, WCAG principle: Operable

Assigned to the following themes: CODE AND LABELS

Related content must be organized into clear sections using headings.

Success criterion 2.4.9 Link Purpose (Link Only)

Level Level AAA, WCAG principle: Operable

Assigned to the following themes: CODE AND LABELS WORDING

The purpose of each link must be clear:

  • from the link text alone
  • without relying on surrounding context.