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.

Sign up for GitHub

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

Jump to bottom

[Accessibility] APM should self-announce and auto-focus search field #28143

Open
aphelionz opened this issue Jan 6, 2019 · 5 comments
Open

[Accessibility] APM should self-announce and auto-focus search field #28143

aphelionz opened this issue Jan 6, 2019 · 5 comments
Labels
bug Fixes for quality problems that affect the customer experience defect-level-3 Moderate UX disruption or potentially confusing obs-accessibilty A11Y issues in the Obs. solution. Project:Accessibility Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team WCAG AA

Comments

@aphelionz
Copy link
Contributor

aphelionz commented Jan 6, 2019 •
edited by alexwizp
Loading

tldr: Make sure that the query bar input contains the necessary aria labels, so the screen reader can announce that on enter/focus.

Steps to reproduce (assumes ChromeVox or similar)

  1. Tab through the nav menu to APM
  2. Press Enter

screenshot_20190105_195756

Actual Result
3. "Kibana" and then user must tab to the search box

Expected Result
3. Search is auto-focused, and consider a friendly message like "Welcome to APM"

Meta Issue #26856
Kibana Version: 6.5
Relevant WCAG Criteria: https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels
@aphelionz aphelionz mentioned this issue Jan 6, 2019
Open
6 tasks
@aphelionz aphelionz added the Team:APM All issues that need APM UI Team support label Jan 6, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui

@aphelionz aphelionz changed the title [Accessibility] APM should self-announce and [Accessibility] APM should self-announce and auto-focus search field Jan 9, 2019
@jasonrhodes
Copy link
Member

Waiting on advice from some Kibana folks on what this means before this is ready to pull in. See here: #26856 (comment)

@myasonik myasonik mentioned this issue Dec 18, 2020
Open
@botelastic
Copy link

botelastic bot commented Nov 1, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the stale Used to mark issues that were closed for being stale label Nov 1, 2021
@smith smith added the obs-accessibilty A11Y issues in the Obs. solution. label Oct 14, 2024
@botelastic botelastic bot removed the stale Used to mark issues that were closed for being stale label Oct 14, 2024
@smith smith removed good first issue low hanging fruit Project:Accessibility Team:APM All issues that need APM UI Team support WCAG A obs-accessibilty A11Y issues in the Obs. solution. labels Oct 14, 2024
@smith smith added the Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team label Oct 14, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

@smith smith added bug Fixes for quality problems that affect the customer experience Project:Accessibility obs-accessibilty A11Y issues in the Obs. solution. labels Oct 14, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-accessibility (Project:Accessibility)

@alexwizp alexwizp added the defect-level-3 Moderate UX disruption or potentially confusing label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience defect-level-3 Moderate UX disruption or potentially confusing obs-accessibilty A11Y issues in the Obs. solution. Project:Accessibility Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team WCAG AA
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@smith @aphelionz @jasonrhodes @sorenlouv @elasticmachine @alvarolobato @alexwizp @rayafratkina