Re: Test of the SC

Sorry 

I didn't mean we needed to change the one posted to the web.  

What I meant was — that we should be able to create a VERSION of the WCAG 2.1 that meets  WCAG 2.1.   If we can’t then…  whatever provisions can’t work — should be questioned as being appropriate for A or AA

(Which part of the template keeps us from meeting the FWPD  ? ) 


Gregg C Vanderheiden
greggvan@umd.edu



> On Feb 19, 2017, at 4:55 PM, Katie Haritos-Shea <ryladog@gmail.com> wrote:
> 
> Sounds like a goal for the Rec
> 
> Katie Haritos-Shea
> 703-371-5545
> 
> On Feb 19, 2017 12:18 PM, "Andrew Kirkpatrick" <akirkpat@adobe.com <mailto:akirkpat@adobe.com>> wrote:
> Gregg,
> I agree with that in principle but given that we are not able to make changes to the requires W3C template quickly we won’t be able to do that for the FWPD.
> 
> Thanks,
> AWK
> 
> Andrew Kirkpatrick
> Group Product Manager, Standards and Accessibility
> Adobe
> 
> akirkpat@adobe.com <mailto:akirkpat@adobe.com>
> http://twitter.com/awkawk <http://twitter.com/awkawk>
> 
> 
> 
> 
> 
> 
> 
> On 2/19/17, 11:47, "Gregg C Vanderheiden" <greggvan@umd.edu <mailto:greggvan@umd.edu>> wrote:
> 
> >One of the criteria for a Success Critions is that it is practical to apply across web content.
> >
> >Since the WCAG is full of experts at making web pages accessible — it seems to me that a good test of any SC would be that the WCAG can figure out how to make any page conform to them.
> > Not that we need to start fixing everyone’s pages  — but if someone asserts the proposed SC can’t be met by a page (with minor fix that doesn’t wreck the functionality) that should be a good indication that the SC would not meet the test.
> >
> >AT A MINUMUM - we should be able to make the current  draft WCAG 2.1 meet all of the Level A and AA  SC.
> >
> >
> >Gregg C Vanderheiden
> >greggvan@umd.edu <mailto:greggvan@umd.edu>
> >
> >
> >