Skip to main content
Perceivly: Perceivly home

1.3.3 Sensory Characteristics

Level A · added in WCAG 2.0

Instructions must not depend only on how something looks, where it sits or how it sounds. "Press the round button on the right" fails unless the instruction also names the button.

Who it helps

Blind people can't see shape or position, and layouts shift on small screens and at high zoom. Deaf people can't hear a sound cue, and people with cognitive disabilities benefit from clear, named references.

How to meet it

Examples

Fails:An instruction that depends on shape and position
<p>When you're ready, press the round button on the right.</p>
<button class="round-btn" aria-label="Place order">&rarr;</button>
Fails:An instruction that depends only on a sound
<p>Start the test when you hear the tone.</p>
<audio id="start-tone" src="/sounds/start.mp3"></audio>
Passes:The instruction names the button's visible label
<p>When you're ready, select <strong>Place order</strong>.</p>
<button class="round-btn">Place order</button>
Passes:The sound cue is paired with a visible status message
<p>Start the test when you hear the tone or see "Go" below.</p>
<audio id="start-tone" src="/sounds/start.mp3"></audio>
<p id="test-status" role="status"></p>

Can a scanner detect this?

No

No axe-core rule tests this criterion, because a script can't understand what instructions mean. Read every instruction on the page and ask whether someone who can't see the layout, or hear the audio, could still follow it.

No automated rule tests this criterion. Check it by hand.

Common mistakes

Official W3C explanation of 1.3.3

Check your own page

See which automated WCAG checks your page fails, with the failing elements and how to fix them.

Enter a page address, for example example.com/shop.

Reviewed November 2, 2026