[a11y][SpeedDial] Assess WCAG 2.2 conformance #49446

Context

Wave 4, item 17 (lower risk). Tracking issue: #49260.

Include SpeedDialAction and SpeedDialIcon. Focus on aria-expanded and aria-haspopup on the trigger (4.1.2), keyboard navigation of the actions (2.1.1), the action names that show only in tooltips (1.1.1, 1.4.13) and hover-to-open (1.4.13).

Scope

1. Add axe tests and fixtures in test/regressions/a11y/fixtures/.
2. Write SpeedDial/accessibility.md.
3. Enroll it in the CSS-dependent suite (1.4.10, 1.4.4, 1.4.12).
4. Run pnpm a11y:scorecard.

Manual tests

Write each check in the report as numbered Manual testing steps, as in Button/accessibility.md. pnpm a11y:scorecard then adds them to manual-testing.md. For screen-reader steps, use NVDA with Chrome and VoiceOver with Safari.

• 2.1.1 — Press Tab to the SpeedDial button. Enter or Space opens it. The arrow keys for the direction move between the actions. Escape closes it, and focus goes back to the button.
• 4.1.2 — With a screen reader, the button announces its name, that it opens a menu, and "expanded" or "collapsed". Each action announces its tooltipTitle as the name.
• 1.4.13 — Open the SpeedDial with hover. Move the pointer onto the actions and their tooltips. They stay visible. Escape closes them without a pointer move.
• 1.1.1 — With tooltipOpen, the action names are visible. Without it, record that the names are visible only on hover or focus.
• 2.4.11 — With the SpeedDial in a fixed position, press Tab through the page. It does not fully hide a focused element.
• 2.5.8 — Each action is at least 24 × 24 CSS px.

Done when

• SpeedDial has a report and is in the scorecard.
• Each manual test in this issue has steps and a result in the report.

Search keywords: