Bug 218311 - AX: VoiceOver does not announce the level/depth of leaf nodes
Summary: AX: VoiceOver does not announce the level/depth of leaf nodes
Status: RESOLVED MOVED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: Safari 14
Hardware: Mac macOS 10.15
: P2 Normal
Assignee: Nobody
URL: https://codepen.io/toddlr/pen/XWrGrGV
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-10-28 15:48 PDT by Todd Kloots
Modified: 2023-04-11 17:24 PDT (History)
3 users (show)

See Also:

Attachments
Screen recording of using VoiceOver navigation to navigate the ARIA tree (2.68 MB, video/quicktime)
2020-10-28 15:48 PDT, Todd Kloots 		no flags Details
View All 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 Todd Kloots 2020-10-28 15:48:08 PDT 
Created attachment 412579 [details]
Screen recording of using VoiceOver navigation to navigate the ARIA tree

Steps to reproduce the problem:
1. Start VoiceOver
2. Go to https://codepen.io/toddlr/pen/XWrGrGV
3. Move focus to the ARIA tree instance via tab
4. Use the up and down arrow keys to move focus through the ARIA treeitems
5. Notice VoiceOver does not announce the level/depth of the leaf nodes

In contrast, the aria-level IS announced when navigating the ARIA tree using VoiceOver navigation
1. Start VoiceOver
2. Go to https://codepen.io/toddlr/pen/XWrGrGV
3. Press ctrl + option + right arrow
4. Press shift + ctrl + option + down arrow to enter the application
5. Press shift + ctrl + option + down arrow again to enter the "table" (how VoiceOver refers to the ARIA tree)
6. Press ctrl + option + right arrow to navigate through the ARIA treeitems
7. Notice VoiceOver announces the level of each treeitem
Comment 1 Radar WebKit Bug Importer 2020-10-28 15:48:20 PDT 
<rdar://problem/70783725>
Comment 2 Sommer Panage 2022-11-15 17:25:09 PST 
Still seeing this issue in 13.1 Beta (22C5044e)
Comment 3 Brent Fulgham 2023-04-11 17:24:53 PDT 
The cause of this issue is outside of WebKit, so resolving as MOVED.

The relevant team is working on the issue under <rdar://problem/70783725>.