you can do that — but I’m not sure you need to. If you change the level — the SC is not required at the new level when it was not required at that level before. Hence #8 does not apply. (PS we already have at least one example of this in WCAG 2.0. There is already overlap between levels. You just don’t want overlap on the same level — or a requirement at a lower level that is already covered by a higher level) Gregg C Vanderheiden greggvan@umd.edu > On Jan 3, 2017, at 9:16 AM, Andrew Kirkpatrick <akirkpat@adobe.com> wrote: > > Gregg and Lisa, > > For reference we are talking about this list: https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria <https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria> > > #8 reads (including the prefix): > Success Criteria shall avoid creating a requirement for something that is already required by an existing Success Criterion. > > I think that your suggestion is fine in that we are already indicating that a level change is acceptable with #5 (Ensure for revised Success Criteria that pages that meet the revised guidance continue to meet the corresponding WCAG 2.0 Success Criteria). > > I think that perhaps the solution is that we just add “(Level changes are not regarded as new requirements)”. Thoughts? > > Thanks, > AWK > > Andrew Kirkpatrick > Group Product Manager, Standards and Accessibility > Adobe > > akirkpat@adobe.com > http://twitter.com/awkawk >
Received on Wednesday, 4 January 2017 22:53:44 UTC