Loading Developer Playground

Loading ...

Skip to main content
Developer Playground
Share:
Back to WCAG Explorer

Success Criterion · WCAG 3.3.5

Help

Context-sensitive help is available.

Level AAAWCAG 2.0Understandable3.3 · Input Assistance
Copy button ready

Success criterion

What WCAG 3.3.5 requires

Summarized directly from the official Understanding document so teams can quote the requirement accurately.

All non-text content that is presented to users must expose an equivalent text-based alternative unless a documented exception applies.

View Understanding 3.3.5Open QuickRef techniques

Fast facts

Conformance level
Level AAA
WCAG version introduced
WCAG 2.0
Principle
Understandable
Guideline
3.3 · Input Assistance

Implementation checklist

Capture progress and blockers

  • Document how this criterion impacts your product and note any exceptions.
  • Describe the user experience goal in plain language for designers and engineers.
  • List the components, templates, or workflows that must meet this requirement.
  • Capture manual and automated testing steps for future audits.

Testing ideas

Prove conformance with evidence

  • Pair automated linting with human review to verify visual, auditory, or temporal aspects.
  • Use assistive technology walkthroughs (screen reader, keyboard, switch, voice) to validate behavior.
  • Capture screenshots or recordings that demonstrate pass/fail conditions.

Related success criteria

More from Input Assistance (3.3)

View all criteria
WCAG 3.3.1Error IdentificationLevel AWCAG 3.3.2Labels or InstructionsLevel AWCAG 3.3.3Error SuggestionLevel AAWCAG 3.3.4Error Prevention (Legal, Financial, Data)Level AAWCAG 3.3.6Error Prevention (All)Level AAAWCAG 3.3.7Redundant EntryLevel AWCAG 3.3.8Accessible Authentication (Minimum)Level AAWCAG 3.3.9Accessible Authentication (Enhanced)Level AAA
Back to WCAG Explorer