Files
jobtrackingapp/docs/audits/evidence/accessibility-evidence.md
T
cesnimda a7c25499bb
CI and Deploy / test (pull_request) Successful in 4m54s
CI and Deploy / deploy (pull_request) Has been skipped
fix(a11y): close cross-app interaction gaps
2026-08-15 17:49:42 +02:00

2.0 KiB

Accessibility code-review evidence

Updated: 2026-08-15

Classification: code inspection, component tests and local authenticated Chromium. Native assistive-technology and production checks remain external.

Corrected issues

  • Every frontend IconButton now has an explicit programmatic name. This includes shell navigation/user/settings/search, company edit, correspondence delete, table columns and row actions, saved views, attachments, and CV Builder navigation. File-specific actions include the affected record name.
  • CV cards expose link semantics, keyboard focus, a visible focus indicator and Enter/Space activation. Their nested action menu remains independent of card navigation.
  • The anonymous public CV no longer puts a fixed 210mm element directly into a narrow page. It retains a full A4 iframe viewport, measures multi-page document height and scales the complete frame to the available width. Local Chromium proves no outer or inner horizontal overflow at 375px.
  • Semantic alert surfaces remain theme-owned. Authenticated Chromium measures the dark-mode missing-job Alert foreground against its composited background at or above WCAG AA 4.5:1.
  • The public loading state is announced with role=status and uses a stronger readable foreground.

Verification

  • Focused accessibility-related UI: 4 suites, 9/9 tests.
  • Full frontend: 54/54 suites, 228/228 tests.
  • Optimized production frontend build/TypeScript: pass.
  • Full Playwright: 7/7; final targeted workspace/public-CV rerun: 2/2.
  • Static IconButton audit: no control without an explicit aria-label.

Remaining external and future gates

  • Native screen-reader/switch-control and operating-system high-contrast checks are not available in the local automated environment and remain a production-readiness spot check.
  • No axe, pa11y or Lighthouse dependency/configuration is present, so CI does not yet run a general automated accessibility crawler. Adding one requires an approved dependency change and should complement, not replace, the focused semantic and contrast assertions above.