Bug 209279 - AX: Safari/VoiceOver BUG: WAI-ARIA Listbox option with aria-labelledby announces as only "text"
Summary: AX: Safari/VoiceOver BUG: WAI-ARIA Listbox option with aria-labelledby announ...
Status: RESOLVED MOVED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: Safari 13
Hardware: All macOS 10.15
: P2 Major
Assignee: Nobody
URL: https://codepen.io/mijordan/pen/NWqBqOV
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-03-19 07:56 PDT by Michael Jordan
Modified: 2023-12-21 14:53 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Jordan 2020-03-19 07:56:11 PDT 
In Safari Version 13.0.5 (15608.5.11) with VoiceOver Version 10 (708.5.7), listbox options using aria-labelledby to refer to a descendant element announce as "text."

Listbox options using both aria-labelledby and aria-describedby to refer to descendant elements announce only the aria-describedby content.

Menu menuitems seem to announce correctly. 

Chrome exhibits the correct behavior.

See https://codepen.io/mijordan/pen/NWqBqOV for a test case.
Comment 1 Radar WebKit Bug Importer 2020-03-19 07:56:18 PDT 
<rdar://problem/60633567>
Comment 2 Michael Jordan 2020-06-22 16:52:58 PDT 
Note that Safari dev tools correctly reports the accessibility name, yet VoiceOver is reading it incorrectly.
Comment 3 Michael Jordan 2020-06-22 16:54:18 PDT 
Note that the accessibility name is also not announced with aria-label on the option element.
Comment 4 chris fleizach 2023-07-03 15:19:21 PDT 
In macOS 14.0, the aria-describedby attribute is now transmuted to AXCustomContent by default and is included in the output.

There is a minor VO issue where only the label of the custom content is output. We'll be making this fix on the VoiceOver side, so we won't get another change on WebKit side for this issue
Comment 5 Brent Fulgham 2023-12-21 14:53:33 PST 
We believe this issue is resolved in the VoiceOver shipping in current macOS and iOS releases.