Update Understanding On Input (SC 3.2.2) #1017
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
swapped out violation for failure impaired for disabled removed unnecessary empty lines
|
Discussed on backlog call, 2/21. |
|
I reviewed this PR for the WCAG 2.x group. I'll admit that while it makes sense, I'm not sure it's necessary. The first change - mentioning that things still need to be keyboard-accessible - seems an unnecessary cross-reference (as the same hold true for all other SCs). The same is true for the additional note I can see how this seems to directly address the problem brought up in #898 ... but it seems overly specific for something that, in essence, is a case that currently falls between the cracks ... "nominally passes the word of the SC, but it a dreadful user experience" |
|
I believe several people have indicated this is a failure of 2.1.1. I'd like to see if we have agreement that the problem described in the original issue -- someone triggers an on input change in a radio button group, it advances a survey -- would be considered a failure. |
|
Resolving this through #898 |
Fixes #898