-
Notifications
You must be signed in to change notification settings - Fork 4
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
Top Nav mouse-over menus are not accessible #68
Comments
Good news: I tested on various iOS and android devices and the drop down did work. However once the drop down menu opened it wouldn't close (but definitely not a phase one deal-breaker). |
Originally, I was using I've changed that code so the dropdowns no longer use The next step is to make them visible when they are tabbed to. I think that can be accomplished with jquery, which is loaded by default on every page. Changing every main navs HTML is not optimal at this point, but if it's absolutely necessary we can consider it. |
Excellent. I'm going to close this issue, since it's about the keyboard accessibility. I'll open another issue for making them visible, and set that to Could Wait. See #284. |
In the UCSC Technology Accessibility and Civil Rights in Higher Education workshop for Global Accessibility Awareness Day (5-21-2015) workshop leader Don Barrett, Assistive Technology Specialist, US Department of Education / Office for Civil Rights mentioned that this is still an issue in both the 1:00 - 3:00 pm and the 3:30 - 5:30 pm sessions. |
@thomasgardner Are you sure you don't mean #284? Len's issue here was that the links were completely inaccessible from the keyboard. I fixed that issue. Issue #284 covers the other problem, which is that the dropdowns need to be visible when tabbed to. |
Len Burns reported this issue. "The page contains a menu activated by a mouseover, the "Undergraduate," link. This is completely inaccessible to a screen reader user. In fact, without close scrutiny, its existence would go unnoticed. This would also present severe problems for other users of adaptive technology who rely upon the keyboard. One good test strategy for developers is to unplug the mouse and explore a page using only the keyboard. The question is, can the page still be fully utilized, or are parts inaccessible or contain areas where a keyboard user will become trapped."
The text was updated successfully, but these errors were encountered: