Difficult to visually determine if focused action is active #10408
Labels
0 - new
New issues that need assignment.
ArcGIS Field Apps
Issues logged by ArcGIS Field Apps team members.
bug
Bug reports for broken functionality. Issues should include a reproduction of the bug.
calcite-components
Issues specific to the @esri/calcite-components package.
design
Issues that need design consultation prior to development.
impact - p2 - want for an upcoming milestone
User set priority impact status of p2 - want for an upcoming milestone
needs triage
Planning workflow - pending design/dev review.
Check existing issues
Actual Behavior
When an action has focus, it is difficult to tell if the action is active.
Expected Behavior
The action's background is the same as when it's unfocused and unhovered. The background color of the inactive action is still set to
--calcite-action-background-color-hover
when hovered.Reproduction Sample
https://codepen.io/nwhittaker-esri/pen/RwXPRVB
Reproduction Steps
active
state.active
state.Reproduction Version
2.12.2
Relevant Info
An accessibility concern is whether the
active
styling offers enough contrast. I was considering that out-of-scope and perhaps more appropriate for #5003 anyway.Should reconsider if the focus style should even get a background change in cases where its focus ring is visible. Of course the user can shift focus, but this is a less discoverable remediation, and it also adds effort to using the action. If focus and hover styles did not share a background color, then moving the pointer off the action would be a more discoverable remediation.
Regression?
No response
Priority impact
impact - p2 - want for an upcoming milestone
Impact
Looking for a workaround,
--calcite-action-background-color-hover
exists, however what really would be needed is a way to set the hover and focus colors separately.Usability is mostly impacted as it is not immediately clear if an action is really inactive, or not.
Calcite package
Esri team
ArcGIS Field Apps
The text was updated successfully, but these errors were encountered: