Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AVT3: JAWS read "none has been selected" when user actually selects Android or IOS in the select platform dropdown list #6840

Closed
pankaj-kumar34 opened this issue Sep 15, 2020 · 4 comments · Fixed by #7889
Labels

Comments

@pankaj-kumar34
Copy link

=====ENVIRONMENT=====
Browser: chrome
IBM CI 162 Checkpoint Violation: IBM 1.3.1 Info and Relationships
IBM Guidance: https://www.ibm.com/able/guidelines/ci162/info_and_relationships.html

=====DEFECT DESCRIPTION=====
JAWS read "none has been selected" when user actually selects Android or IOS in the select paltforms dropdown list

  1. Press tab to the 'Select platform' menu and press space to open the listbox
  2. Press arrow key to the Android/IOS and press space to select Android/IOS

image

@dakahn
Copy link
Contributor

dakahn commented Sep 24, 2020

Confirmed with both JAWS 2020 and NVDA

@deepika-bachu
Copy link

@dakahn - Can we have an update on this- this affects our product's accessibility compliance due to the dependency. Please look into this.

@dakahn
Copy link
Contributor

dakahn commented Jan 21, 2021

No update to give. This is a high priority issue and a still a problem. @carbon-design-system/developers this fix will potentially involve a refactor of the component to use Downshift's useMultipleSelection hook. It's on our radar though, thanks for the ping.

@dakahn
Copy link
Contributor

dakahn commented Feb 23, 2021

Circling back on this. On selection JAWS reads "undefined has been selected". If the list box is closed and then opened list items are not properly described as "selected".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants