Opened 11 years ago
Closed 11 years ago
#7860 closed bug (notabug)
Menubar: accessibility
Reported by: | ezufelt | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.9.0 |
Component: | [meta] ui.dev | Version: | git (not yet released) |
Keywords: | a11y | Cc: | |
Blocked by: | Blocking: |
Description
Firefox 8.0 JAWS 13 Menubar demo 1.9pre
It is possible to tab to the first menu and to navigate across with arrow keys and down each menu with arrow keys.
Problems
- If tabbing through the page from 'theme switcher widget' the order is: 'File', 'Open', 'Default functionality'. I am not sure if 'Open' is from the first
or second menubar.
- When tabbing in reverse from 'Default functionality' the order is: 'Full screen', 'Open', 'File'.
This doesn't seem consistent, I am not sure if there are guidelines or a best practice around this.
- I can begin interacting with a menubar / menu with the enter key, but cannot stop interacting (return to virtual PC cursor) with the escape key. Using
the escape key to stop interacting with controls (e.g. Textarea) is a very common and expected pattern.
Change History (2)
comment:1 Changed 11 years ago by
Component: | ui.core → [meta] ui.dev |
---|---|
Keywords: | a11y added |
Status: | new → open |
Version: | 1.8.16 → git |
comment:2 Changed 11 years ago by
Resolution: | → invalid |
---|---|
Status: | open → closed |
Note: See
TracTickets for help on using
tickets.
Closing as menubar is moved to a future release. We'll come back to a full accessibility review when we're ready to bring it back into master.