Modal - Issue with chromevox and current focus
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Steps to reproduce 🕹
Video Examples:
Link to live example: MUI React Dialog Page
Steps:
- Go to any example on MUI which inherits from Modal: Dialog, Drawers
- Open Chromevox screen reader for ChromeOS. The shortcut is ctrl + alt + z
- Interact with component and see focus keeps getting moved outside the component
Current behavior 😯
Interact with component and see focus keeps jumping outside the dialog/drawer.
I removed the -1 tabindex from the dialog container, and placed it on the element with the dialog role instead, which seems to have helped, but that might break the component for others if they are focusing on the outer container.
Expected behavior 🤔
Focus should not be jumping outside the dialog.
Context 🔦
I'm not 100% sure if this is the same issue mentioned on Issue #23827
Any of the MUI Dialogs/Drawers are giving some focus issues when using the chromevox screen reader on ChromeOS.
Your environment 🌎
npx @mui/envinfo
Don't forget to mention which browser you used.
Output from `npx @mui/envinfo` goes here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior on the MUI React Dialog and Drawer examples with ChromeVox on ChromeOS. Compare focus behavior in the Modal-based components, including the reported tabindex change, and review Issue #23827 for related context. Done means focus no longer jumps outside the dialog or drawer while interacting with it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100