HTML5 includes a handful of section elements that give documents a robust semantic structure. The header, footer, nav, article, section and aside elements give different regions of a document meaning. Amongst other things, that meaning can be understood by screen readers, and the information used to help blind and partially sighted people orient themselves and navigate around the page.
Now that HTML5 is being used on mainstream websites (such as that of the UK Government), itâ€™s interesting to see how well screen readers support this handful of elements. Testing included Jaws 14, NVDA 2012.3 and Window Eyes 8, with Firefox 18 and Internet Explorer 9, and VoiceOver (Mac OSX 10.8.2) with Safari 6.
|Element||Jaws 14/FF 18||Jaws 14/IE 9||NVDA 2012.3/FF 18||NVDA 2012.3/IE 9||VoiceOver/Safari 6||Window Eyes 8/FF 18||Window Eyes 8/IE 9|
Of the six HTML5 elements tested, header is the least well supported.
Only Window Eyes does not support any of the HTML5 elements (in any browser). VoiceOver, Jaws and NVDA all support some elements, but not always consistently across browsers.
NVDA reports the start of supported elements. For example the aside element is announced as â€śComplimentary information landmarkâ€ť. Jaws and VoiceOver report both the start and end of supported elements. For example Jaws announces â€śArticleâ€ť and â€śArticle endâ€ť for the article element, and VoiceOver uses the format “Entering article landmark” and “Leaving article landmark”.
One difference between the screen readers that support the footer element is that VoiceOver reports it as “footer”, whilst NVDA and Jaws use “Content information” and “Content info” respectively.
Jaws, VoiceOver and NVDA include supported elements when navigating by landmark. This makes sense because the header, footer, nav, article, section and aside elements all Map to ARIA landmarks. Worth noting that all screen readers tested have good support for ARIA landmarks.
Those elements that are not supported in a particular screen reader/browser combination are handled in the same way as a div or other element without semantic meaning would be. Which is to say that the content is accessible, but the element itself is not acknowledged in any way.
This entry was posted on February 17th, 2013, and filed under Code things.