-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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: Allow VoiceOver to navigate "back into" web contents #24655
fix: Allow VoiceOver to navigate "back into" web contents #24655
Conversation
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.
@felixrieseberg do you by chance have a reference for this or are we just sort of trusting manual testing and what Apple says? i'm ok with this but have mild concern it might change again in the future and would love to know where we can look for this kind of information 🤔
@codebytere God, I wish I had a good answer for you - that would have made this a lot easier. This PR is the result of some manual testing by Slack's a11y people and an email thread with Apple where some helpful AX experts told me to please fix the parent-child relationship. Actually, as I'm writing this out, we'd probably be better off removing the thing we don't want in the array instead of manually keeping things. Let me amend the PR, because that'd solve our problem here - if things change again in the future, we wouldn't have to change anything in this code. |
Release Notes Persisted
|
I have automatically backported this PR to "10-x-y", please check out #24698 |
I have automatically backported this PR to "9-x-y", please check out #24699 |
Description of Change
After some consultation with our friends at Apple, I've figured out why exactly VoiceOver has such trouble getting "back into" web contents when it was first navigated out. As it turns out, by default, there is no
RenderWidgetHostViewCocoa
in the AXChildren array, so our custom filter ensuring that it's included doesn't do anything. Instead, the web contents are part of a class namedBrowserAccessibilityCocoa
.[Note: I've previously tried to fix this by manually adding the
contentView
, which worked in some cases, but not all]Checklist
npm test
passesRelease Notes
Notes: Fixes an issue where VoiceOver was unable to navigate from the top-level window back into the web contents