Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"undefined" value allowed to use? #2079

Open
JAWS-test opened this issue Nov 16, 2023 · 1 comment
Open

"undefined" value allowed to use? #2079

JAWS-test opened this issue Nov 16, 2023 · 1 comment
Assignees

Comments

@JAWS-test
Copy link
Contributor

Some attributes have the default value "undefined". May this value be used? I think not, but I have not found any statements on this in the ARIA specification and "undefined" is used as a valid value in the ACT rules.

Example: aria-checked=undefined

  • At roles where aria-checked is allowed (e.g. checkbox) it makes no sense because one of the three values (true, false, mixed) must be used.
  • All roles where aria-checked is not permitted (e.g. button) have aria-checked=undefined implicitly, but this must not be set explicitly because the attribute is not permitted

See: #2078 (comment) and https://www.w3.org/WAI/standards-guidelines/act/rules/6a7281/proposed/#passed-example-3

@JAWS-test
Copy link
Contributor Author

I also think the addition of "default" to "undefined" is wrong:

  • "default" is only correct for elements where the attribute is not allowed
  • "default" is sometimes a different value for elements that allow the attribute, e.g. "false" or "true" for aria-selected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants