[a11y]: Modal is not providing content or expected behaviour for screen reader user #12814
Labels
component: modal
package: @carbon/react
@carbon/react
role: dev 🤖
screen-reader: JAWS
severity: 2
https://ibm.biz/carbon-severity
type: a11y ♿
type: bug 🐛
version: 11
Issues pertaining to Carbon v11
Milestone
Package
@carbon/react
Browser
Chrome, Safari
Operating System
Windows, MacOS
Package version
storybook
React version
https://react.carbondesignsystem.com/?path=/story/components-modal--default
Automated testing tool and ruleset
n/a
Assistive technology
JAWS
Description
Likely related to the focus discussions mentioned in the other issue #12727 I've opened against the modal dialog, I'm seeing odd behaviour with JAWS when trying to interact.
For passive modal, focus not place in dialog; text not announced
In addition to the issue with focus not being visually placed on the closed button, as described elsewhere, JAWS is saying nothing when the passive dialog is launched. If I press Tab once, I hear "focus sentinel button". After I tab a second time, the focus goes to the actual X control and I hear "Close button". However, the text "You have been successfully signed out" is not announced (which should have been the aria-label value).
As well, the focus is not actually trapped within the dialog. I have the ability to press Tab again and reach the focus sentinel button. Sometimes repeated pressing Tab will cycle between these. Others, the tab focus exits right out of the modal into the browser chrome. Neither should happen.
The expected behaviour here is that the focus will land on the X and JAWS will announce it's a dialog and also give read the text "You have successfully been signed out"
WCAG 2.1 Violation
Focus Order; Name, Role, Value; Info & Relationships
Reproduction/example
https://react.carbondesignsystem.com/?path=/story/components-modal--default
Steps to reproduce
I recommend opening the storybook in a new window
The text "You have been successfully signed out" is not read
Code of Conduct
The text was updated successfully, but these errors were encountered: