Closed
Bug 147934
Opened 23 years ago
Closed 20 years ago
Active Accessibility: expose correctly for buttons that have popups
Categories
(Core :: Disability Access APIs, defect, P5)
Tracking
()
RESOLVED
FIXED
mozilla1.9alpha8
People
(Reporter: dsirnapalli, Assigned: aaronlev)
References
(Blocks 1 open bug)
Details
(Keywords: access)
I used the following piece of code --------------------------------------- // Testing Menu For Accessibility <menu> <button label="Click Me"/> <menupopup> <menuitem label="Choice 1"/> <menuitem label="Choice 2"/> <menuitem label="Choice 3"/> </menupopup> </menu> ----------------------------------------Open Inspect tool and click on hightlight rectangle.Then move the cursor on to the button. then click on "navigate to parent". watch mozinspect. State shows "focusable,". State should show "focusable, haspopup".
Assignee | ||
Comment 1•23 years ago
|
||
Right now we have: <menu> <button /> <menupoup /> </menu> And we are making it look like: ROLE_MENUITEM -> ROLE_BUTTON We need to figure out what it is supposed to be exposed as.
Summary: In Inspect tool state shows only "focusable" for menu node. → In Inspect tool state shows only "focusable" for menu node.
Assignee | ||
Updated•23 years ago
|
Assignee | ||
Comment 2•22 years ago
|
||
After visiting with a screen reader vendor, it looks like this might be just fine the way we have it. Will check with more vendors.
Priority: P1 → P5
Target Milestone: mozilla1.0.1 → Future
Assignee | ||
Updated•20 years ago
|
Target Milestone: Future → mozilla1.9beta
Assignee | ||
Comment 3•20 years ago
|
||
We do support the HASPOPUP state now, for XUL buttons of type="menu" or type="menu-button". http://lxr.mozilla.org/seamonkey/source/accessible/src/xul/nsXULFormControlAccessible.cpp#156 This was fixed recently.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•