Open TKDickson opened 2 months ago
As described in #9474, the relevant keyboard navigation issue was fixed by Apple in iOS 18 as of 9/16/24. Once enough of our users have upgraded to iOS 18, we can implement the changes described in this ticket.
I've created a branch called revert-keyboard-nav-workarounds
that mostly reverts the changes as desired. However the bottom navigation bar and menu list item changes should not be reverted, so a couple tweaks to the branch will be required.
Removing #9463 as a blocker since Apple fixed the issue.
This is global work & will build off of Chris's existing investigation, but we'll be the ones doing it; removing his assignment & the health label - FYI @ala-yna
@cadibemma VoiceOver is not saying the role for any of the changes you made on iOS. So for example:
@rbontrager CC: @cadibemma ,
Rachael, do you know/can you test if this was working on a previous ios and is now broken in 18? Do you have some older ones we could load Chika's branch on?
Thanks, let us know.
Proposed Change
In response to #9288 (in order to stop the worst impacts), we changed the role for several components to either 'button' or 'link'. Some of them can stay that way (bottom navigation bar, menu list items) but all of the remaining changes should eventually be changed back to a role that 1) is correct and 2) continues to work with all assistive tech.
This could be in response to a fix from iOS or React Native, or could be if we find a working medium-term solution with #9463.
Why Should We Prioritize?
Coding Time Estimation
Testing Considerations
Checklist