-
Notifications
You must be signed in to change notification settings - Fork 27
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
Title should not contribute to accName for generic elements #506
Comments
related to w3c/aria#1981 closing #495 since apparently i had filed similar before |
What is the change you are suggestion, specifically, in HTML? I'm just confused about why this issue is here... |
Discussed in today's meeting: https://www.w3.org/2023/11/02-aria-minutes.html#t10 It was decided to schedule a deep dive for this topic. |
I interpret @scottaohara's request to be the #comp_tooltip step in AccName should be changed from:
To:
If I'm correct, then @spectranaut is right that this issue should be moved from HTML-AAM to AccName. |
But then if |
it is already in AccName: "If the root node's role prohibits naming, return the empty string"
title is usually used for description. This means that a div with a title could theoretically have a description but no name. But then Accname would also have to be changed (see above quote from Accname). Whether this makes sense is another question, as the AT normally does not output a description for generic elements. |
And the engines don't usually expose a generic element with no label, so there may be nothing to hang the description on. |
@accdc and I have dug into this some more. I'd like to have a deepdive on this topic and I would like to present on the topic. We need a good date for this though, considering that holidays are soon. |
see the title of this issue. authors 'shouldn't' be naming generics, but a title could provide a name if no other method is provided - but it's probably the author's intent to provide a description in these cases (what good that will do, i don't know).
The text was updated successfully, but these errors were encountered: