Note: This applies to the home page call to action panels as well
Steps to reproduce (assumes ChromeVox or similar)
[Tab] or [Shift+Tab] to the search field- Enter the letters
"on" to filter the list
- Press
[Tab] to navigate to a navigation section with more than one result, such as the one shown above
- 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
Note: This applies to the home page call to action panels as well
Steps to reproduce (assumes ChromeVox or similar)
[Tab]or[Shift+Tab]to the search field"on"to filter the list[Tab]to navigate to a navigation section with more than one result, such as the one shown above[Enter]to activate the menu item linkActual 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