Open rahimabdi opened 2 months ago
Maybe the "not applicable" in the parenthesis could be replaced with the wording and examples you've provided, something like:
true/false/undefined Value representing true, false, or undefined (The meaning of 'undefined' is attribute dependent. For example, aria-checked="undefined" means that "The element does not support being checked", while aria-hidden="undefined" is a synonym for aria-hidden="false".). The default value for this value type is undefined unless otherwise specified. For example, an element with aria-expanded set to false is not currently expanded; an element with aria-expanded set to undefined is not expandable.
@rahimabdi are you interested in drafting a PR with the definition of undefined you suggest?
@spectranaut Yes, happy to do so!
Compiling all the uses of undefined and their respective meanings here:
aria-checked
= The element does not support being checkedaria-current
= Does not represent the current item within a setaria-expanded
= Element does not own or control a grouping element that is expandablearia-grabbed
= Indicates that the element does not support being draggedaria-hidden
= The element’s hidden state is determined by the user agent on whether it is renderedaria-orientation
= The element’s orientation is unknown or ambiguousaria-pressed
= The element does not support being pressedaria-selected
= The element is not selectablearia-multiselectable
= Only one item can be selected
Describe the change
As of ARIA 1.3,
aria-hidden="false"
will be a synonym ofaria-hidden="undefined"
. However, I noticed that the "undefined" value is now differently defined for various states and properties, e.g.,:aria-checked="undefined"
means that "The element does not support being checked."; similarly,aria-pressed="undefined"
means that "The element does not support being pressed."aria-expanded="undefined"
means that "The element does not own or control a grouping element that is expandable."aria-orientation="undefined"
means that "The element's orientation is unknown/ambiguous."For
aria-hidden="undefined"
, it equates to "The element's hidden state is determined by the user agent based on whether it is rendered."With the changes to
aria-hidden
, should we update section 6.2.4 Value and provide a broad definition of what "undefined" means, or perhaps note that it is property-dependent? The current definition of "undefined" does not appear to encompass the full breadth of what this value means: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