Loading Developer Playground

Loading ...

Skip to main content

Success Criterion · WCAG 1.3.3

Sensory Characteristics

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.

Level AWCAG 2.0Perceivable1.3 · Adaptable
Copy button ready

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

What WCAG 1.3.3 requires

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

Why WCAG created this requirement

  • Sensory-only instructions (shape, color, size, location, sound) exclude users who cannot perceive those characteristics.
  • Color-blind users cannot follow instructions like "click the red button."
  • Screen reader users cannot locate "the button on the left" since they do not perceive visual position.
  • Instructions should include text labels, names, or other non-sensory identifiers.

Benefits

Who gains when you pass

  • Color-blind users can follow instructions when color is not the only identifier.
  • Blind users can follow instructions when location is supplemented with names or labels.
  • Users with low vision who may not perceive shapes clearly can use text identifiers.
  • Deaf users can follow instructions when sound cues are supplemented with visual/text alternatives.
  • Users accessing content in different layouts (mobile, zoomed) benefit from label-based instructions.

Why it matters

User impact when this criterion fails

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.

Overview

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.

  • Supplement color references with text: "Click the green Submit button" includes both color and label.
  • Supplement location references with names: "In the sidebar menu, click Settings" includes location and name.
  • Supplement shape references with labels: "Click the circular Help icon" or better "Click Help."
  • Supplement sound cues with visual indicators: "A tone will play and the screen will show Complete."
  • Using multiple characteristics (color AND label) is acceptable; using ONLY sensory characteristics is not.

Reference: All summaries and highlights originate from Understanding WCAG 1.3.3 and the W3C quick reference.

Fast facts

Conformance level
Level A
WCAG version introduced
WCAG 2.0
Principle
Perceivable
Guideline
1.3 · Adaptable

Examples

Make success tangible for teams

Share pass/fail snapshots to coach designers, engineers, QA, and content authors.

Color reference

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)

Position reference

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)

Shape reference

Pass

"Click the circular Help icon (?) in the toolbar." (Includes shape AND label)

Fail

"Click the round button." (Shape alone may not be perceivable)

Sound reference

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

Document conformance decisions

Capture artifacts for VPATs, procurement reviews, and regression testing.

  • Include sensory characteristics guidelines in content style guides.
  • Document examples of compliant vs. non-compliant instructional text.
  • Create a checklist for content authors to verify instructions.
  • Track and remediate existing sensory-only instructions across the site.

Official resources

Deep dives and supporting material

Keep these links handy when writing acceptance criteria or responding to audits.

Implementation checklist

Capture progress and blockers

  • Audit all instructional text for sensory-only references (color, shape, size, position, sound).
  • Add text labels or names to any instruction that references color ("the red Cancel button").
  • Add element names to any instruction that references location ("in the left sidebar, click Profile Settings").
  • Ensure shape references include accessible labels ("click the gear icon labeled Settings").
  • Supplement audio cues with visual or text alternatives.
  • Test instructions by removing sensory characteristics—can users still understand which element is meant?
  • Include this requirement in content authoring guidelines.

Testing ideas

Prove conformance with evidence

  • Search content for sensory keywords: color names, "left," "right," "above," "below," "round," "square," etc.
  • For each sensory reference, verify additional non-sensory identifying information is provided.
  • Test with grayscale or a color blindness simulator—can instructions still be followed?
  • Use a screen reader and verify instructions make sense without visual perception.
  • Verify audio-based instructions have non-audio alternatives.
  • Have users unfamiliar with the interface attempt to follow instructions to identify unclear references.

Related success criteria

More from Adaptable (1.3)

View all criteria