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.

Filters

Level

Remove filter
  • Level A + AA (PSBAR)

Theme

Remove filter
  • Forms

13 success criteria found for Level A + AA and Forms theme

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 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.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.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.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 1.3.5 Identify Input Purpose [2.1 and 2.2]

Level Level AA, WCAG principle: Perceivable

Assigned to the following themes: FORMS

The purpose of common form fields (like name, email, or address) must be defined in the code so that browsers and assistive technologies can offer input support, such as autocomplete.

Success criterion 3.3.3 Error Suggestion

Level Level AA, WCAG principle: Understandable

Assigned to the following themes: FORMS WORDING

Errors and validation messages must show text that:

  • explains the problem and
  • gives suggestions for how to fix it (like "enter at least 8 characters")

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