Opened 13 years ago
Closed 13 years ago
#6798 closed defect (fixed)
ARIA dojox.form.DropDownSelect check
Reported by: | nathan | Owned by: | becka11y |
---|---|---|---|
Priority: | high | Milestone: | 1.2 |
Component: | a11y - review | Version: | 1.1.0 |
Keywords: | Cc: | Becky Gibson | |
Blocked By: | Blocking: |
Description
I am unable to test ARIA-capability of the dojox.form.DropDownSelect?. I have tested the high contrast, no color, no images, and keyboard accessibility - but am unaware of what needs to be done for screen readers, etc.
I have tried to do as much as possible based off of the drop down button and other places I've seen aria-specific code - but could someone take a look at it and let me know what things need to change?
Change History (3)
comment:1 Changed 13 years ago by
Cc: | Becky Gibson added |
---|
comment:2 Changed 13 years ago by
Note: See
TracTickets for help on using
tickets.
Since you use the dijit.menuitem and the dropdownSelect template matches that of the dijit buttons the screen reader works correctly. However, since you have added the concept of selection in the list, you'll need to update the _updateSelection method to set the ARIA selected state to true if the item is selected, and reset it to false when the item is no longer selected. I'm not sure how you want to work that into the function but the code would be: dijit.setWaiState(this.domNode, "selected", this.selected). Or whenever you do the "addClass" you need to set selected to true and whenever you do the removeClass you need to set selected to false. Does that make sense?