Goal
Ensure instructions do not rely solely on sensory characteristics like shape, color, size, or location.
Loading ...
Success Criterion · WCAG 1.3.3
Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.
Goal
Ensure instructions do not rely solely on sensory characteristics like shape, color, size, or location.
What to do
Provide instructions that use text labels or names in addition to any sensory references.
Why it matters
Users who cannot perceive shape, color, size, or visual location need alternative ways to understand instructions.
Success criterion
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, or sound.
Intent
Benefits
Why it matters
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Color-blind users cannot distinguish "green button" from "red button" based on color alone.
Screen reader users cannot locate "the link on the right side" since position is not announced.
Users with low vision may not perceive shapes or relative sizes.
Deaf users cannot respond to sound-only instructions ("when you hear the beep").
Mobile users in different layouts may not see elements in the described position.
When giving users instructions, do not rely exclusively on sensory characteristics like "click the green button," "select the option on the right," or "press the round icon." Some users cannot perceive color, shape, visual location, or sound. Instructions should include identifying information that does not depend on sensory perception, such as the button's text label or the element's name.
Reference: All summaries and highlights originate from Understanding WCAG 1.3.3 and the W3C quick reference.
Examples
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Pass
"Click the green Submit button to save your changes." (Includes color AND button name)
Fail
"Click the green button." (Color alone does not identify which button for color-blind users)
Pass
"Select Settings from the menu on the left." (Includes name AND position)
Fail
"Click the link on the right." (Position alone does not help screen reader users)
Pass
"Click the circular Help icon (?) in the toolbar." (Includes shape AND label)
Fail
"Click the round button." (Shape alone may not be perceivable)
Pass
"When the process completes, a tone will sound and the status will display Complete." (Sound AND visual)
Fail
"When you hear the beep, proceed to the next step." (Sound-only instruction)
Evidence to keep
Capture artifacts for VPATs, procurement reviews, and regression testing.
Official resources
Keep these links handy when writing acceptance criteria or responding to audits.
Official W3C interpretation, techniques, and intent for Sensory Characteristics.
Filterable list of sufficient techniques and failures.
Providing textual identification of items that otherwise rely only on sensory information.
Failure due to identifying content only by its shape or location.
Failure due to using a graphical symbol alone to convey information.
Implementation checklist
Testing ideas
Related success criteria