Re: DoJo Accessibility Help

There is a lot of accessibility information for developers linked form the 
Digit Accessibility Statement page
 
        see 
http://dojotoolkit.org/reference-guide/1.8/dijit/a11y/statement.html

        Dijit Accessibility Strategy
Dojo Accessibility Resources
Creating Accessible Widgets
Testing Widgets For Accessibility
Basic A11y Requirements
____________________________________________
Regards,
Phill Jenkins, 
Senior Engineer & Business Development Executive
IBM Research - Human Ability & Accessibility Center
http://www.ibm.com/able
http://www.facebook.com/IBMAccessibility
http://twitter.com/IBMAccess
http://www.linkedin.com/in/philljenkins



From:   "Homme, James" <james.homme@highmark.com>
To:     "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>, 
Date:   03/07/2013 01:13 PM
Subject:        DoJo Accessibility Help



Hi,
I'm more of a glorified user sometimes, so that's why I'm asking this. I'm 
trying to guide some developers about where to look in the Dojo 
documentation about making some things more accessible. The symptoms 
mainly are that if you can hover over something to expand it, that ability 
is not being spoken by JAWS. Or if you can click something, JAWS isn't 
saying that you can. I'd like to give sound guidance. 
 
At the same time, I notice, with other scripting technologies, that NVDA 
will say that something is clickable when JAWS doesn't. So I guess that 
under this question is also the broader question of when do you know that 
something is coded correctly and you're encountering the screen reader's 
inability or whatever to follow the standard? But the first question is 
the most important for now.
 
Thanks.
 
Jim 
 
 


This e-mail and any attachments to it are confidential and are intended 
solely for use of the individual or entity to whom they are addressed. If 
you have received this e-mail in error, please notify the sender 
immediately and then delete it. If you are not the intended recipient, you 
must not keep, use, disclose, copy or distribute this e-mail without the 
author's prior permission. The views expressed in this e-mail message do 
not necessarily represent the views of Highmark Inc., its subsidiaries, or 
affiliates.