You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Slider and RangeSlider thumb accessibility issues #114225
1. The entire Slider is focused instead of just the thumb.
The focus window should only follow the thumb while keeping the ability to tap anywhere on the slider to change value.
(this especially becomes problematic with RangeSlider)
Flutter
Android
2. RangeSider focus window is divided in half despite range thumb locations instead of just the range thumbs.
Focus window takes half the size regardless of the thumb location
If both range thumbs are located on one side of the slider, the focus window is still shown on the otherwise side, in an empty slider area.
I will try to reland #121598 again, i think the test failures was because of semantics tree structure changes, thumb become the leaf node and overlay node has their own nodes, i will investigate the google 3 failures
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.
Activity
TahaTesser commentedon Oct 28, 2022
Related #53958
TahaTesser commentedon Oct 28, 2022
cc: @Piinks
Piinks commentedon Oct 31, 2022
M3 has not given us an a11y spec yet (https://m3.material.io/components/sliders/accessibility), so I would follow the spec that preceded it from M2 https://m2.material.io/components/sliders, which is also lacking specific a11y behavior, but it looks like you have this well defined based on the Android behavior.
cc @chunhtai & @gspencergoog if there are any other a11y or focus issues.
Thanks for identifying this!
chunhtai commentedon Oct 31, 2022
Since there is a native android equivalence in this case, we should follow OEM behavior.
18 remaining items
hannah-hyj commentedon Mar 24, 2026
I will try to reland #121598 again, i think the test failures was because of semantics tree structure changes, thumb become the leaf node and overlay node has their own nodes, i will investigate the google 3 failures
Reland "Fix Slider semantics node size" with some changes (#184168)
github-actions commentedon Apr 13, 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.Reland "Fix Slider semantics node size" with some changes (flutter#18…
Reland "Fix Slider semantics node size" with some changes (#184168)
Reland "Fix Slider semantics node size" with some changes (#184168)