Accessibility training module

<h2>Purpose</h2> <p>This is the role-specific accessibility training module for personnel who design, build, review, test, approve, or support HiringCoachAI user-facing interfaces, accessibility statements, VPAT / ACR materials, or accessibility issue remediation.</p> <p>Complete this module before taking accessibility or user-interface delivery responsibilities and annually while those responsibilities remain assigned.</p> <h2>1. Maintain Current Standards Knowledge</h2> <p>Personnel assigned accessibility or UI responsibilities must stay current on:</p> <ul><li>WCAG 2.1 Level AA as HiringCoachAI&#39;s current verified conformance level and the customer-contract and HECVAT baseline.</li><li>WCAG 2.2 Level AA as the stated forward-looking target.</li><li>Section 508 and EN 301 549 concepts when responding to institutional customers.</li><li>WAI-ARIA authoring practices for custom controls.</li><li>Common accessibility risks in modern web applications, including keyboard traps, missing names, poor focus order, insufficient contrast, missing status announcements, and motion sensitivity.</li></ul> <p>No external accessibility certification is currently required. If a customer requires certified personnel or third-party testing, that requirement is handled through the enterprise review process.</p> <h2>2. Build Accessibility Into Design And Development</h2> <p>Accessibility is not a post-launch overlay or alternate mode. Personnel assigned UI work must:</p> <ul><li>Use semantic HTML and landmarks where practical.</li><li>Provide accessible names for links, buttons, form controls, and non-decorative images.</li><li>Maintain visible focus indicators and logical tab order.</li><li>Support keyboard operation for interactive controls.</li><li>Avoid color-only meaning.</li><li>Preserve 320 px reflow and 200% text resizing.</li><li>Respect <code>prefers-reduced-motion</code>.</li><li>Use ARIA only when semantic HTML is insufficient, and verify ARIA roles, states, and properties.</li></ul> <h2>3. Verify Accessibility</h2> <p>For material UI changes, assigned personnel use the applicable verification methods documented in <a href="/trust/docs/sdlc">secure development lifecycle</a> and the accessibility evidence set:</p> <ul><li><code>npm run lint:a11y</code> for jsx-a11y coverage.</li><li><code>npm run test:a11y</code> for jest-axe coverage.</li><li><code>npm run test:playwright:a11y</code> for Playwright + Axe coverage.</li><li>Keyboard-only walkthroughs for core flows.</li><li>Focus-management checks for dialogs, drawers, modals, and custom components.</li><li>Accessibility-tree inspection where names, roles, landmarks, or headings are in doubt.</li><li>320 px reflow checks for responsive pages.</li></ul> <p>Automated tools do not prove accessibility alone. Manual review remains required for keyboard flow, focus order, meaningful labels, status announcements, and user-flow context.</p> <h2>4. Triage And Remediate Accessibility Findings</h2> <p>Accessibility findings are tracked in the accessibility remediation log or an equivalent change record. Each finding should identify:</p> <ul><li>Affected route or component.</li><li>WCAG criterion or accessibility risk.</li><li>Severity and user impact.</li><li>Owner.</li><li>Status.</li><li>Evidence of closure.</li></ul> <p>Critical blockers are prioritized under the public accessibility-statement remediation commitments.</p> <h2>5. Maintain Customer-Facing Accessibility Materials</h2> <p>Personnel assigned accessibility ownership must keep the following materials aligned with actual implementation:</p> <ul><li>Public accessibility statement at <code>/accessibility</code>.</li><li>Public ACR / VPAT at <code>/vpat</code>.</li><li>Internal verification snapshot and evidence checklist.</li><li>Accessibility remediation log.</li><li>HECVAT accessibility answers.</li></ul> <p>Do not represent internal self-assessment as third-party audit, certification, or external attestation.</p> <h2>Acknowledgment</h2> <p>By acknowledging this module in <code>/admin/onboarding</code>, I confirm that I completed the role-specific accessibility training, understand the expectations above, and will maintain current accessibility knowledge for any HiringCoachAI accessibility or user-interface responsibilities assigned to me.</p>