[a11y][Skeleton] Assess WCAG 2.2 conformance #49442

Context

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

Focus on the loading state for assistive technology (aria-busy, 4.1.3), 2.2.2 Pause, Stop, Hide (pulse and wave animations) and prefers-reduced-motion. Compare with the LinearProgress gaps.

Scope

1. Add axe tests and fixtures in test/regressions/a11y/fixtures/.
2. Write Skeleton/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.

• 4.1.2, 4.1.3 — With a screen reader, read a region that shows Skeletons. Record what the screen reader announces. The author can set aria-busy on the region.
• 4.1.3 — Replace the Skeletons with the content. Record if the screen reader announces the change.
• 2.2.2 — Look at the pulse and wave animations. Record if they stop when the content loads, and the behavior with prefers-reduced-motion: reduce.
• 2.3.1 — No part flashes more than three times per second.

Done when

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

Search keywords: