aria
aria copied to clipboard
w3c
Values table for aria-multiselectable/aria-current are missing "undefined"
Describe the change
Some states/properties reference undefined as a value however, this value is missing from their Values table:
aria-multiselectable
The Values table for aria-multiselectable does not have an entry for undefined however, the spec states that both false and undefined are valid values for this property:
| Section | Text |
|---|---|
| option role | The value of aria-multiselectable on the listbox is false or undefined. |
| tab role | The value of aria-multiselectable on the tablist is false or undefined. |
| treeitem role | The value of aria-multiselectable on the tree is false or undefined. |
aria-current
The aria-current description section says "If the attribute is not present or its value is the empty string or undefined...". The value undefined is also missing from aria-current's Values tables.
Should undefined be added?
Link to the version of the specification or documentation you were looking at
Link to documentation: https://w3c.github.io/aria/
Does the issue exists in the editors draft (the editors draft is the most recent draft of the specification)?
Yes.
Discussed briefly in today's working group meeting: https://www.w3.org/2024/05/16-aria-minutes#t08
Meeting minutes from June 27 ARIA WG "undefined" deep dive: https://github.com/w3c/aria/issues/2177#issuecomment-2226727206.
I believe the next steps for aria-multiselectable and aria-current is specifying that the absence of a value is what should be clarified as "undefined" in prose (i.e., state/property is undefined means it is omitted, not the token undefined).
Adding to July 18 2024 ARIA WG agenda.
@rahimabdi does this still need to be discussed, given the discussion last week: https://www.w3.org/2024/07/25-aria-minutes#t05
Closing because aria-current/aria-multiselectable (and all ARIA states/properties) will include "missing value default" values as part of: https://github.com/w3c/aria/issues/2281.