Governance scenarios 0/6 Accessibility policy is documented and approved by leadership Program readiness check Medium Accessibility ownership is assigned across product, design, engineering, QA, and content Program readiness check Low Accessibility requirements are included in vendor procurement and third-party review Program readiness check High A remediation SLA exists for critical, high, medium, and low issues Program readiness check Medium Accessibility metrics are tracked across releases and reported to stakeholders Program readiness check Low Teams receive role-based accessibility training at least annually Program readiness check High
Design scenarios 0/6 Color contrast tokens meet WCAG AA for text, icons, focus, and UI components Design readiness check Medium Design files include keyboard focus order, error states, and responsive states Design readiness check Low Components include accessible names, roles, states, and usage guidance Design readiness check High Touch targets and spacing support mobile and motor accessibility Design readiness check Medium Motion patterns respect reduced motion and avoid unnecessary animation Design readiness check Low Design system patterns include modals, menus, tabs, alerts, forms, tables, and cards Design readiness check High
Content scenarios 0/6 Page titles are unique and describe the page purpose Content readiness check Medium Headings are meaningful and follow a logical hierarchy Content readiness check Low Links make sense out of context and avoid vague labels Content readiness check High Images have useful alt text or are marked decorative Content readiness check Medium Instructions do not rely on color, shape, position, or sound alone Content readiness check Low Plain language, consistent terminology, and readable content structure are used Content readiness check High
Engineering scenarios 0/6 Semantic HTML is used before ARIA, with ARIA only where necessary Engineering readiness check Medium Custom components expose correct name, role, value, state, and properties Engineering readiness check Low Keyboard interaction follows expected platform patterns Engineering readiness check High Focus is managed correctly in dialogs, drawers, menus, and route changes Engineering readiness check Medium Live regions announce important status updates without being disruptive Engineering readiness check Low Automated accessibility tests run in CI or pull request workflows Engineering readiness check High
Keyboard scenarios 0/6 All interactive elements are reachable and operable by keyboard alone Keyboard readiness check Medium Focus order matches the visual and logical reading order Keyboard readiness check Low Focus indicators are visible, high contrast, and not obscured Keyboard readiness check High No keyboard trap exists in modals, menus, widgets, or embedded content Keyboard readiness check Medium Skip links or bypass mechanisms exist for repeated content Keyboard readiness check Low Shortcut keys do not conflict with assistive technology or browser shortcuts Keyboard readiness check High
Forms scenarios 0/6 Every input has a persistent, programmatic label Forms readiness check Medium Required fields are identified visually and programmatically Forms readiness check Low Error messages are clear, specific, and linked to fields Forms readiness check High Success and failure messages are announced through accessible status regions Forms readiness check Medium Autocomplete attributes are used for common personal information fields Forms readiness check Low Forms preserve user input after validation errors whenever possible Forms readiness check High
Media scenarios 0/6 Videos include accurate captions and meaningful transcripts Media readiness check Medium Audio content includes transcripts or equivalent alternatives Media readiness check Low Autoplaying media is avoided or can be paused immediately Media readiness check High Charts and complex visuals include text summaries or data alternatives Media readiness check Medium Documents and downloadable PDFs are tagged and keyboard accessible Media readiness check Low Icon-only controls have accessible names and visible focus states Media readiness check High
Responsive scenarios 0/6 Content reflows at 320 CSS pixels without horizontal scrolling Responsive readiness check Medium Pages remain usable at 200% and 400% browser zoom Responsive readiness check Low Text spacing adjustments do not cause clipping or overlap Responsive readiness check High Orientation is not locked unless essential Responsive readiness check Medium Mobile navigation supports screen readers, keyboard, and touch Responsive readiness check Low Content remains readable in dark mode, high contrast, and forced color settings Responsive readiness check High
QA scenarios 0/6 Manual keyboard testing is completed for key journeys QA readiness check Medium Screen reader testing is completed with NVDA, VoiceOver, or JAWS as appropriate QA readiness check Low Automated scans are reviewed by experts and false positives are triaged QA readiness check High Regression testing is completed after remediation QA readiness check Medium User flows are tested with real content, validation, loading, and error states QA readiness check Low Accessibility defects include WCAG reference, impact, steps, and recommended fix QA readiness check High
AI scenarios 0/6 AI-generated content is reviewed for accuracy, bias, and accessibility quality AI readiness check Medium AI outputs include human review before accessibility-critical changes are shipped AI readiness check Low AI features provide transparent status, errors, and user control AI readiness check High AI remediations do not override assistive technology or user preferences AI readiness check Medium Prompt, response, and generated UI patterns are keyboard and screen reader accessible AI readiness check Low Monitoring is in place for dynamic, personalized, and runtime accessibility changes AI readiness check High
