-
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
Stop automatically exposing details relation for figure -> figcaption #564
Comments
@aleventhal maybe you're thinking of w3c/aria#2224 ? |
Thanks @pkra . I mentioned it in a comment in that PR. But it hasn't been changed in that PR. Should we keep it as a separate issue? Or do you want to add to that PR? |
i have updated the PR |
@aleventhal to be fair though, since the PR never landed because we've been waiting on other browser to implement, chromium should be fine to remove it even without the PR update. |
let's keep this issue open so it can come up in triage - and then this can be a reminder for people to re-review the PR so we can get it merged asap |
This was harmful because it caused JAWS to turn off details announcements, because it was too verbose on certain web pages. These elements are already close by in the DOM/a11y tree so there is really no point in doing this. See w3c/html-aam#564 Bug: none Change-Id: I0be887c382dc3b6768571f3f8770312e619273a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5891779 Commit-Queue: Benjamin Beaudry <[email protected]> Reviewed-by: Benjamin Beaudry <[email protected]> Auto-Submit: Aaron Leventhal <[email protected]> Cr-Commit-Position: refs/heads/main@{#1361785}
Discussed in today's ARIA working group meeting: https://www.w3.org/2024/11/14-aria-minutes.html#d8ca |
FWIW Chromium stopped doing this in milestone 131, to match other browsers. So we just need to make it official in the spec. |
I thought we had filed this, so there may be a dupe somewhere.
We should stop automatically exposing the details relation between figure and figcaption. They are nearby in the DOM anyway. It was so noisy on some pages that it caused JAWS to stop reading details relation entirely.
The text was updated successfully, but these errors were encountered: