-
Notifications
You must be signed in to change notification settings - Fork 22
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
Output of child elements #59
Comments
I think this is a good idea to call out, but would be better served as information in HTML AAM and the ARIA specifications specifically. accname defines how the accessible name is calculated, but the other specs should help define / advise how different elements and roles expect child content to be reached. I'd recommend this issue be closed and taken up in the appropriate specs. |
Do you think I should post the ticket on ARIA and HTML AAM? |
Not HTML AAM please. There are already issues there (as you've already been commenting on) that cover this topic. |
@scottaohara: What HTML AAM issues do you mean? I can't find them |
The HTML AAM issue you linked to here. It's related and we don't need a duplicate issue for it. |
If I understand it correctly, the AccName specification says nothing about the output of child elements when a parent element is labeled. This should be added.
Example:
Here the text content in the region is output as soon as you navigate into the region.
Here the text content of the button is never output.
So the question is: For which elements are child elements not output?
One could assume that it applies to all elements whose children implicitly have role=presentation. But this is probably not true, because a link does not implicitly have role=presentation, but I would expect a link is output without its content, if it was labeled with aria-label or aria-labelledby.
See also: w3c/html-aam#160 (comment)
The text was updated successfully, but these errors were encountered: