-
Notifications
You must be signed in to change notification settings - Fork 58
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
summary
element (child of detail
)
#36
Comments
Thanks, @danielweck. According to https://allyjs.io/data-tables/focusable.html, the |
Very useful response, thank you. However, in our use-case we side-load arbitrary HTML documents, and we avoid as much as possible interfering with the authored markup. We also have the luxury of controlling what browser engine is used, so we can make reliable predictions about the level of support for specific features (like the focusability / tab-ability of |
Ok, @danielweck 👍 Another possibility could be to add an option to this library that allows you to add selectors to the list — so in situations like yours you could add more elements. |
I recently revisited medialize/a11y. https://github.com/medialize/ally.js/blob/master/src/is/tabbable.js Equivalent of tabbable: https://github.com/medialize/ally.js/blob/master/src/query/tabsequence.js |
I noticed that focusableAreas() in the W3C working draft of 'spatial' navigation (not 'sequential' nav) is "at risk". I wonder if the focus / tab heuristics described in the documentation of medialize/a11y match those that the W3C group have been using to design the specification. Perhaps this bit is in fact underspecified, which is why the feature is marked 'at risk'. |
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary
summary
should be added to the list:https://github.com/davidtheclark/tabbable/blob/c5ad06c85e596fea038c8a59a97324627eaa2784/index.js#L1-L11
The text was updated successfully, but these errors were encountered: