Non-text content Screen reader compatibility
Screen reader compatibility for applets and timed media, showing how failures and techniques work in different screen reader / browser combinations.
The results include two types of test:
- Expected to work - these tests show support when accessibility features are used correctly
- Expected to fail - these tests show what happens when accessibility features are used incorrectly (marked with )
WCAG 2.0 1.1.1 Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.) Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content.
Reliability by user agent
The solid area in the graph shows percentage of tests that pass in all tested interaction modes. The cross hatched area shows partial passes that only work in some interaction modes.
An example of a partial pass is when form labels are read when tabbing, but ignored in browse mode.
|JAWS Chrome||JAWS 2022.2207.25 with Chrome 105|
|JAWS Edge||JAWS 2022.2207.25 with Edge 105|
|JAWS Firefox||JAWS 2022.2207.25 with FF102|
|JAWS IE||JAWS 2019.1912.1 with IE11|
|NVDA Chrome||NVDA 2022.2 with Chrome 105|
|NVDA Edge||NVDA 2022.2 with Edge 105|
|NVDA Firefox||NVDA 2022.2 with FF102|
|NVDA IE||NVDA 2019.2 with IE11|
|VoiceOver Mac||VoiceOver macOS 12.5 with Safari 15.6|
|VoiceOver iOS||VoiceOver iOS 15.6 with Safari iOS 15.6|
|WindowEyes IE||WindowEyes 9.2 with IE11|
|1 better 1 worse|
|Dolphin IE||Dolphin SR 15.05 with IE11|
|SaToGo IE||SaToGo 184.108.40.206 with IE11|
|Average||Including older versions|
The average includes all versions, but some browser/AT combinations have tests for multiple versions (NVDA / JAWS / VoiceOver), while others only have tests for a single version (SaToGo and Dolphin).
Expected to work
These tests use conformant HTML or WCAG sufficient techniques and might be expected to work in screen readers. This doesn't always happen.
Expected to fail
These tests use non-conformant HTML or WCAG failures and are expected to fail in screen readers.
Tests expected to fail (due to authoring errors) are marked with .
- Works in 100% of tested screen readers
- Fails in 1% - 25% of tested screen readers
- Fails in 26% - 50% of tested screen readers
- Fails in 51% - 75% of tested screen readers
- Fails in 76% - 100% of tested screen readers
- Stable - works, or doesn't cause problems, in all versions of a specific combination of screen reader and browser
- Better - works, or doesn't cause problems, in the most recent version of a specific combination of screen reader and browser (improvement)
- Worse - causes problems in the most recent version of a specific combination of screen reader and browser, but used to work in older versions (regression)
- Broken - causes problems in all versions of a specific combination of screen reader and browser
All tests were carried out with screen reader factory settings. JAWS in particular has a wide variety of settings controlling exactly what gets spoken.
Screen readers allow users to interact in different modes, and can produce very different results in each mode. The modes used in these tests are:
- Reading Content read using the “read next” command in a screen reader
- Tabbing Content read using the “tab” key in a screen reader
- Heading Content read using the “next heading” key in a screen reader
- Touch Content read when touching an area of screen on a mobile device
In the “What the user hears” column:
- Commas represent short pauses in screen reader voicing
- Full Stops represent places where voicing stops, and the “read next” or “tab” or “next heading” command is pressed again
- Ellipsis … represent a long pause in voicing
- (Brackets) represent voicing that requires a keystroke to hear