Visitar URL original
USWDS - Bug: Introduce visual instruction for range slider · Issue #6614 · uswds/uswds · GitHub
Skip to content

USWDS - Bug: Introduce visual instruction for range slider #6614

Description

@chandracarney

Describe the bug

The range slider component should have instructions to ensure visual users know how to operate the slider.

In partnership with VA teams (including @coforma-jamie, @artsymartha68), we are re-describing minor issues with range slider under this issue and closing out a prior issue, in order to avoid confusion. This issue closes and replaces #6443 and is related to #6116.

Steps to reproduce the bug

  1. Go to https://designsystem.digital.gov/components/range-slider/
  2. Note there's no visual instruction indicating how to operate the component

Expected Behavior

The range slider component and example on the USWDS website should both have visual instruction indicated through a hint in the component example:

  1. The instruction should read: “Move the slider to change the value”
  2. The color of this text can be presented in the dark grey class="usa-hint", which is used in both character count and date range picker components.

Related code

No response

Screenshots

No response

System setup

No response

Additional context

Full instruction on how to operate a range slider is available to screen reader users through a screen reader's inherent behavior navigating semantic HTML. Using both VoiceOver and JAWS screen readers, we verified they each describe how to use the range slider as-is, when no hints or ARIA are added on. Because instruction slightly differs across screen readers, we want to ensure we aren't overly prescriptive in applying screen reader-only hints (excess ARIA was removed in #5413).

Code of Conduct

Activity

  1. added
    Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.
    Package: Range SliderWork affecting Range Slider. Apply only when this area helps route or find the issue.
    Needs: ConfirmationReported behavior needs validation. Remove after recording reproduction or investigation results.
    A11y AuditAccessibility audit work or its findings. Preserve the test scope and evidence in the issue.
    A11Y Audit FindingsA finding from an accessibility audit. Keep links to the test, result, and affected user experience.
    Good first issueA bounded task suitable for a first contributor, with clear acceptance criteria and setup guidance.
    Help wantedCommunity contributions are welcome; scope and acceptance criteria should be clear before applying.
    on Apr 20, 2026
  2. ravitejapioneerblaze-code commented on May 22, 2026

    @ravitejapioneerblaze-code
    Contributor

    Hi team, I'd like to work on this issue. I plan to add the usa-hint span with the visual instruction text and include an automated accessibility test to verify the fix. Will submit a PR shortly.

  3. added and removed
    Needs: ConfirmationReported behavior needs validation. Remove after recording reproduction or investigation results.
    Help wantedCommunity contributions are welcome; scope and acceptance criteria should be clear before applying.
    on May 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

A11Y Audit FindingsA finding from an accessibility audit. Keep links to the test, result, and affected user experience.A11y AuditAccessibility audit work or its findings. Preserve the test scope and evidence in the issue.Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.Good first issueA bounded task suitable for a first contributor, with clear acceptance criteria and setup guidance.Package: Range SliderWork affecting Range Slider. Apply only when this area helps route or find the issue.Status: AcceptedLegacy workflow marker.

Type

No type

Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions