Skip to content

[a11y] RangeSlider keyboard focus does not follow mouse interaction #173575

Closed

Description

@yjbanov

Context

Reproduction

  1. In the Flutter repo, cd dev/a11y_assessments.
  2. flutter run
  3. Enable the additional use-cases using the switch in the top-right corner of the app.
  4. Open the RangeSlider use-case.
  5. Use the mouse or trackpad to move the left thumb.
  6. Let go of the mouse, and use the ARROW RIGHT/LEFT keys to operate the range slider again.

Expected behavior

The keyboard input focus should have moved to the thumb that was moved during step 5, and using the ARROW RIGHT/LEFT keys during step 6 should have moved that same thumb.

It should also be possible to switch focus between the left and the right thumb by clicking on the respective thumb. For example, if the left thumb currently has focus (use the TAB key to get it), the user should be able to click on the right thumb, and then operate it using the keyboard. This is currently not happening.

Actual behavior

The thumb that was used by the mouse last does not react to the keyboard.

Activity

  1. added
    frameworkflutter/packages/flutter repository. See also f: labels.
    a: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)
    team-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)
    on Aug 11, 2025
  2. added
    P2Important issues not at the top of the work list
    on Aug 13, 2025
  3. added
    ⏳Bot is counting down the days until it unassigns the issue
    on Feb 5, 2026
  4. flutter-triage-bot commented on Feb 5, 2026

    @flutter-triage-bot

    This issue is assigned to @hannah-hyj but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

  5. removed
    ⏳Bot is counting down the days until it unassigns the issue
    on Feb 10, 2026
  6. github-actions commented on Mar 3, 2026

    @github-actions

    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 -v and a minimal reproduction of the issue.

  7. locked as resolved and limited conversation to collaborators on Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work lista: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)customer: thoughts (g3)frameworkflutter/packages/flutter repository. See also f: labels.team-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)triaged-accessibilityTriaged by Framework Accessibility team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions