aria
aria copied to clipboard
w3c
Empty or non-matching values for ID reference and ID reference list - Clarification on author responsibilities
Closes: #2225
Clarification on author responsibilities concerning empty or invalid references for properties accepting ID reference (or ID reference list) as values.
The intention is, considering the dynamic nature of contemporary websites, to allow authors to set empty or "invalid" values, acknowledging the DOM can be populated accordingly when necessary.
Note:
The scrollbar role is currently the only role that requires an ARIA attribute with an ID reference (aria-controls). Should we make an exception for this scenario?
Deploy Preview for wai-aria ready!
| Name | Link |
|---|---|
| Latest commit | 2492505d27491742dc780527d4d302f3d6f242af |
| Latest deploy log | https://app.netlify.com/projects/wai-aria/deploys/686fab51db8370000853a81e |
| Deploy Preview | https://deploy-preview-2235--wai-aria.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify project configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Absolutely, since it affects https://www.w3.org/WAI/standards-guidelines/act/rules/in6db8/proposed/
Added label
@giacomo-petri something odd just happened with this branch. It's near impossible to review now.
@pkra, should I create a different PR starting from an updated branch?
@pkra, something strange is happening here. I rebased onto main, but there are still differences showing up. Every time I try to resolve them by cherry-picking the changes, when I commit, it prompts me to revert them back. If I do revert, it keeps asking me to apply the changes again. I'm not sure what's going on (you can check the logs to see for yourself).
@giacomo-petri I still have an old version of this branch from my rebase in March. I could try force-pushing this. I think it would only be missing my suggestion from last week. What do you think?
@pkra @giacomo-petri
We were discussing in ARIa Editors with @pkra what the prettier debacle may be coming from. And I think I've fixed this PR. Now I only see two changes. Since both of you have been more involved in this one that I have, let me know if this makes any sense.
ACT feedback: The role scrollbar still requires the use of the aria-controls attribute. ACT requires further clarification regarding this requirement and how it should apply specifically to scrollbars. Should the aria-controls attribute be removed as a requirement? Alternatively, should we clarify that the recent change applies in all cases except for elements with the scrollbar role?