You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The EuiHorizontalSteps component blocks click events when a step is disabled, but allows the button to take keyboard focus. It would be an improvement if the button had a tabindex="-1" to prevent it from taking keyboard focus either while disabled. Screenshot below. an aria-disabled="true" attribute so screen reader users can hear the button in the tabindex, but also be made aware it's not currently available.
1Copenut
changed the title
< EuiStepsHorizontal/> should not allow keyboard focus on disabled stepsEuiStepsHorizontal should not allow keyboard focus on disabled steps
Apr 15, 2024
Would setting aria-disabled on the disabled step suffice? If not, that directive would conflict directly with the goal of #5666.
Yes it would. I talked with our auditor a bit more and we agreed aria-disabled="true" while still allowing focus, is the right course of action. I'll take this as an action item to update the component and issue a PR.
1Copenut
changed the title
EuiStepsHorizontal should not allow keyboard focus on disabled stepsEuiStepsHorizontal should have aria-disabled on steps that users cannot take action
Apr 18, 2024
Describe the problem
The EuiHorizontalSteps component blocks click events when a step is disabled, but allows the button to take keyboard focus. It would be an improvement if the button had
aantabindex="-1"
to prevent it from taking keyboard focus either while disabled. Screenshot below.aria-disabled="true"
attribute so screen reader users can hear the button in the tabindex, but also be made aware it's not currently available.WCAG or Vendor Guidance (optional)
Screenshots or Trace Logs
The text was updated successfully, but these errors were encountered: