It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

This looks like an ok change to make, I did some digging and found #32528 added this, but those tests were changed soon after for #42404
The point you make in #121098 is valid, it does not seem congruent with how accessible navigation is used elsewhere in the framework, and it may in fact have been a workaround for the issue fixed by flutter/engine#35478

We can certainly run it through additional testing to be sure though. :)

@Piinks Thanks for the feedback! Should I remove the [WIP] in title to make it possible to run this PR on additional testing?

No need, it was pretty easy for me to just go run this one since the actual change is simple. I will report back with results!

All of the tests passed. This is safe to proceed! :)