Are you a VoiceOver user stuck inside a Facebook post, unable to find the back button? You are not alone. A recent update to the Facebook app on iOS has caused the “Back” button to become invisible or inaccessible to VoiceOver focus, leaving many users “trapped” after opening a post or photo.
If you are stuck, do not close the app. You can fix this instantly using two simple VoiceOver gestures.
The Solution: How to Go Back
Since the on-screen Back button is currently failing to respond to VoiceOver, use these built-in system gestures to navigate backward.
Method 1: The Two-Finger Scrub (Recommended)
This is the fastest and most reliable way to go back in any iOS app, including Facebook.
- Place two fingers on the screen.[
- Quickly move your fingers back and forth three times in a “Z” motion (imagine you are scrubbing a small spot on the screen).
- You will hear an earcon (a sound) indicating that you have successfully navigated back to the previous screen.
join us on telegram for more useful updates
Method 2: The Slide-to-Back Gesture
If the scrub gesture feels difficult, you can try this alternative:
- Tap and hold your finger on the screen until you hear a tone.
- Without lifting your finger, slide it toward the right side of the screen.
- This gesture often triggers the “Back” action in apps that are not properly exposing the back button to VoiceOver.
Support us:
Why is this happening?
This is a software bug within the Facebook app’s latest update. The back button still exists visually, but the app has failed to “expose” it to the iOS Accessibility layer.
Pro-Tip: If you absolutely must find the button, some users have reported success by turning on Screen Recognition in the VoiceOver Rotor settings. Swipe with the rotor until you hear “Screen Recognition,” turn it on, and then swipe through the screen—the back button may suddenly reappear. Turn it off afterward, as Screen Recognition can make the rest of the app laggy.
A good news for you: Meta released version 555.0.0 of Facebook application for iOS, apparently the problem has been fixed.
The third way would be to temporarily use the VO screen recognition, you should then identify the back button…