Description
When using flutter_intro, the guided intro steps shown through Intro + IntroStepBuilder are not read by accessibility services (Android TalkBack / iOS VoiceOver).
Screen readers do not focus on or announce the step content, and underlying widgets remain accessible even while the intro overlay is active.
Expected Behavior
- The intro overlay content (text or overlayBuilder) should be included in the accessibility tree
- Screen readers should automatically announce the step content when it appears
- Focus should move to the guided step instead of remaining on widgets behind the overlay
- Users should be able to navigate the intro using screen reader actions (Next / Continue / Skip)
Actual Behavior
- TalkBack/VoiceOver ignore the intro overlay entirely
- Focus remains on UI behind the highlight
- No spoken announcement when a new step is shown
- Users depending on accessibility services cannot follow the intro
Platforms Tested
| Platform |
Result |
| Android (TalkBack) |
❌ Not accessible |
| iOS (VoiceOver) |
❌ Not accessible |
Description
When using
flutter_intro, the guided intro steps shown throughIntro+IntroStepBuilderare not read by accessibility services (Android TalkBack / iOS VoiceOver).Screen readers do not focus on or announce the step content, and underlying widgets remain accessible even while the intro overlay is active.
Expected Behavior
Actual Behavior
Platforms Tested