@Apple Frameworks Engineer: It would be helpful to understand intended Table focus patterns for Apple like there are for HTML tables with keyboard focus vs screen reader focus in web.

@Apple from your answer it appears that "item" is every interactive element. You introduce a new term, the Full Keyboard Access cursor, and do not directly state what the cursor is. Please elaborate.

@glow the focus indicator is driven by the operating system and it also is adjustable in the Settings under full keyboard access. This makes it not applicable for the non-text- contrast WCAG SC.

See thread https://developer.apple.com/forums/thread/656821

Thanks, that helps for the main movements. … spinners? Modals? content groupings? what’s the expectation there? The surprise scenario that throws me is a wall of text… what about UITextView/ UIScrollView or whatever Apple News and similar layout? Enabling keyboard gestures with FKA is a decent backup to simulate touch scrolling; is a gesture the only intended way for FKA users to navigate a UIScrollView? I can’t seem to focus on inline links with tab, Ctrl+ tab or arrow keys in this type of View. Which is an accessibility issue. But maybe I’m missing some FKA Help Menu function.

Also I can confirm there is no custom actions or custom shortcut in the Apple News app for scrolling.

I found that for some scrollviews I have to move between Keyboard Gestures (Tab + G) enabled and disabled. Option (alt) + up/down arrows also has some ability to move. But what is expected, I cant' say.

Please point users to the Apple Developer pages that are needed to configure custom code to be focusable for keyboard users, but also how to address screen reader (VoiceOver) focus that is differently from keyboard focus.