video with aria-labelledby attribute Screen reader compatibility

Expected Result: works in a screen reader

Actual Result: causes problems in 62 screen reader / browser combinations

Note: The ARIA Text Alternative Computation allows objects to be labelled by items hidden by CSS

WCAG Technique: ARIA10: Using aria-labelledby to provide a text alternative for non-text content

Code used for this test:

		<video aria-labelledby='video-aria-labelledby-id'>
			<source type='video/mp4' src='small.mp4'></source>
		</video>
		<p id='video-aria-labelledby-id' style='display:none'>This is ARIA-LABELLEDBY text</p>
	

Reliability Trend

This graph shows reliability over time for this code in NVDA, JAWS and Voiceover. Other screen readers don't have enough historical data yet to plot trends.

Change History

Last updated: November 26, 2024

• NVDA with Chrome Causes problems from NVDA 2018.4 to NVDA 2024.4
• NVDA with IE Causes problems from NVDA 2015.2 to NVDA 2019.2
• NVDA with FF Better - caused problems in NVDA 2020.2, but now OK in NVDA 2024.4
• JAWS with Chrome Causes problems from JAWS 2018.1811.2 to JAWS 2024.2409.2
• JAWS with IE Causes problems from JAWS 14.0.9002 to JAWS 2019.1912.1
• JAWS with FF Causes problems from JAWS 14.0.9002 to JAWS 2024.2409.2
• VoiceOver macOS Better - caused problems in VoiceOver macOS 10.12, but now OK in VoiceOver macOS 14.6
• VoiceOver iOS Better - caused problems in VoiceOver iOS 10.3, but now OK in VoiceOver iOS 17.7
• WindowEyes with IE Causes problems from WindowEyes 8.4 to WindowEyes 9.2
• Dolphin with IE Causes problems in Dolphin SR 15.05

Test notes

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