Click Here link with aria-describedby attribute Screen reader compatibility

Expected Result: works in a screen reader

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

Tests if the user hears extra text describing the "Click Here" link when moving between links. Without extra text the user hears a sequence like "Click Here. Click Here. Click Here" when tabbing, using the read next link command, or the list links command. In reading mode the text surrounding the link helps explain what the link does.

By design aria-describedby produces different results to aria-labelledby because the Accessible Name and Description: Computation and API Mappings specification maps these to different accessibility API properties.

WCAG Technique: ARIA1

Code used for this test:

		<a href='4567.html' aria-describedby='a-aria-describedby-clickhere'>Click Here</a>
		<span id='a-aria-describedby-clickhere'>this is an aria described by</span>
	

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: December 12, 2023

• NVDA with Chrome Stable - OK from NVDA 2018.4 to NVDA 2023.3
• NVDA with IE Stable - OK from NVDA 2012.3 to NVDA 2019.2
• NVDA with FF Stable - OK from NVDA 2012.1 to NVDA 2023.3
• JAWS with Chrome Stable - OK from JAWS 2018.1811.2 to JAWS 2023.2311.34
• JAWS with IE Better - caused problems in JAWS 18.0.5038, but now OK in JAWS 2019.1912.1
• JAWS with FF Better - caused problems in JAWS 13.0.852, but now OK in JAWS 2023.2311.34
• VoiceOver macOS Better - caused problems in VoiceOver macOS 10.10, but now OK in VoiceOver macOS 13.6
• VoiceOver iOS Stable - OK from VoiceOver iOS 7.1 to VoiceOver iOS 16.6
• WindowEyes with IE Causes problems in WindowEyes 9.2
• Dolphin with IE Causes problems in Dolphin SR 15.05
• SaToGo with IE OK in SaToGo 3.4.96.0

SortSite rules: AccHtmlLinkTextAmbiguous

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