Closed
Bug 955066
Opened 11 years ago
Closed 11 years ago
accessibility: Context menu for input box not exposed via accessibility APIs
Categories
(Instantbird Graveyard :: Conversation, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
1.6
People
(Reporter: bugzilla, Unassigned)
References
()
Details
*** Original post on bio 1636 by James Teh <jamie AT nvaccess.org> at 2012-08-09 13:04:00 UTC ***
Str:
1. Open a conversation.
2. Focus on the input box.
3. Press the applications key or shift+f10 to open its context menu.
Expected: An accessibility event should be fired on the menu indicating that it has opened.
Actual: Accessibility APIs are not notified.
4. Press down arrow.
Expected: An accessibility event should be fired on the focused menu item indicating that it gained focus.
Actual: Accessibility APIs are not notified.
This makes this context menu inaccessible to users of assistive technology such as screen readers.
Comment 1•11 years ago
|
||
*** Original post on bio 1636 at 2012-09-01 23:17:08 UTC ***
Are you sure this is not a Gecko bug? The input box is a standard XUL textbox element and its context menu is the standard, unmodified context menu that comes with such a textbox:
http://lxr.instantbird.org/instantbird/source/instantbird/content/conversation.xml#52
Moreover, while we listen for keyboard events on the input box, pressing the applications key seems to be handled by the input box without triggering this listener, so our handler shouldn't be affecting it.
Comment 2•11 years ago
|
||
*** Original post on bio 1636 at 2012-09-01 23:19:25 UTC ***
(Tiny loophole for the last paragraph: I checked this on Linux, and bug 955065 (bio 1635) suggests context menu keys are handled differently on Linux than on Windows.)
Reporter | ||
Comment 3•11 years ago
|
||
*** Original post on bio 1636 by jamie AT nvaccess.org at 2012-09-03 02:30:15 UTC ***
(In reply to comment #1)
> Are you sure this is not a Gecko bug?
Err... it appears so. My apologies. I obviously haven't tried using the context menu on a XUL textbox before. :)
I filed a bug with Mozilla. Please close this is you'd prefer not to track this here; I'm not sure what the policy is on external bugs.
See Also: → 787858
Comment 4•11 years ago
|
||
*** Original post on bio 1636 at 2012-09-03 06:24:40 UTC ***
(In reply to comment #3)
> I filed a bug with Mozilla. Please close this is you'd prefer not to track this
> here; I'm not sure what the policy is on external bugs.
Thanks for filing a bug! We generally keep bugs open here until they're fixed in Instantbird. I added that bug as a blocking bug for the Instantbird bug though, so we'll know when it's fixed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 5•11 years ago
|
||
*** Original post on bio 1636 at 2012-09-03 09:03:03 UTC ***
(In reply to comment #3)
Thanks for checking and filing the bug!
Comment 6•11 years ago
|
||
*** Original post on bio 1636 at 2013-12-09 17:29:57 UTC ***
Fixed in mozilla 28.
Updated•11 years ago
|
Comment 7•11 years ago
|
||
See coment 6.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Target Milestone: --- → 1.6
You need to log in
before you can comment on or make changes to this bug.
Description
•