Bug 368860 - Unable to invoke actions menu
Summary: Unable to invoke actions menu
Status: RESOLVED FIXED
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: Client (show other bugs)
Version: 0.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.4 M2   Edit
Assignee: Susan McCourt CLA
QA Contact: Carolyn MacLeod CLA
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks: 365361
  Show dependency tree
 
Reported: 2012-01-17 13:04 EST by Max Li CLA
Modified: 2012-02-10 13:05 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Max Li CLA 2012-01-17 13:04:08 EST 
Build Identifier: 0.3

While using the screen reader JAWS, tabbing to the actions menu button (on any page with the widget) and subsequently trying to bring it up does not work. 

It may be worth noting that if one uses a mouse to bring it up, the actual menu itself is controllable with the keyboard. Also, this problem does not seem to occur if not using a screen reader.

Reproducible: Always
Comment 1 Susan McCourt CLA 2012-01-17 13:16:30 EST 
interesting.
Can you be specific with a particular page/button example?
For example in the navigator I can tab to the menu icon and use space bar or enter key to invoke the menu (but I don't have a screen reader installed).

If it doesn't work, it sounds like a dojo/dijit bug.  Could you try the same thing on this page?

http://download.dojotoolkit.org/release-1.5.0/dojo-release-1.5.0/dijit/themes/themeTester.html?theme=nihilo

tab to the widget labeled "Drop Down" and see if the problem occurs there.  If so, then it's a general dijit bug.  If not, then we have a more specific problem.
Comment 2 Max Li CLA 2012-01-17 13:46:36 EST 
It seems to happen on any page with this sort of menu button (i.e. navigator (both in the file tree and the favorites menu), repositories).

The widget seems to work on the page you gave me, so it doesn't seem to be a dijit bug.
Comment 3 Max Li CLA 2012-01-24 09:18:11 EST 
I have fixed this bug in the following repository in the accessibility branch.
https://github.com/max-li/orion.client.git
Comment 4 Felipe Heidrich CLA 2012-01-24 10:06:57 EST 
(In reply to comment #3)
> I have fixed this bug in the following repository in the accessibility branch.
> https://github.com/max-li/orion.client.git

404 
Max can you check the link ?
Comment 5 Felipe Heidrich CLA 2012-01-24 10:20:49 EST 
(In reply to comment #4)
> (In reply to comment #3)
> > I have fixed this bug in the following repository in the accessibility branch.
> > https://github.com/max-li/orion.client.git
> 
> 404 
> Max can you check the link ?

This one https://github.com/max-li/orion.client/commit/af3205698ac893ad233ce79fd6bc8511473888e5 ?
Comment 6 Max Li CLA 2012-01-24 10:31:26 EST 
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > I have fixed this bug in the following repository in the accessibility branch.
> > > https://github.com/max-li/orion.client.git
> > 
> > 404 
> > Max can you check the link ?
> 
> This one
> https://github.com/max-li/orion.client/commit/af3205698ac893ad233ce79fd6bc8511473888e5
> ?

Yes, that is the one.
Comment 7 Susan McCourt CLA 2012-01-24 11:24:40 EST 
I'm working in here today, will commit.
Thank you, Max!
Comment 8 Susan McCourt CLA 2012-01-24 18:52:21 EST 
pushed.  I'm not running JAWS, but I tested that it works the same otherwise, and I understand how this could fix the problem.

Thanks, Max!