@Frameworks Engineer Has there been any update on whether this issue will be resolved in a future update or perhaps best practices you can share on how to best build for this issue? Our team built our entire app on the iOS 14 beta with a robust menu for the visually impaired. In the beta everything worked perfectly, however since the public release version we were frankly devastated when the latest version of the OS presented this massive interaction change. Could you please share any resources on how a developer can best create custom navigation menus with this new system? For example, our app has horizontal menus, we built an entire, voiceover based, menu system so visually impaired users can navigate the items in these menus in the correct order. With a standard vertical order menu system, one that is default in this new screen recognition feature, the order of the menu items are entirely incorrect, making the experience terrible for our visually impaired users. So much so that we’ve had to pull our app until this is figured out. Is our only option to completely redesign our app to have vertical navigation? Please….any help or any documentation for best practices would be extremely appreciated. Our visually impaired users simply cannot use our app with the persistent “Direct Touch Area” message…which is incredibly disappointing considering how awesome the voiceover framework is.

Anyone finding success in beta 3?

Ditto. Looking forward to when this API starts working. Hope this doesn’t go the way of AirPower haha...