Identify Purpose
Summary:
WCAG 1.3.6, "Identify Purpose," expands on making digital content more accessible by enabling the identification of the purpose of user interface components, icons, and regions. This Level AAA criterion is particularly beneficial for users relying on assistive technologies, offering a more personalized and understandable user experience.
What:
This guideline requires that the purpose of user interface components, icons, and regions can be programmatically determined. This allows for more personalized user interfaces based on individual needs and preferences, especially for those using assistive technologies like screen readers or alternative input methods.
Why:
Understanding the purpose of different elements on a web page or application is crucial for users with disabilities. When the purpose of elements is clear, assistive technologies can better assist users in navigating and understanding content, making the digital environment more intuitive and accessible.
Examples and Scenarios:
- Customizable Interface for Screen Readers: Users with screen readers can benefit from a website where the purpose of different sections (like navigation, main content, search) is programmatically determined, allowing for more efficient navigation.
- Adaptable Icons for Cognitive Disabilities: Icons on a user interface, when programmatically labeled, can be adapted or replaced with text for users with cognitive disabilities who might find text easier to understand than icons.
- Personalization for Motor Impairments: Users with motor impairments can have interfaces automatically adjust, highlighting interactive elements like buttons and links more prominently based on their purpose.
How to Comply:
- Websites: Use semantic HTML and ARIA roles to define the purpose of elements. Ensure that the role, state, and value of user interface components are identifiable.
- Mobile Apps: Implement accessibility features that allow app elements to be identified and adapted based on their purpose.
- Software Applications: Design your application's UI in such a way that the purpose of different elements can be easily determined by assistive technologies.
Exceptions:
- *Complex User Interfaces: As mentioned, in specialized or complex software, it can be challenging to clearly define the purpose of every UI component, particularly when they serve multiple or dynamic functions.
- Legacy Systems: Older systems or content that wasn't designed with modern semantic web standards might not easily support the level of programmability required by this guideline.
- Third-Party Content: Content or components integrated from third-party sources might not always comply with this level of semantic clarity, and modifying them could be beyond the control of the site or application owner.
1* Technological Limitations: Current limitations in technology or programming languages might restrict the ability to fully implement this guideline, especially for more nuanced or less common user interface components.