-
Notifications
You must be signed in to change notification settings - Fork 15.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Add ContentsView to AXChildren #22399
Conversation
e42de1b
to
17aeafa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks fine to me, cc @zcbenz for second opinion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Release Notes Persisted
|
I have automatically backported this PR to "9-x-y", please check out #22469 |
I have automatically backported this PR to "8-x-y", please check out #22470 |
/trop run backport-to 7-2-x |
The backport process for this PR has been manually initiated - |
I have automatically backported this PR to "7-2-x", please check out #23174 |
Description of Change
The native window on macOS has only three elements in its
AXChildren
: The close, maximize, and minimize button. In practice, that means that a VoiceOver user won't be able to navigate from the window into the web contents, therefore unable to interact with anything that's actually happening in the window.In this PR, I'm manually editing the
AXChildren
array and adding theContentsView
back in. I have to admit that I have little experience with accessibility work in Cocoa, but I believe that it fixes the issue. I also have no idea how we could write a test for this, but I'm open to ideas!Closes #17207
Before
After
Checklist
npm test
passesRelease Notes
Notes: macOS VoiceOver is now able to find its way back into web contents after it navigated "out" of an application.