[Switch] Enhance the component's colors for a11y and usability #10483
Labels
0 - new
New issues that need assignment.
a11y
Issues related to Accessibility fixes or improvements.
ArcGIS Hub
Issues logged by ArcGIS Hub team members.
calcite-components
Issues specific to the @esri/calcite-components package.
design
Issues that need design consultation prior to development.
enhancement
Issues tied to a new feature or request.
impact - p1 - need for current milestone
User set priority impact status of p1 - need for current milestone
p - high
Issue should be addressed in the current milestone, impacts component or core functionality
visual changes
Issues with visual changes that are added for consistency, but are not backwards compatible
Check existing issues
Summary
We got a number of accessibility violations on calcite-switch when LevelAccess audited Hub. See:
I think these boil down to: when the switch is off the track border (
--calcite-color-border-2
/#d4d4d4
) does not sufficiently contrast with the track background (--calcite-color-foreground-2
/#f3f3f3
). It would not sufficiently contrast with even a white (#ffffff) surrounding background either but I think it is sufficient to focus on making its own border and background contrast sufficiently.Actual Behavior
calcite switch has insufficient contrast between the track border and track background when in the off position.
Expected Behavior
calcite-switch should have sufficient contrast between the track border and track background when in the off position. I think something like border: #949494 (--calcite-color-border-input) and background #ffffff (--calcite-color-foreground-1) would do it.
Acceptance criteria
Reproduction Sample
https://codepen.io/mjuniper/pen/rNXemPZ?editors=100
Reproduction Steps
Reproduction Version
2.13.0
Working W3C Example/Tutorial
No response
Relevant Info
No response
Regression?
No response
Priority impact
impact - p1 - need for current milestone
Calcite package
Esri team
ArcGIS Hub
The text was updated successfully, but these errors were encountered: