Opened 7 years ago

Closed 5 years ago

Last modified 5 years ago

#17238 closed defect (fixed)

[PATCH][CCLA] JAWS does not initially announce dijit.form.Select selected value

Reported by: mikeb Owned by: Bill Keese <bill@…>
Priority: undecided Milestone: 1.8.11
Component: Dijit - Form Version: 1.9.0
Keywords: a11y, JAWS Cc:
Blocked By: Blocking:

Description

If you navigate to this page: http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_Select.html with JAWS and tab into the first dijit.form.Select dijit, JAWS does not read the first selected option. For example, JAWS will say "Test one colon list box collapsed" - it should read out "Virginia." The reason for this is that the "aria-selected" attribute is not applied to the <span> with role="option". Interestingly, when the user activates the listbox, dijit creates a new drop down with all of the available options and correctly applies aria-selected attribute, which is why JAWS will read the options as you scroll through.

The fix is to just apply aria-selected to this initial DOM node.

Attachments (1)

a11y-JAWS-dijit-select.patch (696 bytes) - added by mikeb 7 years ago.
Add aria-selected to the initial option in dijit.Select so that JAWS reads it - please proxy commit for Michael Billau CCLA on file with IBM

Download all attachments as: .zip

Change History (8)

Changed 7 years ago by mikeb

Add aria-selected to the initial option in dijit.Select so that JAWS reads it - please proxy commit for Michael Billau CCLA on file with IBM

comment:1 Changed 7 years ago by mikeb

Keywords: a11y JAWS added
Owner: set to Douglas Hays
Status: newassigned

This raises another accessibility issue in that now when you tab into the Select, JAWS will read the name of the selected item, followed by "one of one", which indicates that there are no other options to select. We are working to figure out a solution to this (lesser priority) issue.

comment:2 Changed 6 years ago by Douglas Hays

Owner: Douglas Hays deleted
Status: assignedopen

comment:3 Changed 5 years ago by Bill Keese <bill@…>

Owner: set to Bill Keese <bill@…>
Resolution: fixed
Status: openclosed

In a0064e10166b45c44a9bf89c73b1e966569a5450/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:4 Changed 5 years ago by Bill Keese <bill@…>

In 86fea8b3585216d96cfbda073e16a92148b745e3/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:5 Changed 5 years ago by Bill Keese <bill@…>

In b37775f239aea44a7e1b777d8e794e312cd00a45/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:6 Changed 5 years ago by Bill Keese <bill@…>

In 07423ea58e060020c664610359449c9e7c99db48/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:7 Changed 5 years ago by bill

Milestone: tbd1.8.11

Checked in fix for 1.11, and backported to 1.8.11, 1.9.8, and 1.10.5.

Note: See TracTickets for help on using tickets.