[Skip navigation links]

CSS and text content Screen reader compatibility

Last updated: December 27, 2017

Screen reader compatibility for CSS and text, showing how failures and techniques work in specific screen reader / browser combinations.

The results include two types of test:

Expected to fail

These tests use non-conformant HTML or WCAG failures and are expected to fail in screen readers.

Screen ReaderNVDAJAWSVoiceOverWin-EyesDolphinSaToGo
Should fail. Fails in 51% - 75% CSS content: propertyBadGoodBadBetterGoodGoodBadBadBad
Should fail. Fails in 76% - 100% Definition lists with images as bulletsBadBadBadBadBadBadBadBadBad
Should fail. Fails in 76% - 100% Look alike unicode charsBadBadBadBadBadBadBadBadBad
Should fail. Fails in 76% - 100% Space separated tablesBadBadBadBadBadBadBadBadBad
Should fail. Fails in 76% - 100% Space separated wordsBadBadBadBadBadBadBadBadBad


Tests expected to fail (due to authoring errors) are marked with Expected to Fail.

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:

In the «What the user hears» column: