|
3 | 3 | ## Understand How Accessibility Patterns Are Used |
4 | 4 | This section provides a structured overview of accessibility patterns identified through WAVE, organized into three categories: |
5 | 5 |
|
6 | | -### Structural Element |
7 | | -Documentation about accessibility patterns related to semantic HTML elements that define the structure, organization, and relationships within a page. These patterns include headings, lists, landmarks, tables, and other structural components that enable assistive technologies to interpret and navigate content effectively. |
| 6 | +- **Structural Element:** Documentation about accessibility patterns related to semantic HTML elements that define the structure, organization, and relationships within a page. These patterns include headings, lists, landmarks, tables, and other structural components that enable assistive technologies to interpret and navigate content effectively. |
8 | 7 |
|
9 | | -### Feature |
10 | | -Documentation about accessibility patterns related to user-facing functionality and interface behaviors that enable users to perceive, understand, and interact with content. These patterns include images, links, forms, navigation aids, and other interactive elements that must be accessible to all users across different devices and assistive technologies. |
| 8 | +- **Feature:** Documentation about accessibility patterns related to user-facing functionality and interface behaviors that enable users to perceive, understand, and interact with content. These patterns include images, links, forms, navigation aids, and other interactive elements that must be accessible to all users across different devices and assistive technologies. |
11 | 9 |
|
12 | | -### ARIA |
13 | | -Documentation about accessibility patterns that use ARIA roles, states, and properties to enhance or communicate meaning, behavior, and dynamic changes to assistive technologies when native HTML alone is not sufficient. These patterns focus on ensuring that custom or interactive components are properly announced, labeled, and usable by screen |
| 10 | +- **ARIA:** Documentation about accessibility patterns that use ARIA roles, states, and properties to enhance or communicate meaning, behavior, and dynamic changes to assistive technologies when native HTML alone is not sufficient. These patterns focus on ensuring that custom or interactive components are properly announced, labeled, and usable by screen |
14 | 11 | reader and keyboard users. |
15 | 12 |
|
16 | 13 | Each category groups related patterns that address how users interact with content, how that content is structured, and how additional semantics are communicated to assistive technologies. |
|
0 commit comments