Tracker for aria-describedby to use AXCustomContent. aria-description support and AXCustomContent was added in bug 206253.
<rdar://problem/100736814>
https://github.com/w3c/core-aam/pull/142
Hi, I'm curious the priority of this issue? Chrome is landing aria-description exposed in AXCustomContent (https://chromium-review.googlesource.com/c/chromium/src/+/4015695), and we would like to follow up exposing aria-describedby in the same way.
@James Craig, we implemented this in Chrome and unfortunately it was reverted because people weren't expecting the user-facing change part of it. One question, is it worth considering that for very short descriptions, needing to hear "more content available" and go through the menu/command is counterproductive? Maybe it should just read the description if it's on the short side, according to some heuristic. Also am hopeful that this change soon. I'm hesitant to reland Valerie's change to Chrome if WebKit isn't going to match.
(In reply to Aaron Leventhal from comment #4) > @James Craig, we implemented this in Chrome and unfortunately it was > reverted because people weren't expecting the user-facing change part of it. > > One question, is it worth considering that for very short descriptions, > needing to hear "more content available" and go through the menu/command is > counterproductive? Maybe it should just read the description if it's on the > short side, according to some heuristic. > > Also am hopeful that this change soon. > I'm hesitant to reland Valerie's change to Chrome if WebKit isn't going to > match. Still planning to land this in 2023. I'll let James weigh in on whether he thinks this is the right course of action as well, but I do believe this is the design of the platforms. Extra info and actions are available through rotors in order to reduce chatter.
Additional comments from web authors on a11y slackers https://web-a11y.slack.com/archives/C042TSFGN/p1679073626809829
See bug 255812
*** This bug has been marked as a duplicate of bug 255812 ***