Open MelSumner opened 10 months ago
Looking at my notes from different ACCVALUE discussions, after I condense them all, it seems like the biggest question is this:
Is there some implementor issue that means we need an accessible value computation algorithm?
There's the idea that obtaining an accessible value should be in the ACCNAME spec (Accessible Name, Description and Value). But what would an ACCVALUE calculation look like?
Let's look at what already exists.
From the combobox documenation in ARIA spec
The value of a combobox is represented by one of the following:
If the combobox element is a host language element that provides a value, such as an HTML input element,
the value of the combobox is the value of that element.
Otherwise, the value of the combobox is represented by its descendant elements and can be determined
using the same method used to compute the name of a button from its descendant content.
It appears as though we already have an acceptable way to do this.
Using the same method to compute the name of a button from its descendant content
value
of a given input?We'll probably have to go over it again during one of the ARIA meetings, but from what I can recall when we spoke of this late last year in one of the other meetings, we determined that it wasn't necessary to create a whole new algorithm, but instead do the following.
We talked about this briefly in the meeting last week, and Sarah said she remembered this issue and wanted to take a stab at it: https://www.w3.org/2024/02/22-aria-minutes#t04
Breaking Issue #184 into action steps. Each of these items could be completed in distinct PRs, or a single PR.