Remove verbiage regarding combobox values #1871
Conversation
Fixes w3c#1720. Removing the MUST statement about getting the value for a combobox because it includes logic to get a value. The method to get a value will be handled outside the ARIA spec, in either accName or Core-AAM. See the discussion at w3c/accname#184.
Removing the MUST statement regarding the value of a combobox
|
This is a follow up to closing this issue: #1827 |
There was a problem hiding this comment.
I marked this PR as "draft" because I think we shouldn't change the specification until we have something specific to point to.
Some context: When reviewing the PR #1827 to add non-input value calculations to listbox and searchbox, we realized the value calculation was more complicated than presented. Sarah suggested, since there is some discussion of value already in acc name, to move the value calculation to there.
Here is the issue for that: w3c/accname#184
I think we should put this PR on hold until the accname work is done, then we can point to accname in this PR.
|
Thank you @spectranaut, I just caught up on all the discussion and agree this should be on hold. Even if there are some potential issues with the current language, it is working in practice in Chromium now. For select-only comboboxes to work, it is imperative that the browser calculate a value. The accname algorithm is the best we have at the moment. In practice, it is not as important for ARIA to say anything about the value of textbox and searchbox. That is not to say that it doesn't matter, it is just not as pressing an issue in practice. |
|
We are discussing adding combobox values to accname, when we do that we will update this language. |
Closes #1720
Removed verbiage regarding combobox values which includes a MUST statement.
##1720
Preview | Diff