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] Version: git (not yet released)
Keywords: a11y Cc:
Blocked by: Blocking:


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.


  1. 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.

  1. 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.

  1. 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 Scott González

Component: ui.core[meta]
Keywords: a11y added
Status: newopen
Version: 1.8.16git

comment:2 Changed 11 years ago by Scott González

Resolution: invalid
Status: openclosed

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.

Note: See TracTickets for help on using tickets.