[REVIEW: Verify against live product before announcing.]
VideoPlayer.ai uses semantic HTML and ARIA so that screen readers can describe pages, dashboards, and the player itself.
What screen readers should announce
| Element | Announcement |
|---|---|
| Page H1 | "Heading level 1, title" |
| Player | The player is wrapped in a region labeled with the video title |
| Play / pause control | Button with an accessible name; the state toggles between "Play" and "Pause" |
| Time slider | Slider with current and total time, value updates as the user seeks |
| Volume slider | Slider with current volume from 0 to 100 |
| Captions toggle | Button labeled "Captions on" or "Captions off" |
| Fullscreen | Button labeled "Enter fullscreen" or "Exit fullscreen" |
Live regions
Status changes that matter to a screen reader user (such as "Captions enabled" when toggled) are announced through ARIA live regions configured to be polite. The player does not blast the user with constant updates.
Tested with
The player has been smoke-tested with VoiceOver on macOS and NVDA on Windows. Behavior on other combinations may differ; if you find a regression, write to [email protected] with the screen reader, browser, and page URL.
What is not yet covered
- Programmatic descriptions of every UI element in the dashboard have not been audited end-to-end.
- Sign-language interpretation tracks are not supported.
- Audio descriptions are supported as a separate uploaded track but are not automatically generated.
Verification
If you rely on a screen reader and something does not announce as expected, the dashboard's contact form is the fastest way to report it. Include the page URL, the assistive technology and version, and the expected vs actual announcement.