a11y
Run every accessibility check (jsx-a11y lint, scan coverage and contrast unit tests, the diff check, axe on every page in he/en, keyboard and reflow tests) and summarize violations with file:line and
SKILL.md.claude/skills/a11y/SKILL.md
GitHubFrom the repo root:
pnpm --filter @kj/web lint
pnpm --filter @kj/web test -- src/lib/a11y
pnpm a11y:diff
pnpm test:scripts
pnpm --filter @kj/web build
pnpm --filter @kj/web test:a11y
Notes:
test:a11yrunse2e/a11y.spec.ts(axe, every entry insrc/lib/a11y/routes.ts, both locales, Chromium and WebKit) ande2e/a11y-keyboard.spec.ts. Add--project=mobile-chromefor a quicker first pass.- If another dev server holds
apps/web/.nextor port 3000, build and test withNEXT_DIST_DIR=.next/e2e PORT=3100 NEXT_PUBLIC_SUPABASE_URL= NEXT_PUBLIC_SUPABASE_ANON_KEY=on both commands (demo mode, like CI), and revertapps/web/tsconfig.jsonafterwards. - A failing axe test prints each violation with its rule, help link, CSS selector and
failureSummary; the full JSON is attached to the test inapps/web/playwright-report(in CI: thea11y-reportartifact). - Fix the cause in the component or token, not the test.
color-contrastfailures usually mean white text onbg-brand/bg-brand-2: usebg-brand-fill/bg-brand-2-fill. - "scans every page" failing in the unit tests means a new
page.tsxneeds anA11Y_SCANSentry.
Report: green/red per check, each violation as file:line - rule - who it affects - fix, and
what you changed.