The dialog guide already covers native and custom dialogs, focus trapping, accessible names, initial focus, focus return, and screen-reader behavior. This is not a request to duplicate or replace that guidance.
Would an external worked incident be useful as an optional companion? I maintain FrontendAtlas and published a public exercise showing several modal failures occurring together:
https://frontendatlas.com/incidents/modal-screen-reader-failure
It covers focus escaping behind the dialog, a missing accessible name and announcement, failed focus return, keyboard and screen-reader checks, remediation steps, and a behavioral regression guard.
If external case studies are not in scope, please close this issue. I will not open a pull request unless the maintainers invite one.
Disclosure: I maintain FrontendAtlas. The incident exercise is public; optional Premium material elsewhere on the platform is clearly labeled.
The dialog guide already covers native and custom dialogs, focus trapping, accessible names, initial focus, focus return, and screen-reader behavior. This is not a request to duplicate or replace that guidance.
Would an external worked incident be useful as an optional companion? I maintain FrontendAtlas and published a public exercise showing several modal failures occurring together:
https://frontendatlas.com/incidents/modal-screen-reader-failure
It covers focus escaping behind the dialog, a missing accessible name and announcement, failed focus return, keyboard and screen-reader checks, remediation steps, and a behavioral regression guard.
If external case studies are not in scope, please close this issue. I will not open a pull request unless the maintainers invite one.
Disclosure: I maintain FrontendAtlas. The incident exercise is public; optional Premium material elsewhere on the platform is clearly labeled.