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
Mapping rules to WCAG 2.0 Failure Techniques is problematic. #15
Comments
Can't reconcile "ACT Rules should map to [WCAG 2.0 Failure Techniques]" and "It does not include any ACT Rules". Either it maps rules or it doesn't include rules, not both. - Michael Cooper |
The document says (section 3.8 2.8) that the rule set will test for failures. Will these rules be based solely on our documented failure techniques? If so the rule set may be limited. Some people have given up trying to introduce failures. David has pointed out [1] that the WCAG Working Group has approved 3 small administrative failures in 8 years. John Foliot has said [2] "I also struggle myself to understand how/why Failure Techniques are so important to some content creators. In a simplistic view, Failures seem to be 'Don’t do this' statements, whereas Techniques for Success are 'You should do this (or this, or this, or this)' – and so I see the fundamental difference as being one between positive re-enforcement and negative re-enforcement, and as the guy known to state 'Be the Fireman and not the Cop' I am struggling to understand how the negative re-enforcement provides value (but I leave open the possibility that it does, and I’m just not seeing it)." Will the Working Group will be adding further failure techniques? [1] https://lists.w3.org/Archives/Public/w3c-wai-gl/2016AprJun/0336.html
|
@Laura asked (quoting JF): “I am struggling to understand how the negative re-enforcement provides value” |
The part about “ACT Rules should map to [WCAG 2.0 Failure Techniques]” is problematic because we have relatively few of those. - Bruce Bailey
WCAG WG Survey - November 2016
The text was updated successfully, but these errors were encountered: