-
Notifications
You must be signed in to change notification settings - Fork 276
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
[WCAG AAA] - Move H28 from sufficient to advisory in 3.1.4 Abbreviations SC #4195
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Discussed on Backlog call 1/17. Moved to Ready for approval. |
IMO, there should be some language inside the technique, and maybe inside the Understanding document (i.e., in the final example), explaining the matter raised in the issue. The SC language reads:
The use of
The argument is that use of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am of the opinion that something should be added to H28 explaining why it has been down graded from sufficient to advisory.
Keyboard support for abbr
has been weak, but historically we didn't assert that the default behavior of the element fails 2.1.1. But maybe enough time has passed that we should?
Discussed on backlog call 2/7. @mbgower agreed to take another pass, stays in For discussion. |
Discussed on backlog call 2/21. Keeping in For Discussion as Mike is still has this in his queue. |
Added in an explanation of why this was downgraded to an advisory technique.
updated the language to do with G102
I have added an explanation to the top of the H28 techniques which I think resolves this. |
Closes: #3019
H28 is not a sufficient technique, rather than an advisory one, since it would likely fail 2.1.1
Actions: moved H28 from sufficient to advisory.