CSS content: property on div Screen reader compatibility

CSS HTML WCAG
Nov 26, 2024

Expected Result: causes problems in some screen readers

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

For expected failures, the results show which AT combos the failures affect. Results are recorded from the user's viewpoint, so describe the user impact of authoring errors.

WCAG Failure: F87

Code used for this test:


		<style> div.important::after { content: ' Safety Recall'; color: red; } </style>
		<div class='important'>Blue Widgets</div>
	

Change History

Last updated: November 26, 2024

  • NVDA with Chrome Stable - OK from NVDA 2023.3 to NVDA 2024.4
  • NVDA with FF Stable - OK from NVDA 2023.3 to NVDA 2024.4
  • JAWS with Chrome Stable - OK from JAWS 2023.2311.34 to JAWS 2024.2409.2
  • JAWS with FF Stable - OK from JAWS 2023.2311.34 to JAWS 2024.2409.2
  • VoiceOver macOS OK in VoiceOver macOS 14.6
  • VoiceOver iOS OK in VoiceOver iOS 17.1
Screen readerBrowserModeNotesWhat the user hears
NVDA 2024.4Chrome 131 Reading Blue Widgets Safety Recall
NVDA 2024.4FF 128 Reading Blue Widgets Safety Recall
NVDA 2024.4Edge 131 Reading Blue Widgets Safety Recall
NVDA 2023.3Chrome 120 Reading Blue Widgets Safety Recall
NVDA 2023.3FF 115 Reading Blue Widgets Safety Recall
NVDA 2023.3Edge 120 Reading Blue Widgets Safety Recall
JAWS 2024.2409.2Chrome 131 Reading Blue Widgets Safety Recall
JAWS 2024.2409.2FF 128 Reading Blue Widgets Safety Recall
JAWS 2024.2409.2Edge 131 Reading Blue Widgets Safety Recall
JAWS 2023.2311.34Chrome 120 Reading Blue Widgets Safety Recall
JAWS 2023.2311.34FF 115 Reading Blue Widgets Safety Recall
JAWS 2023.2311.34Edge 120 Reading Blue Widgets Safety Recall
VoiceOver macOS 14.6Safari 17.6 Reading Blue Widgets Safety Recall
VoiceOver iOS 17.1Safari iOS 17.1Touch Blue Widgets Safety Recall

SortSite rules: AccWcag2-F87-1

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