-
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
Is it possible to expose descendants of childrenArePresentational? #292
Comments
try adding a role to the map element, for example
|
Thanks for the quick response @stevefaulkner, I should've described my previous attempts, which include adding I've tried various things, here's screenshot of only a few attempts I tried just now based on your example suggestion: |
@Malvoz thanks for the info, I see that it is causing issue in chrome, works fine in Firefox.
Will look into it more on the morrow, it is late here now :-) |
Is it specified somewhere that |
This behavior is not specified in this spec. Rather, I filed a bug against chromium https://bugs.chromium.org/p/chromium/issues/detail?id=1208405 since Firefox and Safari are working as expected. Leaving this open for tracking purposes, but the ball should be in Chromium's court to fix this. |
Oops, I forgot to link the chromium bug I filed: https://bugs.chromium.org/p/chromium/issues/detail?id=1147035. Sorry! In that bug I incorrectly refer to wanting to change the implicit ARIA role, I probably meant to say ARIA semantics, I corrected that statement in a later comment. I hope it's not too confusing, it seems on their response I got my point across. However, because it seemingly isn't defined anywhere that |
yes @Malvoz, please refer to mine. it's not really even that the children are treated as presentational (eg role=presentation) - if it was then the child content would still be exposed, but have no roles exposed. The content is rather being flat out ignored. From what i saw in testing today, the accessibility panels in chrome were exposing the correct information - but something is still weird since, again, regardless of being exposed in the a11y panel, none of the content is actually accessible to the screen readers when using only chromium browsers |
@scottaohara The bug you filed was marked as fixed, though I'm not seeing (hearing) any improvements using NVDA. Perhaps I've misunderstood the bug and the fix, perhaps it should now be considered an NVDA issue that the non-area elements aren't announced in your attached HTML file? |
cc @aleventhal per above comment. i haven't looked into it / didn't notice it was marked as fixed. |
The Maps For HTML Community Group has a custom
<map>
component, but in testing I had found that no child elements of<map>
(I believe anything that isn't<area>
) are being exposed in the accessibility tree.Is it possible to tell UAs to expose descendants of
childrenArePresentational
?The text was updated successfully, but these errors were encountered: