Using the ‘Drag’ option from the VoiceOver Rotor to rearrange widgets can be inconsistent and unreliable, as there are times when VoiceOver does not give accurate feedback on where the dragged widget will be place or offer the option to place the widget.
This behaviour appears to be most prevalent on the Today View and when there are too many active widgets to be present at the same time on this screen (so, when not editing, you would need to scroll the view to access all of the widgets).
The app library screen is divided into sections such as Productivity, Utilities etc. You can no longer quickly move between these sections using the VoiceOver containers navigation.
In Safari, using the Back button or Scrub gesture to return to the previous page will result in VoiceOver becoming near unusable. VoiceOver will read an item if you locate it by touch, but flicking will not move focus.
You should find that some UI elements have the extraneous text “today” prepended to their VoiceOver label - for example, when VoiceOver focus lands on the Edit button it will say “Today Edit button”.
This issue can occur on widgets both on the Today screen and on home screens.
VoiceOver's actions menu should be present to allow the user to enter edit mode, and when it is a stacked widget, to cycle to the next or previous widget in the stack.
On some occasions, after placing VoiceOver focus on a widget, this menu is failing to appear.
In the list of languages of the iOS 14 Translate application, Voiceover announces new line before the language variant if a language offers multiple variant.
For example, Spanish Spain will be spoken as "Spanish. New line. Spain."
When you adjusts the volume slider in Control Center using the flick gesture, VoiceOver announces the previous volume level rather than the new level after the adjustment. Specifically, when a user focuses on the volume slider in Control Center with VoiceOver enabled, then performs a 1 finger flick up or down to change the volume, VoiceOver speaks the volume percentage. However, instead of announcing the new volume level, VoiceOver reads out the volume level prior to the flick gesture adjustment.
The short explanation of this problem is that the screen becomes unresponsive to VoiceOver when you attempt to add a new favourite in the Phone app and go to your list of contact groups as part of that process.
So, to check for this you will need to have 1 or more groups setup within your contacts.
Now …
1. Open the Phone app and go to the Favourites tab.
2. Double-tap on the ‘Add’ button.
If using the Voiceover practice feature available in Voiceover settings, the braille tab does not give the correct information about the gestures available in the braille screen input mode.
On occasion, VoiceOver can become unresponsive when attempting to use the two-finger double-tap ("Magic Tap") gesture to answer an incoming phone call.
VoiceOver crashes when attempting to navigate the Sounds settings, particularly when attempting to change a ringtone.
VoiceOver does not announce the current selection status of the Love and Dislike buttons on the More menu located on the Mini Player of the native Music app
VoiceOver does not announce the selection status when adding people or apps to the allowed notifications list of a Focus mode.
I would expect VoiceOver focus to move to the data which is presented here graphically, and then speak the data as you move focus through it.
If you are playing audio through an external device, the "Playback Destination" button on the Mini Player screen of the native Music app no longer includes the name of the destination device (although this information is visually present on screen, it is not spoken by VoiceOver).
When navigating a canvas in Freeform, VoiceOver announces the types of items in focus, like file or website, but does not speak their names. In order to identify the item in focus, you must double-tap to open it.
You should find that the text on the clipboard has been pasted in to the message field.
As you move VoiceOver focus, VoiceOver should provide feedback on which items are selected. It does not.
If you double-tap on an item, VoiceOver should provide feedback on the new selection status of this item. It does not.
If you activate the listen button in the Translate application, and instead of speaking flick around the screen, you will notice a text field which is dimmed (logical since you are dictating the text), a close button to dismiss the listen screen as well as an element Voiceover does not speak and it does not seem to do anything when activated.
When using the VoiceOver rotor to mark an email as read in the iOS Mail app, VoiceOver fails to provide clear confirmation feedback. Instead of announcing "read" to confirm the action, VoiceOver speaks an unclear and incomprehensible phrase. This results in a confusing experience for VoiceOver users who rely on the screen reader to understand the results of their actions.
We have not tested this behaviour against all VoiceOver voices, but it has been consistent across the voices that we have tested.