Opened 12 years ago

Closed 12 years ago

#3739 closed defect (fixed)

screen reader no longer speaking menu items

Reported by: Becky Gibson Owned by: simonjb
Priority: high Milestone: 0.9
Component: Accessibility Version: 0.9
Keywords: Cc: Becky Gibson
Blocked By: Blocking:

Description

Testing menu in nightly (on July 12) with the window-Eyes screen reader the menu items are no longer spoken. The screen reader speaks "menu opened" when menu (or submenu) is first opened but does not speak the actual menu item. It also speaks "menu closed" when menu is closed.

I didn't investigate what might have broken this. JAWS DOES speak the items so hopefully this isn't just something I am doing wrong!

Change History (5)

comment:1 Changed 12 years ago by simonjb

Status: newassigned

comment:2 Changed 12 years ago by Becky Gibson

I have bee having some problems with my Window-Eyes install so this may be a local problem but I need someone else to verify/test.

comment:3 Changed 12 years ago by simonjb

Window-Eyes seems to be reading the menu items fine for me on:

http://archive.dojotoolkit.org/dojo-2007-07-12/dojotoolkit/dijit/tests/test_Menu.html

However, I'm seeing a different problem on the current trunk:

Window-Eyes is saying "menu closed" after each item. I did some investigation with Microsoft's AccEvent? tool and it looks like focus is going to the document in between moving from one item to another.

comment:4 Changed 12 years ago by bill

Hmm, that focus thing doesn't sound good. I added a blur() call to Menu in my recent checkin [9613], since it doesn't make sense to have focus on a MenuItem? in a closed (ie, not displayed) Menu. Is that what broke it? I think we can take that out. (Does focus automatically disappear when the focused node's ancestor gets set to display:none?)

comment:5 Changed 12 years ago by bill

Resolution: fixed
Status: assignedclosed

(In [9634]) Remove code to blur() menu item when it is no longer the selected item. Confuses Windows-Eyes screen reader (fixes #3739)

Also, blur seems to be occuring too late (when a context menu closes, I meant for the blur() to happen first, followed by focusing on the thing that had focus before the context menu opened, but seems to happen the other way. (refs #3705)

Note: See TracTickets for help on using tickets.