Skip to content

fix(a11y): WCAG 2.1 AA accessibility audit and remediation for claim flow (Closes #401) - #417

Open
waterWang wants to merge 1 commit into
bridgelet-org:mainfrom
waterWang:fix/wcag-aa-claim-flow-accessibility
Open

fix(a11y): WCAG 2.1 AA accessibility audit and remediation for claim flow (Closes #401)#417
waterWang wants to merge 1 commit into
bridgelet-org:mainfrom
waterWang:fix/wcag-aa-claim-flow-accessibility

Conversation

@waterWang

Copy link
Copy Markdown

Description

Conducts a WCAG 2.1 AA accessibility audit and remediation for the claim flow, as described in #401.

Changes

  1. Skip-to-content link (WCAG 2.4.1 Bypass Blocks) — Added #main-content skip link in PageShell that appears on focus for keyboard users.

  2. Loading state screen reader announcement (WCAG 4.1.3 Status Messages) — Added role="status" + aria-live="polite" to the loading state in ClaimPageClient so screen readers announce "Loading claim details…"

  3. Claim in-progress announcement (WCAG 4.1.3) — Added visually hidden role="status" aria-live="assertive" live region that announces "Claim in progress" when the user submits a claim. Added aria-busy to the form container during processing.

  4. Automated axe-core accessibility checks — Added @axe-core/playwright to the e2e test suite with three scans:

    • Claim page in PENDING_CLAIM state
    • Claim page in CLAIMED state (after successful claim)
    • Send page
  5. Audit documentationdocs/accessibility-audit.md documents all findings, existing patterns confirmed, and remediation applied.

Verification

  • ✅ All 194 existing frontend unit tests pass
  • ✅ 27 test files pass with no regressions
  • ✅ Keyboard-only navigation verified through the full claim flow
  • ✅ ARIA live regions properly announce status changes
  • ✅ axe-core integrates into the existing e2e CI pipeline

Acceptance criteria

  • Manual audit findings documented and triaged → docs/accessibility-audit.md
  • Claim flow is fully operable via keyboard alone
  • Async status changes are announced to screen readers via ARIA live regions
  • Automated axe-core checks added to CI for the claim and send flows

…flow (Closes bridgelet-org#401)

- Add skip-to-content link in PageShell (WCAG 2.4.1 Bypass Blocks)
- Add role=status live region to loading state in ClaimPageClient (WCAG 4.1.3)
- Add sr-only live region announcing claim-in-progress + aria-busy on form
  (WCAG 4.1.3 Status Messages)
- Add axe-core automated accessibility scans to e2e suite covering the
  claim flow (PENDING_CLAIM + CLAIMED states) and the send flow
- Document audit findings in docs/accessibility-audit.md

Existing accessibility patterns confirmed: aria-live on ClaimStatusCard
article, role=alert on errors, role=status on success, color+text status
badges, visible focus indicators, full keyboard operability.
@vercel

vercel Bot commented Aug 22, 2026

Copy link
Copy Markdown

@waterWang is attempting to deploy a commit to the aminubabafatima8-gmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant