Skip to content
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

accesskey should not function on inert content #40

Open
jnurthen opened this issue Dec 10, 2016 · 1 comment
Open

accesskey should not function on inert content #40

jnurthen opened this issue Dec 10, 2016 · 1 comment

Comments

@jnurthen
Copy link

If accesskey is specified on content which is inert it should be ignored. Currently if I add an accesskey on the checkbox in the demo pages, then I can check it using the accesskey even if it is inert.

@rodneyrehm
Copy link

Setting input elements to disabled prevents the accesskey behavior. If that's not an option things may get a bit tricky. Here's an excerpt of accesskey behavior tests I did ~2 years ago:

Chrome will not focus a link, but execute its default action (navigate to href), while Trident will focus the <a> element and not perform the default action. Trident does not dispatch click events (the default activation of otherwise non-interactive elements), except for <input> elements. Chrome on Windows won't dispatch a click event for <input type="checkbox">

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants