Skip to content

Slider and RangeSlider thumb accessibility issues #114225

Description

@TahaTesser

Description

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.

  1. Focus window takes half the size regardless of the thumb location
  2. 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.
  3. Focus windows should be on the range thumbs
Flutter Android

Activity

  1. added
    in triagePresently being triaged by the triage team
    frameworkflutter/packages/flutter repository. See also f: labels.
    p: material_uimaterial_ui package in flutter/packages
    and removed
    in triagePresently being triaged by the triage team
    on Oct 28, 2022
  2. TahaTesser commented on Oct 28, 2022

    @TahaTesser
    ContributorAuthor

    Related #53958

  3. self-assigned this
    on Oct 28, 2022
  4. moved this to To do in Nevercodeon Oct 28, 2022
  5. TahaTesser commented on Oct 28, 2022

    @TahaTesser
    ContributorAuthor
  6. added
    f: focusFocus traversal, gaining or losing focus
    on Oct 31, 2022
  7. Piinks commented on Oct 31, 2022

    @Piinks
    Contributor

    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!

  8. added
    P2Important issues not at the top of the work list
    on Oct 31, 2022
  9. chunhtai commented on Oct 31, 2022

    @chunhtai
    Contributor

    Since there is a native android equivalence in this case, we should follow OEM behavior.

  10. 18 remaining items

  11. moved this from PR submitted to No status in Nevercodeon Feb 12, 2024
  12. self-assigned this
    on Mar 24, 2026
  13. hannah-hyj commented on Mar 24, 2026

    @hannah-hyj
    Member

    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

  14. github-actions commented on Apr 13, 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.

  15. locked as resolved and limited conversation to collaborators on Apr 13, 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)f: focusFocus traversal, gaining or losing focusframeworkflutter/packages/flutter repository. See also f: labels.p: material_uimaterial_ui package in flutter/packagesteam-designOwned by Design Languages teamtriaged-designTriaged by Design Languages team

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions