Skip to main content

Search and Top Navigation

#7860 closed bug (notabug)

Opened November 10, 2011 05:13AM UTC

Closed May 25, 2012 12:09PM UTC

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

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.

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

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

Attachments (0)
Change History (2)

Changed November 10, 2011 01:56PM UTC by scottgonzalez comment:1

component: ui.core[meta] ui.dev
keywords: → a11y
status: newopen
version: 1.8.16git

Changed May 25, 2012 12:09PM UTC by scottgonzalez comment:2

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.