-
Notifications
You must be signed in to change notification settings - Fork 360
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
Why dialog-modal pattern don't use HTML <dialog> tag ? #3160
Comments
see #3148 (comment) |
I understand, thank you very much! |
Notethat in the case of html dialog element, browsers do not trap focus. So, it does not yet give you the option of creating an actual modal. This is particularly problematic for screen reader users as it is unexpected and confusing to leave a dialog with the tab key. It also reduces navigation efficiency by making the tab ring unnecessarily long. |
This sounds as if the keyboard focus goes to the rest of the page outside the modal dialog. However, this is not the case. The focus only goes to the browser and then back to the modal dialog. I don't think this is so problematic - and as far as I know, it was a conscious decision to implement it this way. F6 can also be used to quickly switch between the browser and modal dialog. |
It seems that dialog-modal pattern is not using tag.
Is there any reason not to use tag?
https://github.com/w3c/aria-practices/tree/main/content/patterns/dialog-modal
The text was updated successfully, but these errors were encountered: