Critical VoiceOver Bug in iOS 26.1: Swiping Fails to Find Elements (e.g., "Cancel" buttons)

By mahmood, 26 September, 2025

Forum
Apple Beta Releases

Hello everyone,

I'm posting here because I've run into a serious and frustrating bug in iOS 26.1 that is severely impacting standard VoiceOver navigation (swiping).

The problem is that VoiceOver's standard left/right swipe gesture often fails to focus on or announce all elements on the screen. However, if I drag my finger across the screen, the missing element is found and announced, proving it's present and accessible—it's just being skipped by the swipe gesture.

This issue forces me to constantly switch from reliable swiping to the much slower and less precise finger-dragging method.

Reproduction Steps

I can reliably reproduce this bug using any action that brings up a confirmation alert or action sheet, or certain action menus:

  • Phone Call Alert (Reliable Test): After tapping a "Call Us" link on a **website or app** (which triggers the system's confirmation alert with options like "Call [Number]" and "Cancel"), **swiping gets stuck** on the call button. The "Cancel" button is unreachable via swiping and can only be found by manually dragging your finger.
  • WhatsApp Action Menu (Widespread Example): After selecting a message, the "Share" option is often **skipped entirely by the swipe gesture** (it is usually at the bottom right). Again, the only way to activate "Share" is by dragging your finger to that location.

This clearly shows that the bug is a core VoiceOver focus management issue across different types of applications and menus.

Call to the Community

I've already submitted this to Apple via their Feedback Assistant, but the issue is still present in 26.1. Even more concerning, I've checked the AppleVis Community Bug Tracker and this specific swiping bug is not currently listed.

Has anyone else encountered this same issue in iOS 26 or 26.1?

  • Can you reproduce the "stuck on Call button" or "missing Share button" behavior?
  • Have you found any quick workarounds?
  • If you have submitted feedback to Apple, please share your experience!

If you can confirm this bug, please also consider submitting your own feedback to Apple to increase its priority.

Options

Share Your Bug Reports with AppleVis

If you experience a bug in Apple Beta Software, the most important thing you can do is to file a report in Feedback Assistant. Please do not assume that Apple is already aware of a bug or that your report won't make a difference; your report may provide crucial information, and submitting bug reports directly to Apple helps them reproduce and resolve the issue faster. The more reports they receive, the higher the priority Apple is likely to give to fixing the bug.

If you are using beta software, please use the Feedback Assistant on your device to submit feedback and bug reports. If you are using a public release, this blog post explains how to report the issue and what information to include.

In 2025, AppleVis launched the Community Bug Reporting Program with the goal of improving the quality and quantity of information we share with the community about bugs in Apple software releases. If you would like to contribute to this effort, please submit your reports via our Community Bug Report Form.

All reports shared with AppleVis must first be filed with Apple via Feedback Assistant. More information about the Community Bug Program is available here.

Comments

By Ash Rein on Friday, September 26, 2025 - 17:00

I’ve reported it. I would say there’s no work around (as far as I know). I encourage you to to also report it. Accessibility@apple.com

Been around prior to iOS 26 final release. Needs more people reporting it

By mahmood on Friday, September 26, 2025 - 17:09

Hello, yes, as I mentioned in the topic, I emailed Apple and also submitted feedback through the iOS 26 beta program, but unfortunately, it hasn't been resolved! Everyone needs to report the issue.

By TheBlindGuy07 on Saturday, September 27, 2025 - 01:06

Often in the notification centre vo loops on the same element swiping left/right, I have to use explore by touch and after a couple elements it seems to un stuck itself.

By Ash Rein on Sunday, September 28, 2025 - 00:49

Somewhat surprised that people aren’t seeing this issue.

By Manuel on Sunday, September 28, 2025 - 08:21

Does this only occur on iPhone? On iPad, which is my beta device, I‘ve not run into this issue yet.

By Ash Rein on Sunday, September 28, 2025 - 09:51

I don’t know if it only happens on iPhone. Probably

1. open up Safari and do a search for a phone number like McDonald’s customer service or Best Buy customer service or Amazon customer service phone number. Anything really

2. When you find the surgery result that has the phone number, double tap, and you’ll get a pop-up menu call the phone number.

3. When pop-up menu shows up, right or left for the phone number and the cancel button. You can’t move from this point because the navigation is locked up.

By mahmood on Sunday, September 28, 2025 - 10:55

You can go to beta.apple.com to reproduce the issue. When you try to sign in, only 'Sign In' is present, and there is no 'Cancel' option! You cannot find 'Cancel' by swiping.

By Holger Fiallo on Sunday, September 28, 2025 - 11:48

I am curious if the LG is affecting VO. Did people turn it off?

By Holger Fiallo on Monday, September 29, 2025 - 01:26

Yes, it is. Setting, accessibility, display and text off.