-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
High
-
None
-
Affects Version/s: 8.20.1
-
Component/s: Accessibility
-
- 4.1.2
- AXSR-20
- Level-A
- Level-AA
- WCAG21
- accessibility
- ax-at-JAWS
- ax-at-NVDA
- ax-at-VO
- ax-at-user
- ax-bug
- ax-customer-escalated
- ax-desktop
- ax-dev-ready
- ax-esc-dt
- ax-high-priority
- ax-jira
- ax-jiradc-header
- ax-macos-safari
- ax-platform-dc
- ax-qa
- ax-qa-bl
- ax-qa-prioritised
- ax-triaged
- ax-vpat-serious
- ax-windows-chrome
- ax-windows-firefox
- axsr-high-priority
- axsr-march-22
- ozghonnyk
-
8.2
-
Severity 2 - Major
Issue description
When user navigates to "Search" input field (which is available in header region) it triggers a drop-down. The screen reader does not render when the drop-down items receives keyboard focus. This issue takes place in Firefox/NVDA and Voiceover/Safari
STR
- Turn on screen reader and navigate to "Search" input field present in header region.
Actual Behaviour
When user try to navigate in options of "Search" field with up/down or Tab keys, it is receiving keyboard focus but screen reader does not make announcement for that. As a result screen reader users will not be able to interact with drop-down items effectively.
Expected Behaviour
When user navigates in drop-down items of "Search" input field with up/down or Tab keys, it should receive keyboard focus and screen reader should make announcement for that.
For more details on editable combo-box please refer this link : https://www.w3.org/TR/wai-aria-practices-1.2/examples/combobox/combobox-autocomplete-list.html
Screenshot
Screen Recording
Screen Recording 2022-02-16 at 4.18.51 PM.mov
AXQA Ref:AXQA-185
- is resolved by
-
-
- Closed
-