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

Main Heading should be focused after a menu item is selected #622

Closed
aphelionz opened this issue Apr 2, 2018 · 2 comments
Closed

Main Heading should be focused after a menu item is selected #622

aphelionz opened this issue Apr 2, 2018 · 2 comments
Labels
accessibility - WCAG A Level A WCAG Accessibility Criteria accessibility documentation Issues or PRs that only affect documentation - will not need changelog entries stale-issue stale-issue-closed

Comments

@aphelionz
Copy link
Contributor

aphelionz commented Apr 2, 2018

Note: This applies to the home page call to action panels as well

Steps to reproduce (assumes ChromeVox or similar)

  1. [Tab] or [Shift+Tab] to the search field
  2. Enter the letters "on" to filter the list
  3. Press [Tab] to navigate to a navigation section with more than one result, such as the one shown above
  4. Press [Enter] to activate the menu item link

Actual Result
The list un-filters, leaving a non-sighted user lost in a context switch on input with no instructions or indication that something has changed. They then have to tab through a very long list to get to the content.

Expected Result
The H1 element that presents at the top of every major page of the site should be auto-focused on and read once an item is selected from the menu.

Suggested Fixes
Auto-focus the H1 on menu selection with Javascript, or even better, an anchor tag (if possible)

Category: #615: Elastic UI Chrome Accessibility
Relevant WCAG Criteria: 3.2.2 On Input and tangentially 2.4.1 Bypass Blocks

@rayafratkina rayafratkina changed the title Main Heading should be focused after a manu item is selected Main Heading should be focused after a menu item is selected Apr 3, 2018
@aphelionz aphelionz added the accessibility - WCAG A Level A WCAG Accessibility Criteria label May 6, 2018
@snide snide added the documentation Issues or PRs that only affect documentation - will not need changelog entries label Jun 8, 2018
@snide snide mentioned this issue Mar 9, 2021
41 tasks
@github-actions
Copy link

👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment.

@github-actions
Copy link

❌ We're automatically closing this issue due to lack of activity. Please comment if you feel this was done in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility - WCAG A Level A WCAG Accessibility Criteria accessibility documentation Issues or PRs that only affect documentation - will not need changelog entries stale-issue stale-issue-closed
Projects
None yet
Development

No branches or pull requests

2 participants