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
Inconsistent behaviour. Pressing [Enter] or [Space] does not register as a 'click' on some modal windows #5345
Comments
It also happens with the Twitter Bootstrap modal demos. I encountered this issue using Chrome 49.0.2623.87 (Official Build) m (32-bit). I spent some time testing it, and it seems to come down to the role="dialog" ARIA attribute on the parent modal element. If present, enter/space won't trigger a click event on buttons or links, and moves focus back to the modal parent. But when the role attribute is removed, clickable items work as expected. |
+1 |
The URL http://itstiredinhere.com/accessibility/ no longer seems to be active. |
The Twitter Bootstrap modal demos are still available, I was not able to reproduce this with Chrome Version |
I can reproduce this issue with chrome 71 and with Firefox 64.0.2.
Actual: when pressing enter or space on "close button, the modal dialog still remains focused. You can only get out of it by tabbing multiple times. Expected: the modal should be closed when pressing enter or space bar on the close button. |
I can't get that Bootstrap dialog to close at all. Pressing enter on it in focus mode, clicking the buttons, nothing works. My feeling is that this is a bug in the example. It's also confusing because there are two close buttons, one at the top and one near the bottom. |
In this case, should we close this issue as invalid? We do not have any updates from the initial author since years. |
I am closing this issue as abandoned due to missing updates from the initial author. |
Reported by stephen.khuu on 2015-09-09 16:26
On Chrome, using the NVDA reader to navigate to the 'close' button on a dialog and using [or Space to click on the close button does not always work.
When it doesn't work, hitting [or Space will just cause the 'close' button to go out of focus.
Happens on Chrome v44.0.2403.157, Windows 10 Pro
Example of where it's not working:
http://itstiredinhere.com/accessibility/ (look for the launch accessible modal)
Examples of where it is working:
http://accessibility.oit.ncsu.edu/training/aria/modal-window/version-2/
http://www.visionaustralia.org/digital-access-dialog
http://www.accessiblemootoolsdemo.iao.fraunhofer.de/Mootools_Widgets/ (dialog widget)
The text was updated successfully, but these errors were encountered: