WCAG Guideline 1.3.3: Sensory Characteristics Explained

Estimated read time: 8–10 minutes


Guideline 1: Perceivable

The first principle of WCAG, Perceivable, ensures that information and user interface components must be presented to users in ways they can perceive. This means content can’t be invisible to all of a user’s senses—whether they are seeing, hearing, or feeling the content through assistive technology.

Guideline 1.3: Adaptable

Guideline 1.3 focuses on creating content that can be presented in different ways (for example, simpler layout) without losing information or structure. This is essential for users who rely on assistive technologies or need content in alternative formats.

What Is Guideline 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."

Guideline 1.3.3 is a Level A requirement in the Web Content Accessibility Guidelines (WCAG) .

  • Don’t use instructions like “click the red button” or “see the box on the right” without also providing a text label or description.
  • Ensure that users who can’t perceive color, shape, or sound can still follow instructions and operate your site.
  • Use text labels, icons, or other cues in addition to sensory characteristics.

This ensures that everyone, including users with visual, auditory, or cognitive disabilities, can understand and use your content.


Why Does It Matter?

  • Inclusivity: Users with color blindness, low vision, or hearing loss may not perceive sensory cues.
  • Legal Compliance: Sensory Characteristics is a Level A requirement in WCAG 2.2 and referenced in accessibility laws worldwide.
  • Usability: Clear instructions help all users, especially in complex interfaces.

For more, see WebAIM's instructions and cues guide .


What Needs Clear Instructions?

  • Forms and input fields
  • Buttons and controls
  • Charts and graphs
  • Navigation menus
  • Any element referenced in instructions

All such elements should be identified by more than just color, shape, or position.


How to Provide Accessible Instructions

  • Use text labels in addition to color, shape, or sound
  • Reference elements by name or label, not just position or appearance
  • Provide icons or patterns for color-coded information
  • Test instructions with users who have different sensory abilities

For more, see the MDN instructions docs .


Common Mistakes to Avoid

  • Instructions that say “click the green button” without a label
  • Relying on color or shape alone to identify elements
  • Not providing alternative cues for charts or graphs
  • Ignoring users with sensory disabilities

Audit your site regularly and use accessibility checkers to ensure all instructions are clear and accessible. For more, see Oregon State University: Sensory Characteristics .


Differences Between A, AA, and AAA for Guideline 1.3.3 in WCAG 2.2

  • Level A: Requires instructions not rely solely on sensory characteristics. This is the core requirement for 1.3.3 and is mandatory for basic accessibility.
  • Level AA: For Guideline 1.3.3, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AA.
  • Level AAA: For Guideline 1.3.3, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AAA.

For more, see the W3C’s official documentation for 1.3.3 Sensory Characteristics .


Quick Checklist

  • All instructions use text labels, not just color or shape
  • Elements referenced by name or label
  • Color-coded info has icons or patterns
  • Instructions tested with users of different abilities
  • No reliance on sensory cues alone

Summary

Guideline 1.3.3 is essential for making your site usable and understandable for everyone. By providing instructions that don’t rely solely on sensory characteristics, you support users with disabilities, improve usability, and meet legal requirements. Make accessible instructions a standard part of your development process.