videojs Accessibility review
Inspect rendered semantics, interaction code, tests, and adjacent controls.
- Define the expected name, role, value or state, keyboard behavior, focus behavior, and announcements.
- Use
references/checklist.mdselectively for the affected control type; do not load the whole checklist for a narrow change. - Verify behavior in a browser when the review covers interaction or focus.
- Report only observable barriers or standards-backed risks.
For each finding, identify the affected user, element or state, impact, evidence, and smallest viable fix. Distinguish blockers from enhancements and avoid speculative conformance claims.
Example
Input: “Review the captions menu for keyboard and screen-reader barriers.”
Output: Standards-backed findings with the affected user, observable impact, evidence, severity, and smallest viable fix.