Skip to main content
Version: 1.0.0
Last Updated: 2026-02-09
Status: Active
Purpose: Document in-scope routes and patterns for accessibility audits (e.g. axe-core, jest-axe, manual a11y checks).

Hub Pages (In Scope)

Tabbed hub pages are in scope for accessibility audits. These include: When running axe or similar tools, include these routes (with at least one ?tab= variant per hub) to verify tab panels, focus management, and keyboard navigation. See UI/UX Standards § Tabbed Hub Accessibility Checklist.

Running Audits

Manual Audits

  1. Open the target hub route in Chrome DevTools (e.g. /hr/ats?tab=applications).
  2. Run Lighthouse → Accessibility audit and verify score ≥ 90.
  3. Alternatively, install the axe DevTools browser extension and run a scan on each hub route.
  4. Verify keyboard navigation: Tab through all triggers, confirm focus ring visibility, confirm Enter/Space activates tabs.

Automated Audits (Optional)

jest-axe (Unit/Integration)

Create __tests__/accessibility/hub-pages.test.tsx:

Playwright-axe (E2E)

Create e2e/accessibility/hub-pages.spec.ts: