Repository navigation
Accessibility focus positions not updated after keyboard dismiss when dialog is shown immediately #186178
Copy link
Copy link
Closed
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work lista: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)Accessibility, e.g. VoiceOver or TalkBack. (aka a11y)platform-androidAndroid applications specificallyAndroid applications specificallyplatform-iosiOS applications specificallyiOS applications specificallyteam-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)Owned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)triaged-accessibilityTriaged by Framework Accessibility teamTriaged by Framework Accessibility team
Description
Activity
- addedin triagePresently being triaged by the triage teamPresently being triaged by the triage team
on May 7, 2026 @luomo-pro Thanks for the report. Labelling for
team-accessibilityto investigate further.- addedplatform-androidAndroid applications specificallyAndroid applications specificallyplatform-iosiOS applications specificallyiOS applications specificallya: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)Accessibility, e.g. VoiceOver or TalkBack. (aka a11y)team-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)Owned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)and removedin triagePresently being triaged by the triage teamPresently being triaged by the triage team
on May 7, 2026 - addedP2Important issues not at the top of the work listImportant issues not at the top of the work listtriaged-accessibilityTriaged by Framework Accessibility teamTriaged by Framework Accessibility team
on May 13, 2026 Hi @luomo-pro, thanks for the code sample.
Reproduced on iOS 26.6.1 and Flutter 3.47- added a commit that references this issue
on Sep 4, 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.- locked as resolved and limited conversation to collaborators
on Sep 18, 2026
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work lista: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)Accessibility, e.g. VoiceOver or TalkBack. (aka a11y)platform-androidAndroid applications specificallyAndroid applications specificallyplatform-iosiOS applications specificallyiOS applications specificallyteam-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)Owned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)triaged-accessibilityTriaged by Framework Accessibility teamTriaged by Framework Accessibility team
Steps to reproduce
Expected results
Accessibility focus should be on the TextField at the bottom of the screen, matching its visual position.
Actual results
Accessibility focus for the TextField remains at its old position (middle of screen, where it was pushed up when the keyboard was open). Touching the bottom of the screen where the TextField is visually located produces no accessibility focus.
This affects both Android TalkBack and iOS VoiceOver.
Additionally, in more complex real-world scenarios (e.g. a chat page with a message list and a bottom input field), this issue can escalate further: the TextField may become completely unreachable ? neither touch exploration nor swipe navigation can focus it. We have not found 100% reliable steps to reproduce this more severe case, but we suspect it shares the same root cause. This makes the impact of this bug more serious than the basic reproduction suggests.
Minimal reproduction code
Flutter version
Affected platforms