Had to force the Typescript package to 4.2.2 to allow the package to compile on local
Changed the Single Range Input Max value into an Input [type=Number]. This allows a user to be able to input a value vs. having to use the slider. This change is meant to address screen reader users + those with finite motor controls in their hands.
Created a Multi Range Slider type, in addition to the existing single. This allows for 2 input selectors, with Input [type=Number[] for both the lower and upper values.
Supporting tweaks to the RangeSlider and Input tsx files to support the Multi Range Slider
Known Issues/Discussions: These are areas that are not up to par. Would need more time + discussion to better understand the product and users.
Accessibility surrounding Number Input and min + max values. Currently uses as aria-label to provide the min and max value for each input as a stop gap solution.
Vertical is Broken for both Single and Multi Sliders. The change to using a Number Input does not play not with the width of a vertical slider (for single) and the use of two inputs do not play well with the verticality.
Utilize the "style" field to determine the sizing of the multi range slider track
Are there ways to improve the # of code lines surrounding the Multi Range Slider + its supporting css.
Need tests around the new Multi Slider + update old tests for the Range Slider
Closes #
Changes
Had to force the Typescript package to 4.2.2 to allow the package to compile on local
Changed the Single Range Input Max value into an Input [type=Number]. This allows a user to be able to input a value vs. having to use the slider. This change is meant to address screen reader users + those with finite motor controls in their hands.
Created a Multi Range Slider type, in addition to the existing single. This allows for 2 input selectors, with Input [type=Number[] for both the lower and upper values.
Supporting tweaks to the RangeSlider and Input tsx files to support the Multi Range Slider
Known Issues/Discussions: These are areas that are not up to par. Would need more time + discussion to better understand the product and users.
Accessibility surrounding Number Input and min + max values. Currently uses as aria-label to provide the min and max value for each input as a stop gap solution.
Vertical is Broken for both Single and Multi Sliders. The change to using a Number Input does not play not with the width of a vertical slider (for single) and the use of two inputs do not play well with the verticality.
Utilize the "style" field to determine the sizing of the multi range slider track
Are there ways to improve the # of code lines surrounding the Multi Range Slider + its supporting css.
Need tests around the new Multi Slider + update old tests for the Range Slider
Screenshots
153026280-35da76ba-ce9d-4732-8a83-979edfc9cf5a.png">
Checklist
Check all that apply