Link text replaced by aria-label attribute Screen reader compatibility

Expected Result: works in a screen reader

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

A much more reliable alternative is changing the text inside in the link element start and end tags.

Tests if the user hears the ARIA label as specified by HTML Accessibility API Mappings

WCAG Technique: ARIA8

Code used for this test:

		<a href='4567.html' aria-label='this is an aria label'>Click Here</a>
	

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 Stable - OK from NVDA 2018.4 to NVDA 2024.4
• NVDA with IE Better - caused problems in NVDA 2014.1, but now OK in NVDA 2019.2
• NVDA with FF Better - caused problems in NVDA 2014.1, but now OK in NVDA 2024.4
• JAWS with Chrome Stable - OK from JAWS 2018.1811.2 to JAWS 2024.2409.2
• JAWS with IE Stable - OK from JAWS 13.0.852 to JAWS 2019.1912.1
• JAWS with FF Better - caused problems in JAWS 2018.1811.2, but now OK in JAWS 2024.2409.2
• VoiceOver macOS Stable - OK from VoiceOver macOS 10.9 to VoiceOver macOS 14.6
• VoiceOver iOS Stable - OK from VoiceOver iOS 7.1 to VoiceOver iOS 17.7
• WindowEyes with IE Better - caused problems in WindowEyes 8.4, but now OK in WindowEyes 9.2
• Dolphin with IE OK in Dolphin SR 15.05
• SaToGo with IE Causes problems 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