Hi again @capitainecaverne,
I’ve done some digging and some further testing. I couldn’t find mention of a specific iOS 13 bug anywhere. I’ve tested the tutorial app on my phone and it seems to be working.
VoiceOver tries to be as efficient as possible by changing it’s behaviour to suit your current settings and not repeat announcements if unnecessary, but the way the app main screen is implemented also has an effect.
Here are some patterns I noticed through testing:
If I enable VoiceOver before starting the app, and have the rotor position set to “Headings”, when the app launches it focuses on the first amp name, and adds “Actions Available” after the amp name is read.
But, If I enable VoiceOver before starting the app, and have the rotor position set to “Actions”, it adds “Swipe up or down to select a custom action, then double tap to activate” after the amp name is read. Which is the announcement you hear in the video in the tutorial.
The relationship between the rotor setting and the actions announcement behaves the same if I turn on VoiceOver while the app is running, but the first element focuses is the navigation controller title and I have to swipe right to focus on the amp name label to hear the announcement.
This behaves differently if I run the app from Xcode on my device, or simulator, in which case it seemed random; sometimes it would say it, sometimes not.
Due to the way this screen is implemented, the “Actions available” announcement is only heard on the first launch, I think this is due to the fact that the actions are attached to this view controller, and the view controller doesn’t change. Only the content of the screen is updated.
If you install the app on your device, then launch it fresh (without Xcode) do you see a similar pattern?