Bug 246987

Summary: AX: Dynamically added element is not traversable
Product: WebKit Reporter: Jerry Lung <jerry.lung>
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: andresg_22, tyler_w, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 16   
Hardware: Mac (Intel)   
OS: All   
See Also: https://bugs.webkit.org/show_bug.cgi?id=211284
https://bugs.webkit.org/show_bug.cgi?id=241851

Jerry Lung
Reported 2022-10-24 20:45:03 PDT
Hey team, seeing an issue with Voiceover on Safari, where if an element is attached to the DOM after the initial render (e.g. conditional rendering via React), it is not traversable with VO Nav nor by the Rotor. I believe it's in the same vein as these other issues, though not exactly: https://bugs.webkit.org/show_bug.cgi?id=211284 https://bugs.webkit.org/show_bug.cgi?id=241851 In general it seems like elements are not being added to the traversal/rotor in a lot of instances. In mine, I find that if I unattach that element, and then reattach it, it now works fine in the traversal. Almost seems like its getting cached. Thanks for taking a look.
Attachments
Radar WebKit Bug Importer
Comment 1 2022-10-24 20:45:17 PDT
Andres Gonzalez
Comment 2 2022-10-25 08:10:10 PDT
Jerry: Thanks for the report. Would you please attach a reduced test case of this problem?
Tyler Wilcock
Comment 3 2022-10-25 09:52:59 PDT
Also, what version of macOS are you experiencing this on?
Jerry Lung
Comment 4 2022-11-03 09:50:37 PDT
It was MacOS Monterey 12.6 -- however; when I went to make a codepen the next day, I could not reproduce the issue, as well as on my actual project. Our QA just verified today. Not sure what happened, but we can close this. Thanks
Note You need to log in before you can comment on or make changes to this bug.