The subject of screen reader detection has been under discussion lately. It isn’t something I’m comfortable with, so I’d like to share the reasons why.
There is an unusual problem with Jaws and Internet Explorer that causes the word “region” to be announced before every field in a form. Fortunately there is a workaround until the problem itself is resolved.
Most current screen readers support ARIA to one extent or another, and many now support some features of HTML5 as well. With ARIA and HTML5 making increasing amounts of semantic data available to screen reader users, it’s really easy to inadvertently overload people with too much information. Let’s take an example that crops up from […]
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 […]
The main element extension specifies a way to markup the primary content area of a web page in HTML5. There are several good reasons for introducing the main element, including a more reliable way for screen readers to pinpoint the start of the primary content area on the page.
When a form is used to update information on the page, it can be troublesome for screen reader users. Unless the screen reader is focused on the relevant bit of the page, the update goes by un-noticed. ARIA live regions are a simple way to improve the experience for screen reader users.