Open jnurthen opened 7 years ago
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 dispatchclick
events (the default activation of otherwise non-interactive elements), except for<input>
elements. Chrome on Windows won't dispatch aclick
event for<input type="checkbox">
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.