[a11y][Link] Assess WCAG 2.2 conformance #49413

Context

Wave 1, item 9. Tracking issue: #49260.

Check link purpose (2.4.4), use of color when underline="none" or "hover" (1.4.1), focus visibility (2.4.7) and component="button" semantics (4.1.2).

Scope

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

• 1.4.1 — With underline="none" and underline="hover", find a link in body text. Either the link color is at least 3:1 against the text color and a non-color cue shows on hover and focus, or the link fails.
• 1.4.3 — With a contrast checker, measure the link color against the background for each color, in light and dark mode. Each is at least 4.5:1.
• 2.4.4 — Read each link with the sentence around it. The purpose is clear.
• 2.4.7 — Press Tab to a link. A visible focus indicator shows.
• 4.1.2 — With a screen reader, focus an href link and a component="button" link. They announce "link" and "button".

Done when

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

Search keywords: