NEW 266456
AX: Change to element's aria-describedby value doesn't update its announced description
https://bugs.webkit.org/show_bug.cgi?id=266456
Summary AX: Change to element's aria-describedby value doesn't update its announced d...
Darin Senneff
Reported 2023-12-14 21:00:14 PST
When using iOS Safari + VoiceOver (17.2): if an item has a description set via the 'aria-describedby' attribute, and then the value of 'aria-describedby' changes, the item's announced description doesn't update. Steps to reproduce: 1. Visit test link in iOS Safari with VoiceOver: https://codepen.io/dsenneff/pen/xxMoReR/b0a1de7d369927086875385bbe2139cd?editors=1010 2. Navigate to the 'apple' button and hear the announcement: 'apple, description fruit'. Observe in devtools that the item's 'aria-describedby' value points to the 'fruit' element. 3. Activate the button, which swaps its 'aria-describedby' value. Observe in devtools that the item's 'aria-describedby' value does change to point to the 'vegetable' element. 4. Navigate away from the button, then back to it and hear the original announcement: 'apple, description fruit' The button's announcement should change to reflect the updated description, 'apple, description vegetable', but it does not. Other browser + screen reader combinations do update the element's description, including MacOS Safari + VoiceOver.
Attachments
Radar WebKit Bug Importer
Comment 1 2023-12-14 21:00:30 PST
Darin Senneff
Comment 2 2024-06-25 12:34:38 PDT
Issue still present in iOS 18's developer beta #2, despite the iOS 18 beta's release notes including the following text: "Fixed updating 'aria-describedby' text after the targeted element changes its subtree." -Source: https://webkit.org/blog/15443/news-from-wwdc24-webkit-in-safari-18-beta/#bug-fixes-and-more Safari + VoiceOver's handling of accessible descriptions continues to be a huge support gap. Oftentimes, an accessible description is used to provide error or status messages, or instructions, which may change after initial page load. Being unable to rely on this consistently means developers can't reliably provide certain information to screen reader users in Safari browsers.
Note You need to log in before you can comment on or make changes to this bug.