-
Notifications
You must be signed in to change notification settings - Fork 269
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
prop or att #7
Comments
If we talk about "the aria-label property" then we should use . Similarly, if we say "the input should have aria-label set to..." then we're talking about the attribute and should use . We should fix these for consistency, but currently it is not super-high priority since both prop and att are transformed to <code> elements in the HTML. I'll leave open as a reminder... |
Because Github is killing the Markup in comments, I think it's better to write att and prop. I went through the document short and saw some missing markup. I can do that in the next week. |
Thanks for all of your edits to address att and prop in the source documents. |
Created practices/examples folder, and added link design pattern example...
Dfferent markup for property in ARIA-techniques:
"aria-required property" (like in 411, 513 - prop) or
"aria-describedby property" (like in 2052 - att) and "aria-labelledby property" (like in 1330-1335 - att)?
The text was updated successfully, but these errors were encountered: