With VoiceOver running and a Bluetooth keyboard or braille keyboard connected, go to settings>Safari, and under the Tabs heading, change this to Single Tab. Now, Nnvigate to Safari's address bar and attempt to type in it. You will find that with either input method, it does not work.
iOS/iPadOS
Post Date:
Though Live Captions work in other apps, they are not working with Face Time calls.
Post Date:
In Focus mode settings, any existing automation for a Focus mode is announced by VoiceOver as an unlabelled button. Specifically, if you have created triggers for a Focus mode to be automatically enabled — such as at specific time or location — where these are listed in the settings for the Focus Mode, each will be an unlabelled button.
Post Date:
In Settings, VoiceOver does not speak the information displayed about devices linked to your Apple ID.
Depending upon the type of device, this will include information such as the model number, the software version, and the serial number.
Post Date:
In some situations, it is not possible to move apps into folders on the Home Screen when using the VoiceOver Rotor's Drag-and-Drop functionality.
When selecting the Rotor option to add an app to a folder, our experience has been that the app is instead placed in the position before the folder.
Post Date:
In the Files app that is new in iOS 11, the VoiceOver Actions Menu for files and folders includes two separate instances of "Delete." In some instances, one of these will be "Delete Now"; on other occasions, both will be "Delete."
Post Date:
In the Home tab of the Games app, there is a Continue Playing section, where your active games are listed for easy restart.
The buttons representing each game are not labelled for VoiceOver.
Post Date:
If you have multiple translation results on the screen, focusing on one will announce the presence of custom actions.
Most of them work correctly, except the two Voiceover calls "Drag1" and "Drag2".
Activating one of them will freeze Voiceover for a few seconds, but in the end won't do anything and will just play the no item discovered sound if sounds are enabled.
Post Date:
In the iTunes Store app, using the VoiceOver rotor to navigate by heading is inconsistent and unreliable.
The typical behaviour appears to be that navigating by heading only works with headings that are visually present on screen at the time.
Consequently, VoiceOver may report that no further headings are available, when in fact there are.
Post Date:
On occasion, when viewing the list of mailboxes in the Mail app, the number on the unread badge read by VoiceOver is inaccurate.
Post Date:
In the Messages app you have the ability to pin conversations to the top of the list.
One way to do this with VoiceOver is to select the Pin option in the Actions menu.
However, when you do this, nothing happens. The method is not working.
Post Date:
In the native Contacts app, the first item visually displayed at the top of any list of contacts is your own contact card. This can consistently and reliably be located by touch; however, when swiping, it is only found when swiping left from below in the Contacts list. If you swipe right from the top of this screen, VoiceOver focus will completely miss that your contact card is present.
Post Date:
On most tabs in the native Music app, using the VoiceOver rotor to navigate by heading is unreliable.
The typical behaviour appears to be that navigating by heading only works with headings that are visually present on screen at the time.
Consequently, VoiceOver may report that no further headings are available, when in fact there are.
Post Date:
New to iOS 16 are app Shortcuts, which are simple, one-action shortcuts that are ready to use as soon as you install an app from the App Store that has been updated to include them.
These are listed in the Shortcuts app. Unfortunately, where the shortcuts available for any app are listed, they are spoken by VoiceOver as a series of unlabelled buttons.
Post Date:
When you attempt to open the context menu on an individual message in a chat thread in WhatsApp, the menu quickly closes before you have the chance to select any items.
This menu contains actions including reactions.
Post Date:
A regression in iOS 17 causes incoming banner notifications to interrupt VoiceOver speech when the “Speak Notifications” accessibility setting is enabled.
Specifically, any time a new notification banner appears, VoiceOver will immediately stop reading the current on-screen text or menu to announce the notification. This interrupts VoiceOver mid-sentence or mid-menu in a disruptive manner.
Post Date:
If you have notifications set to be grouped by day in the Notifications Center, there may be inconsistencies in the behavior of the ‘Clear Section’ and ‘Confirm Clear Section’ buttons when there are notifications for multiple days on this screen. These can prevent you from clearing notifications. Some of the Team have not been able to reproduce this, so it may be the result of a specific combination of settings or use case.
Post Date:
If you use 3D Touch to open the ‘Quick Actions’ menu on an icon in a Home screen folder, using the ‘scrub’ gesture to close that menu actually closes the folder. The ‘Quick Actions’ menu remains on screen and you have to use the scrub gesture again to close the menu.
Note that this only occurs if you activate the Quick Actions for an item and do not swipe around the screen to explore the Quick Actions. If you navigate to one of the available Quick Actions and perform the two-finger scrub, the gesture works as intended and you are placed back on the item’s icon inside the folder.
Post Date:
Using the VoiceOver Actions Rotor on a Contact icon on the Proactive Search screen will occasionally result in the information from another contact being used/shown.
Post Date:
During a phone call, showing or hiding the keypad works, but VoiceOver doesn't recognize that until you touch the screen. If you have the keypad visible and double-tap the button to hide it, then swipe left, you swipe through the keypad. If you instead touch the screen to explore it, VoiceOver reports what it should have all along--that the keypad is gone. The same happens in reverse when you show the keypad again.