Open
Bug 1304631
Opened 8 years ago
Updated 2 years ago
Menubars and menus (ARIA and browser) should implement AtkSelection
Categories
(Core :: Disability Access APIs, defect, P3)
Tracking
()
NEW
People
(Reporter: jdiggs, Unassigned)
References
(Blocks 1 open bug)
Details
Steps to reproduce: 1. Launch Firefox and load: "data:text/html,<div role="menubar"><div role="menuitem">File</div></div>" 2. Launch Accerciser and use it to examine the accessible menubar objects in both the Firefox toolbar and the document content. Expected results: Accerciser would indicate the selection interface was implemented for each menubar. Actual results: Accerciser indicates the selection interface is not implemented for either menubar. If you perform the same steps looking at a Gtk+ application (e.g. the gtk-demo and gtk3-demo Application Class demos), you'll note that the selection interface is implemented. Orca uses this interface to determine the currently selected menu and menu items, but cannot do so in Gecko apps. This means each menu/menu item must be examined to see if it has STATE_SELECTED, which can be non-performant in menus with many children. As a general rule, the parent container of things which can have STATE_SELECTED are expected to implement the accessible selection interface.
Updated•7 years ago
|
Priority: -- → P3
Reporter | ||
Comment 1•6 years ago
|
||
Updating the summary to include menus. Firefox's and Thunderbird's menus (e.g. the File menu) don't seem to implement the selection interface either.
Summary: Menubars (ARIA and browser) should implement AtkSelection → Menubars and menus (ARIA and browser) should implement AtkSelection
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•