37 lines
1.3 KiB
Markdown
37 lines
1.3 KiB
Markdown
[Back to 1 Perceivable index](index.md)
|
|
|
|
# 1.3.6 Identify Purpose
|
|
|
|
- Level: AAA
|
|
- Guideline: 1.3 Adaptable
|
|
- Principle: 1 Perceivable
|
|
|
|
## What it is
|
|
|
|
In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.
|
|
|
|
## How to test
|
|
|
|
- Check: In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.
|
|
- Use the sufficient techniques below as acceptable methods when applicable.
|
|
|
|
## Sufficient techniques (W3C)
|
|
|
|
- Programmatically indicating the purpose of icons, regions and user interface components
|
|
- ARIA11: Using ARIA landmarks to identify regions of a page
|
|
- Using microdata to markup user interface components (future link)
|
|
|
|
## Advisory techniques (W3C)
|
|
|
|
- Enabling user agents to find the version of the content that best fits their needs
|
|
- Using semantics to identify important features (e.g., coga-simplification="simplest")
|
|
- Using aria-invalid and aria-required
|
|
|
|
## Resources
|
|
|
|
- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#identify-purpose
|
|
- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/identify-purpose.html
|
|
- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#identify-purpose
|
|
|
|
[Back to 1 Perceivable index](index.md)
|