@tarangpatel has it been published on your end? There has been an OS version update and it looks like your app has also been updated since your post but based on your link and looking at your app on the App Store today (August 190 I still don't see it in the App Store. I am curious about this as well, as my team originally thought it wouldn't be launched by Apple until "fall 2025" based on news and the Overview page. It would be helpful to others as well to know where you got the info that it depends on the release version. I may have missed it but it looks like that is not in the Overview page.

Thank you. Is there any expectation from Apple that developers / app owners audit or regularly review their own claims of accessibility over time as features and enhancements occur? Another way to ask this, is the Nutrition Label going to have some sort of date of last release that can be tracked? Accessibility is not a one and done thing when an app itself has regular releases; if an app never updates the label wouldn't need to, but if a label is created in 2025 and then never updated despite regular app updates that will lead to a gap in the next year and on. It is because we have a robust team and because we employ users with disabilities, that my team has regular discussions on the ongoing effort of maintaining a certain standard, something not all apps on the App Store have.

How about tabList?

related question… is ”Move to Next Frame” for the HTML or to accessibilityFrame instance property?

Which OS are you referring to? VO accessibility settings are available to re-assign (or assign for the first time) a number of commands that a user may want that are not assigned by default.

Thanks; that partly answers my question. Please address the main issue: Is there a list somewhere or a HIG guideline for which transition types should have a sound? I would also appreciate any direction on what code strings are associated with these sounds and how custom components can capture these sounds or haptics or hints where it is expected? I understand the sounds are controlled by the system. You gave one example of an earcon "hen a screen changed notification gets sent to VoiceOver" which I already identified in my OP. I am asking for confirmation of all the places where earcons are associated with a VO swipe. Please respond.

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.

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.

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

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.

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

@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.

@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.

@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.