Open benbeaudry opened 4 months ago
Since the combobox spec was updated on the more recent side of things, it's entirely plausible that ACCNAME could be updated to provide further clarification.
Re: is it possible to have a combobox element that doesn't have a role of listbox:
If the combobox popup element has a role other than listbox
This sentence in the spec suggests that it is possible to have a role other than listbox, and seems to be specific to things like the mentioned tree, grid, or dialog that corresponds to the role of its popup
.
Discussion of value: https://github.com/w3c/accname/issues/200
Here is Ben's related issue on ARIA, which we will probably close as it is about the combobox value and we already have issues for that: https://github.com/w3c/aria/issues/2149
Additionally, this issue was discussed in the ARIA working group meeting, during new issue triage today: https://www.w3.org/2024/03/14-aria-minutes.html
I think the key phrase in the spec is "of the chosen option."
We could further clarify that this could be an empty string if no option is chosen or no option is present. Sometimes options will be dynamically rendered and there could be a state where the container is there but the options are not there (yet).
So the TODO here is indeed to add some additional language to help browser authors.
While working on this accname wpt with Daniel Clark, we stumbled upon the computation steps, section 2C, where it says:
However, in the combobox spec, it says:
We think (and are trying to confirm with the ARIA editors) that it's possible to have a combobox element that doesn't have a listbox and any option.
The combobox spec also says:
Which appears to indicate that a combobox without a listbox should have its name from its value, and its value computed from the descendants' content. Is that right? If that's the case, should we clarify the accname computation steps?