Loading Developer Playground

Loading ...

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

Success Criterion · WCAG 1.3.5

Identify Input Purpose

The purpose of each input field collecting information about the user can be programmatically determined when the input field serves a purpose identified in the Input Purposes for User Interface Components section and the content is implemented using technologies with support for identifying the expected meaning for form input data.

Level AAWCAG 2.1Perceivable1.3 · Adaptable
Copy button ready

Success criterion

What WCAG 1.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 1.3.5Open QuickRef techniques

Fast facts

Conformance level
Level AA
WCAG version introduced
WCAG 2.1
Principle
Perceivable
Guideline
1.3 · Adaptable

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 Adaptable (1.3)

View all criteria
WCAG 1.3.1Info and RelationshipsLevel AWCAG 1.3.2Meaningful SequenceLevel AWCAG 1.3.3Sensory CharacteristicsLevel AWCAG 1.3.4OrientationLevel AAWCAG 1.3.6Identify PurposeLevel AAA
Back to WCAG Explorer