| Summary: | AX: VoiceOver doesn't announce aria-activedescendant value for select-only combobox specification | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Nabeel K <nabeel.kabeer> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | andresg_22, aron_j, awhite, giacomo.petri, joewatkinspdx, kiya.doig, pweil2, uxengineering, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 15 | ||
| Hardware: | Mac (Intel) | ||
| OS: | macOS 10.15 | ||
| Bug Depends on: | 271287 | ||
| Bug Blocks: | |||
|
Description
Nabeel K
2021-10-14 00:06:42 PDT
Point number 2 and 3 are related to Bug 236881 (something is happening when aria-expanded is added to an element with role="comobox"). As for point 4- using arrow keys to navigate through options does not work because aria-controls is not appropriatelyimplemented. In the previous iterations (https://www.w3.org/TR/wai-aria-practices-1.1/examples/combobox/aria1.0pattern/combobox-autocomplete-list.html) all works fine because the listbox is associated through aria-owns on the combobox. The 1.2 pattern requires that aria-activedescendant works through the use of aria-controls, see the following from the ARIA spec about comboboxes: "... one common convention is that Down Arrow moves focus from the input to the first focusable descendant of the popup element. If the popup element supports aria-activedescendant, in lieu of moving focus, such keyboard mechanisms can control the value of aria-activedescendant on the combobox element. When a descendant of the popup element is active, authors MAY set aria-activedescendant on the combobox to a value that refers to the active element within the popup while focus remains on the combobox element." So, Chrome and Firefox have implemented the support for aria-activedescendant when using aria-controls. I think the whole thing is quite confusing because the definition of aria-activedescendant does not mention anything about aria-controls. Anyway, please, please, please implement this as soon as possible as none of the 1.2 patterns work in safari- the only way to do it at the moment is by adding aria-owns which caused issues in the past for touch screen devices. Scratch my comment about the confusing thing, just checked and point two of the definition of aria-activedescendant is clear: "The element with DOM focus is a combobox, textbox or searchbox with aria-controls referring to an element that supports aria-activedescendant, and the value of aria-activedescendant refers to an owned element of the controlled element. For example, in a combobox, focus may remain on the combobox while the value of aria-activedescendant on the combobox element refers to a descendant of a popup listbox that is controlled by the combobox." https://www.w3.org/TR/wai-aria-1.2/#aria-activedescendant So, please implement. Still not working. Using Safari + VO users are still not able to perceive the available options. What is the status of this, please? The problem still exists with Safari 16.5 and MacOS 12.6.6. Virtually all of the APG 1.2 Combobox patterns rely on aria-activedescendant for reading out the current option.Please assign this to someone and implement the specs ASAP. Hello, what is the status of this ticket? This issue prevents MAC users from utilizing our community portal. Thank you. Still an issue in 2024. MacOS 14.4.1 / Safari 17.4 This is still an issue with Safari Version 17.5, MacOS: Sonoma Version 14.5 Still reproducible at https://www.w3.org/WAI/ARIA/apg/patterns/combobox/examples/combobox-select-only/ VoiceOver does not read the options in the listbox. It works in other browsers (Chrome, Firefox). Likely this is very related to Bug 209076. As Nick Williams said there; The criteria for a fix should be "all ARIA APG combobox/listbox examples work as expected/intended". A fix for this would be really impactful for my company's design system and customers. Please! |