1.3.3: Sensory Characteristics
Guideline 1.3.3 "Sensory Characteristics" under WCAG 2.0 ensures that instructions for understanding and operating content do not rely solely on sensory characteristics such as shape, color, size, visual location, orientation, or sound. This guideline aims to make content accessible to individuals with disabilities by providing alternative ways to convey information that does not depend solely on sensory cues.
Importance of 1.3.3: Sensory Characteristics Success Criterion
The importance of adhering to Guideline 1.3.3 lies in its role in ensuring that all users, including those with visual, auditory, and cognitive impairments, can understand and interact with web content. Relying solely on sensory characteristics can create barriers for users who cannot perceive these cues due to their disabilities. By providing alternative methods for conveying information, such as text descriptions or additional context, content creators can ensure that instructions and information are accessible to a wider audience. This practice not only enhances accessibility but also improves the overall user experience by making content more inclusive.
Primary Use Cases and Requirements Under Guideline 1.3.3: Sensory Characteristics (Level A)
Use Case 1: Form Instructions
Instead of saying "Click the green button to submit," use "Click the 'Submit' button."
How to Test: Review the form instructions to ensure they do not rely solely on color. Use a screen reader to verify that the instructions are clear and understandable without visual cues.
Use Case 2: Navigation and Links
Instead of "See the image to the right," use "See the image labeled 'Company Logo' to the right."
How to Test: Check all navigation instructions and links to ensure they do not depend solely on spatial orientation. Verify that users can understand and follow the instructions using a screen reader or keyboard navigation.
Use Case 3: Data Tables
Instead of "Refer to the values in the blue column," use "Refer to the values in the 'Monthly Sales' column."
How to Test: Review table descriptions and instructions to ensure they provide text labels or headings instead of relying on color. Use a screen reader to confirm that the table is accessible and understandable.
Use Case 4: Icons and Symbols
Instead of "Click the star icon to favorite," use "Click the star icon labeled 'Favorite' to add this item to your favorites."
How to Test: Check all icons and symbols to ensure they have text labels or descriptions. Use a screen reader to verify that the labels are announced and make sense without visual cues.
Use Case 5: Buttons and Interactive Elements
Instead of "Press the large round button to start," use "Press the 'Start' button."
How to Test: Review all buttons and interactive elements to ensure they are described by their function rather than shape or size. Use a screen reader to confirm that the descriptions are accurate and clear.
Use Case 6: Instructions for Users
Instead of "Enter your details in the boxes below," use "Enter your details in the text fields below the heading 'Personal Information'."
How to Test: Review all user instructions to ensure they do not rely solely on visual location. Verify that users can follow the instructions using a screen reader or keyboard navigation.
Use Case 7: Graphs and Charts
Instead of "The important data points are highlighted in red," use "The important data points are labeled 'High Priority' and highlighted in red."
How to Test: Check all graphs and charts to ensure that important information is conveyed through text labels or descriptions, not just color. Use a screen reader to verify that the information is accessible.