WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Developing Accessible Pages Using JAWS (11 and IE 8+)

for

From: Bryan Garaventa
Date: Jul 3, 2015 4:38PM

One thing of note, I had to evaluate a government product a while back using only JAWS11 within IE8, and there is some early attempts at ARIA support built into it, but this is very unreliable.

E.G http://www.freedomscientific.com/Support/TechnicalSupport/Bulletin/1404

The use of role=application and role=dialog/alertdialog causes major accessibility issues, and should be avoided unless absolutely necessary. ARIA Menu constructs do work if 'roving tabindex' is used instead of aria-activedescendant, and requires that the container be surrounded using role=application to invoke the correct browse modality when focus is set to a menuitem. ARIA Buttons work, but toggles do not, at least, not reliably, especially when contained within a container with role=toolbar. Most other ARIA constructs work partially and often cause more trouble than they are worth, because they convey enough to change what a screen reader user hears, but not enough to make them work accessibly.