Heading is IMG ALT="" Screen reader compatibility

Last updated: September 5, 2016

Expected Result: causes problems in some screen readers

Actual Result: causes problems in 28 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.

Code used for this test:


        <h2><img src='1234.png' alt=''></h2>
        <p>Heading 2 content</p>
    

Change History

Last updated: September 5, 2016

Screen readerBrowserModeNotesWhat the user hears
Fail NVDA 2016.2FF48HeadingHeading visible in browser, but ignored by screen reader.
Fail NVDA 2016.2IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail NVDA 2015.2FF41HeadingHeading visible in browser, but ignored by screen reader.
Fail NVDA 2015.2IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail NVDA 2014.1FF29HeadingHeading visible in browser, but ignored by screen reader.
Fail NVDA 2014.1IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail NVDA 2012.1FF29HeadingHeading visible in browser, but ignored by screen reader.
Fail NVDA 2012.1IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 17.0.2619FF48HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 17.0.2619IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 16.0.4350FF41HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 16.0.4350IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 15.0.9023FF29HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 15.0.9023IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 14.0.9002FF29HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 14.0.9002IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 13.0.852FF29HeadingHeading visible in browser, but ignored by screen reader.
Fail JAWS 13.0.852IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail WindowEyes 9.2IE11HeadingHeading visible in browser, but ignored by screen reader.
Fail WindowEyes 8.4IE11HeadingText of following paragraph read out as heading Speak Heading 2, Heading 2 content
Fail VoiceOver OSX 10.11Safari 9.1.2HeadingHeading image visible in browser, no heading label read by screen reader. Speak Heading level 2
Fail VoiceOver OSX 10.10Safari 9.0.1HeadingHeading image visible in browser, no heading label read by screen reader. Speak Heading level 2
Fail VoiceOver OSX 10.9Safari 7.0.3HeadingHeading image visible in browser, no heading label read by screen reader. Speak Heading level 2
Fail VoiceOver iOS 9.1Safari iOS 9.1TouchHeading image visible in browser, meaningless heading read by screen reader. Speak Two, heading level 2
Fail VoiceOver iOS 8.4Safari iOS 8.4TouchHeading image visible in browser, meaningless heading read by screen reader. Speak Two, heading level 2
Fail VoiceOver iOS 7.1Safari iOS 7.1TouchHeading image visible in browser, meaningless heading read by screen reader. Speak Two, heading level 2
Fail Dolphin SR 15.05IE11HeadingHeading visible in browser, but ignored by screen reader
Fail SaToGo 3.4.96.0IE11HeadingReads following paragraph as heading Speak Heading 2 content, heading level 1

SortSite rules: AccWcag1-3.5.3

Test notes

The threshold for inclusion in these results is 5% usage in the most recent WebAIM screen reader survey. Chrome and Android still fall below the 5% threshold.

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: