-
Notifications
You must be signed in to change notification settings - Fork 118
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
do we need a focusable definition #1936
Comments
an example use case is in https://w3c.github.io/aria/#conflict_resolution_presentation_none |
HTML gives a detailed but somewhat complex description of the focusable area. Furthermore there are some differences between browsers, in which situation is an element / area focusable and with wich method:
|
Current PR doesn't include a lot of the items discussed as necessary in the original PR attempt: w3c/aria-common#39 |
FWIW, I'm not sure I agree that an ARIA definition of "focusable" counts as "editorial." |
Android even adds up the term screenreader-focusable ;): Well they mean the reading "focus" of Talkback, but annother example how widespread the term is used. |
@cookiecrook writes in the comments to the old PR from 2020:
Of course I studied all previous comments and I thought, we have only to informativly describe the concept of "focusable" and it would be enough to link to the colex and - I think - complete definition of "focusable" in the HTL spec. Why should we go into details in our glossary? |
Followup from editors call: do we need a focusable definition
Defined(ish) in HTML and SVG - should we point to those definitions and how?
The text was updated successfully, but these errors were encountered: