Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Accessibility] Announce Kibana route changes within an app #149213

Closed
5 tasks
vadimkibana opened this issue Jan 19, 2023 · 1 comment · Fixed by #150461
Closed
5 tasks

[Accessibility] Announce Kibana route changes within an app #149213

vadimkibana opened this issue Jan 19, 2023 · 1 comment · Fixed by #150461
Assignees
Labels
Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)

Comments

@vadimkibana
Copy link
Contributor

vadimkibana commented Jan 19, 2023

  • Create a solution which would correctly announce deep route changes within a Kibana application. Potentially how this could work with:
    • Through some integration into the default Kibana application router.
    • Maybe somehow through React components.
  • Make use of this new mechanism in some places in Kibana.
  • Write up a document of best practices of using this.

Partially addresses #135760

@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 19, 2023
@vadimkibana vadimkibana added Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) and removed needs-team Issues missing a team label labels Jan 19, 2023
@1Copenut
Copy link
Contributor

The EUI docs site is a good model for how to implement this improvement using EUI components. Having the EuiScreenReaderOnly as the first element in the React root gives us a consistent place to set focus programmatically and sets us up nicely to add the skip to content link as the first user-focusable element.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants