Display Range Value Dynamically as Slider Changes #41196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses the concerns mentioned in: #41181
it improves the Range component documentation by demonstrating how developers can make their range sliders more accessible and user-friendly. A new example has been added, displaying the range value as text next to the “Example range” header.
This feature is already implemented in the Boosted Orange docs (Boosted Orange Range Usability).
Motivation & Context
This change enhances accessibility by helping developers present range values more clearly, improving usability for users who rely on visual or assistive cues.
Type of changes
Checklist
npm run lint
)Live previews
Related issues
Closes: #41181