Skip to content

Nav drawer a11y problems #2252

@myasonik

Description

@myasonik

Critical (imo):

Less so:

  • The dock/undock button doesn't show up in a screen reader's rotor when the nav is expanded. (Should work the same as the "pin to top" buttons which do show up.)
  • All of the "pin to top" buttons should have aria-pressed=true|false defined on them to communicate their state.
  • The dock/undock button should have aria-pressed=true|false defined to communicate state. This can replace the role=switch and aria-checked=true|false.(EuiNavDrawer a11y, pt. 1 #2643)

Up for debate:
1. I think the focus order would be better in visual order. I get the argument that it's to keep users from having to tab through all the options, then hit "expand", then potentially go back to the option they want but I think it's so unexpected that it's difficult to find and you lose your place instead of it feeling smooth. I tried playing around with a super obvious focus state and that grabbed my attention enough that I knew what was going on but that'd be pretty far away from our current focus state styles.
2. I think EUI should provide a skip link past the navigation.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions