Epic: Make any missing pages for aria, feature and structural elements guidance

[Rabia2219]

Overview

We need to make sure that the repo has complete guidance for accessibility patterns so that developer can understand which accessibility pattern to use

Action Items

• Ask ChatGPT for a list of all accessibility patterns
  • ARIA
  • Features
  • Structural Elements
• Compare against list in spreadsheet to identify missing items
• Add to spreadsheet
• Create issue for each page to add as sub issues to this issue

Resources/Instructions

• 1.0.1 Spreadsheet: Accessibility: WAVE: Known Issues and Solutions DRAFTS
• W3C: WAI-ARIA 1.2: Definitions of States and Properties.

[Rabia2219]

Accessibility: WAVE: Known Issues and Solutions DRAFTS, ChatGPT's List of Accessibility Patterns

[rayneng]

WAVE does not provide a separate indicator or guidance page for every ARIA role, state, and property. Most are represented by WAVE’s generic ARIA indicator, which identifies the presence of an ARIA role, state, or property. WAVE creates separate indicators only for selected cases where more specific evaluation guidance is useful:

• ARIA label
• ARIA description
• ARIA expanded
• ARIA hidden
• ARIA popup
• ARIA menu
• ARIA button
• ARIA alert or live region

The ARIA pages in our Accessibility Patterns Index reflect WAVE’s reporting categories rather than a comprehensive catalog of WAI-ARIA roles and aria-* attributes. The generic ARIA page should be understood as covering the remaining ARIA usage detected by WAVE.

To see additional ARIA attributes, see W3.org: WAI-ARIA 1.2: Definitions of States and Properties.

[rayneng]

todo: leaving comment with

• table from codex (comparing w3 aria attributes w/ WAVE)