-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JAWS not allowing keyboard control of the datepicker #42
Comments
Hi, Yikes, this is horrible news. I shall remove the "grid" role which should do the trick. I take accessibility very seriously so shall treat this as a priority. Many thanks for the info. |
Hi Again, My laptop has decided to die on me so I had to resort to editing the script using the github code editor. I ave removed the grid, rowheader and columnheader roles to see if this fixes the accessibility problems. I still have to migrate the update to both the minified version of the file and the gh-pages version. Regards, |
Latest version moves these changes into the minified file also. |
...and I closed the issue without thinking. Reopening now. I am currently working on a V7 of the control that updates the HTML structure (to make it easier to style and to add appropriate aria- roles and states) and, if time permits, updates the CSS to use BEM syntax. Shall keep this thread updated with a status. |
I've also encountered this issue. |
While JAWS is running, the datepicker is not controllable via keyboard. I see that you applied role=application to the div and role=grid to the table and I'm not sure if one is overriding the other but it appears that the application role isn't being respected in order to release the control of the screen reader. The problem seems to be present in the latest version of JAWS and NVDA.
If it helps, here is a demo of a datepicker that works with JAWS:
http://whatsock.com/tsg/Coding%20Arena/ARIA%20Date%20Pickers/ARIA%20Date%20Picker%20(Basic)/demo.htm
And some explanation of some details of the tag nuances:
http://whatsock.com/training
The text was updated successfully, but these errors were encountered: