Repository navigation
Description
In Flutter master version 3.30.0-1.0.pre.428, I've identified a regression in iOS accessibility behavior. When using a ListView, there is now an extra, silent accessibility focus that appears before the first item in the list. This empty focus point doesn't announce anything when navigated to with VoiceOver, creating a confusing experience for blind users.
This issue was not present in versions from approximately 6 months ago. It appears to be a regression introduced in recent builds.
Steps to Reproduce
- Run the minimal example code below on an iOS device
- Enable VoiceOver on the device
- Navigate to the list
- Observe that when swiping right to move through list items, there's a silent focus before the first item
Expected results
VoiceOver should focus directly on the first item in the ListView when navigating to it.
Actual results
When using VoiceOver, an empty, silent accessibility focus appears before the first ListView item. This focus point doesn't announce anything, and users must swipe again to reach the actual first item.
Code sample
Code sample
import 'package:flutter/material.dart';
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({Key? key}) : super(key: key);
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'VoiceOver Issue Demo',
home: const AccessibilityIssueDemo(),
);
}
}
class AccessibilityIssueDemo extends StatelessWidget {
const AccessibilityIssueDemo({Key? key}) : super(key: key);
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: const Text('VoiceOver Issue Demo'),
),
body: ListView.builder(
itemCount: 20,
itemBuilder: (context, index) {
return ListTile(
title: Text('Item ${index + 1}'),
);
},
),
);
}
}Screenshots or Video
No response
Logs
No response
Flutter Doctor output
Doctor output
[✓] Flutter (Channel master, 3.30.0-1.0.pre.428, on macOS 14.4.1 23E224Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
darshankawar commentedon Mar 4, 2025
Thanks for the report @luomo-pro
I tried on latest master and stable versions running on iOS 15 device but was unable to replicate the reported behavior. The focus moves to item 1 from the app title properly. If you could provide us a short video will be helpful further along with device on which you are seeing this behavior.
luomo-pro commentedon Mar 4, 2025
demo_video.mp4
My Environment
darshankawar commentedon Mar 5, 2025
Thanks for the video. I was able to replicate this on latest master and stable versions.
34 remaining items
Archydude commentedon Nov 24, 2025
I managed to get around it by wrapping the listview (or scrollview) with Semantics and setting blockUserActions: true.
I'm not sure what are the consequences of this change but it does resolve the extra silent focus.
Tested on flutter version 3.35.3
zywek123 commentedon Nov 27, 2025
@Snirdude You just took away the ability to scroll through the list with three fingers for VoiceOver users.
amugofjava commentedon Dec 7, 2025
Thanks for trying to find a workaround @Snirdude
I am surprised this issue is still pending. It's not an obscure bug that has little impact; this must effect pretty much every Flutter app out there. I am still holding on to Flutter 3.27.4 on iOS to avoid this bug, but at the same time I have had to move to current stable on Android for the 16KB page size support. It's getting trickier to maintain these two versions.
smd-shafi commentedon Dec 8, 2025
I can reproduce this on Flutter 3.35.5 on iOS Emulator Iphone 16. Minimal app attached (same as OP).
I inspected the semantics tree using showSemanticsDebugger: true and Xcode Accessibility Inspector — there is an extra semantics node before Item 1 that has no label and is focusable.
Workarounds tested:
ListView.builder(..., semanticChildCount: 20) — did not fix the issue
addSemanticIndexes: false + manual IndexedSemantics(index: index, child: ...) — did not fix the issue.
gmoraja commentedon Feb 9, 2026
Is it possible to escalate this important accessibility issue? We have developed multiple apps for the US Department of Veterans Affairs using Flutter, and this regression is having a major impact on our users.
parultrantor commentedon Feb 20, 2026
Hi team,
We’re also encountering this in our production app on iOS and can confirm it’s still reproducible on the current stable Flutter version. This is affecting screen reader navigation on scrollable screens for us.
Could you please share the current status of this issue and whether there is a planned fix or workaround at the framework level?
Thanks in advance 🙏
jimgerth commentedon Feb 26, 2026
I can reproduce this in Flutter
3.41.2on an actual iOS device.It seems like #99011 is indeed the same issue and has persisted since 2022, for 4 years now!?
EDIT:
Reproduced with Flutter3.7.0, can't test with older releases right now, as older Flutter versions result in build errors with my current Xcode.So, seems like this has really been a bug for a while...
EDIT 2: Apparently there is indeed a difference between the "Accessibility Inspector" used to test with the Simulator (which annoyingly doesn't have VoiceOver) and the VoiceOver on physical iOS devices. The inspector always sees a semantic node for the entire scrollable (at least back to
3.7.0as the above test was done with the inspector), while actual VoiceOver is able to ignore this unlabelled node in some versions (for me last known good version is3.7.12) but does not ignore it in others (in current3.41.2at at least back to3.32.2).VoiceOver not being supported on the Simulator and the accessibility inspector being different to VoiceOver unfortunately makes this very annoying to test.
I could not get a test app to run on a physical iOS device below flutter
3.32.2as I get errors in some assembly code I don't understand when trying to run.Because of this unfortunately I cannot bisect to find the concrete change that introduced this issue.
Others suggested
3.27.4to work still, unfortunately I couldn't check that.@chunhtai could we get someone from the team to look at this again? It's been quite a while now and there have been quite a few replies now that highlight this as a not-unimportant issue, which I would like to add to.
EDIT 3: This can be worked around by building an app with a custom flutter engine (see https://github.com/flutter/flutter/blob/master/docs/engine/contributing/Compiling-the-engine.md) by hard-coding
- (BOOL)isAccessibilityElement { + return NO; - if (![self.semanticsObject isAccessibilityBridgeAlive]) { - return NO; - } - - if (self.semanticsObject.isAccessibilityElement) { - return YES; - } - if (self.contentSize.width > self.frame.size.width || - self.contentSize.height > self.frame.size.height) { - // In SwitchControl or VoiceControl, the isAccessibilityElement must return YES - // in order to use scroll actions. - return ![self.semanticsObject bridge]->isVoiceOverRunning(); - } else { - return NO; - } }in
flutter/engine/src/flutter/shell/platform/darwin/ios/framework/Source/FlutterSemanticsScrollView.mm.Fix invisible accessibility element before scroll view (#184155)
Fix invisible accessibility element before scroll view (flutter#184155)
github-actions commentedon Apr 20, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.Scrollable.excludeFromSemanticsonSingleChildScrollView#187376 as a duplicate of this issueFix invisible accessibility element before scroll view (#184155)