Conduct a formal accessibility conformance review

Problem

The site has automated Axe coverage, an accessibility page, alternate résumé access, appearance modes, and other accessibility protections, but docs/SYSTEM_STATE.md explicitly notes there has been no formal accessibility conformance audit.

Goal

Validate the public site against a defined WCAG target and turn any real findings into focused follow-up work.

Scope

• Choose and document the conformance target, preferably WCAG 2.2 AA where applicable.
• Review the highest-value visitor paths manually in addition to automated scans.
• Cover keyboard operation, focus management, screen-reader semantics, contrast, zoom/reflow, forms, résumé alternatives, and Ask Mantosh interactions.
• Record evidence and separate actual failures from advisory improvements.
• Update the public accessibility statement when findings are resolved or known limitations change.

Acceptance criteria

• The audit target and methodology are documented.
• Critical public routes and interactive flows receive manual review.
• Findings are recorded with severity and reproducible evidence.
• Material failures are fixed or tracked in dedicated issues.
• accessibility/ accurately reflects verified capabilities and known limitations.

Start with docs/SYSTEM_STATE.md and the existing accessibility/ content, then review the site's automated Axe coverage and identify the critical public routes and interactive flows. Document the WCAG target and methodology, record manual and automated findings with reproducible evidence, and ensure failures are fixed or tracked and accessibility/ reflects verified capabilities and limitations.