Skip to content

Accessibility

Ankit Upadhyay edited this page Aug 25, 2026 · 3 revisions

Accessibility

Accessibility is enforced in CI, not treated as a polish pass. The driver is the EU Accessibility Act (EAA) and Germany's BFSG; the standard is WCAG. Compliance context: Compliance and Certifications.

Target

  • Floor: WCAG 2.1 AA. Goal: WCAG 2.2 AA.
  • Enforced automatically on every frontend component via jest-axe / axe-core (jest-axe specs in the frontend Jest suite, run by the single-run CI pipeline; plus @axe-core/playwright in the frontend-e2e public a11y job) plus required ARIA patterns for interactive elements, live-status regions, forms, tabs, dialogs, and data tables.
  • Color never carries meaning alone - always paired with text or an icon.

The canonical documents

The plans and checklists live in docs/accessibility/:

Document Purpose
frontend-bfsg-wcag-audit-plan.md The master BFSG/EAA audit & remediation plan for apps/frontend - WCAG 2.1 AA floor, 2.2 AA target - written as a batch-by-batch engineering handoff.
frontend-bfsg-execution-checklist.md Progress checklist across remediation batches (skip link, jest-axe/axe-core enforcement, the /accessibility statement page, and more).
zoom-reflow-reduced-motion-checklist.md Manual regression checklist for the criteria tooling can't cover: SC 1.4.4 (resize to 200%), 1.4.10 (reflow), 2.3.3 (reduced motion).

Automated vs manual

  • Automated (every PR): jest-axe assertions, ARIA correctness, contrast where statically checkable.
  • Manual (regression checklist): 200% zoom, reflow at narrow widths, and reduced-motion behavior - human verification steps that automated tooling can't fully cover.

Recent remediation evidence

A contrast and motion pass landed in 2026-08: mobile's danger token was split so error text clears 4.5:1 (the fill and the text ink are now separate tokens), ink-ramp contrast on the bone surfaces was fixed, mobile's blueText token was darkened to #1162CE so blue text passes on bone, and the frontend's reduced-motion handling was rewritten to read prefers-reduced-motion through useSyncExternalStore rather than effect-mirrored state. The token-level reasoning is documented inline in apps/mobileAppYC/src/theme/colors.ts, which records measured contrast ratios next to the values.

User-facing statement

A dedicated /accessibility statement page is part of the remediation so the platform publicly documents its conformance and contact route.

Related

Product & Domain
Architecture
Applications
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Roadmap
Operations
Meta

Canonical code & docs: main repo · Auto-generated companion: DeepWiki

Clone this wiki locally