Accessibility pass: WCAG 2.2 AA across portal, public hubs, widget, and API
Bring the entire product up to WCAG 2.2 AA. Front-end: keyboard reachability, focus-visible states, semantic landmarks, ARIA only where native semantics fall short, color contrast tokens audited in both themes, prefers-reduced-motion respect, captions and transcripts on demo videos, screen-reader pass on every primary flow (post create, comment, vote, status change, billing). Back-end: API errors return human-readable messages, error responses include WCAG-compliant status text for downstream renderers, server-rendered pages ship correct lang attributes, transactional emails use accessible HTML structure. Add an automated axe-core run to CI so regressions fail PRs.
Comments (3)
- Elsama· 9 days ago
Partial ship: CI now runs @axe-core/playwright on /login via npm run test:a11y (wired into the admin-routing job). Marketing home / still fails color-contrast on decorative step numbers, so it is not in the gate yet. Expanding paths after those contrast fixes.
- Elsama· 9 days ago
Axe CI PUBLIC_PATHS now: /, /login, /compare, /glossary, /status. Marketing/status contrast tweaks included.
- Elsama· 9 days ago
Shipped as far as product CI can carry: axe gate on key public routes, focus-visible baseline, prefers-reduced-motion for marketing/terminal demos, html lang already set. Full WCAG 2.2 AA across every flow remains ongoing polish.
Join the discussion
Sign in to leave a comment on this thread.