Opened 14 years ago

Closed 14 years ago

#4311 closed defect (fixed)

Combobox Previous Choices/ More Choices not spoken by screen reader

Reported by: Becky Gibson Owned by: ptbrunet
Priority: high Milestone: 1.0
Component: Accessibility Version: 0.9
Keywords: Cc: [email protected]
Blocked By: Blocking:


on quick inspection the value of the input element does seem to get updated with "Previous Choices" and "More Choices" but the screen reader doesn't speak the new value. One option is to add a call to wai.setAttr() to update the valuenow for the input element. However, if you do this in _autoCompleteText() the regular options get spoken twice when you arrow to them. This may have something to do with pageup/down being pressed rather than up/down - need to check with screen reader vendors.

Change History (3)

comment:1 Changed 14 years ago by ptbrunet

Cc: [email protected] added; ptbrunet removed
Owner: changed from Becky Gibson to ptbrunet

comment:2 Changed 14 years ago by ptbrunet

I added code to set the valuenow attribute and now page up and down are spoken correctly. There is double annoucements of the value when pressing up and down. However, the only msaa event fired is a valuechange event. Rob Gallo at Freedom Scientific said he'll work on the double speaking issue. I am sending a patch to Becky.

comment:3 Changed 14 years ago by Becky Gibson

Resolution: fixed
Status: newclosed

(In [10675]) fixes #4311 commit for peteb (IBM CLA). Need to add call to dijit.wai.setAttr() so prev/more choices options get spoken by screen reader. Causes JAWS to speak each option twice but this is an issue the JAWS folks are aware of. Works OK in Window-Eyes

Note: See TracTickets for help on using tickets.