- From: David MacDonald <david100@sympatico.ca>
- Date: Sat, 2 Jun 2018 21:18:02 -0400
- To: Eric Eggert <ee@w3.org>
- Cc: Shawn Henry <shawn@w3.org>, EOWG <w3c-wai-eo@w3.org>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CAAdDpDYDdF1k09+K50tP-xdS+Ro4wWXG+i7BpghYjthQXYG-qw@mail.gmail.com>
Your right that link to the quickref doesn't have any other standards.... That's weird I was in a window that looked just like the Quickref... and it had JIS, EU, 508, WCAG 2, WCAG 1, WCAG 2.1 etc.... Do you know what it is I ended up on? Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd GitHub <https://github.com/DavidMacDonald> www.Can-Adapt.com <http://www.can-adapt.com/> * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html> On Sat, Jun 2, 2018 at 1:42 PM, Eric Eggert <ee@w3.org> wrote: > Hi David, > > On 2 Jun 2018, at 18:01, David MacDonald wrote: > > > One thing that I find a bit of a head scratcher... in the filters section > > it has 12 different standards. I think that gives the impression they are > > all comparable and equal. > > Where do you see 12 different standards? I don’t understand where you get > this from. It is WCAG 2.1 and WCAG 2.0. There are no other standards in > there. > > We list the Techniques for different technologies as they are listed in > the Understanding/Techniques documentation created by this Working Group. > Is that what you mean? > > Can you elaborate? > > Eric > > > I think we should stick to our primary mission. We are the W3C and I > think > > we should present W3C standards. > > > > Cheers, > > David MacDonald > > > > > > > > *Can**Adapt* *Solutions Inc.* > > > > Tel: 613.235.4902 > > > > LinkedIn > > <http://www.linkedin.com/in/davidmacdonald100> > > > > twitter.com/davidmacd > > > > GitHub <https://github.com/DavidMacDonald> > > > > www.Can-Adapt.com <http://www.can-adapt.com/> > > > > > > > > * Adapting the web to all users* > > * Including those with disabilities* > > > > If you are not the intended recipient, please review our privacy policy > > <http://www.davidmacd.com/disclaimer.html> > > > > On Fri, Jun 1, 2018 at 2:39 PM, David MacDonald <david100@sympatico.ca> > > wrote: > > > >> Cursory look, seems great... > >> > >> Cheers, > >> David MacDonald > >> > >> > >> > >> *Can**Adapt* *Solutions Inc.* > >> > >> Tel: 613.235.4902 > >> > >> LinkedIn > >> <http://www.linkedin.com/in/davidmacdonald100> > >> > >> twitter.com/davidmacd > >> > >> GitHub <https://github.com/DavidMacDonald> > >> > >> www.Can-Adapt.com <http://www.can-adapt.com/> > >> > >> > >> > >> * Adapting the web to all users* > >> * Including those with disabilities* > >> > >> If you are not the intended recipient, please review our privacy policy > >> <http://www.davidmacd.com/disclaimer.html> > >> > >> On Fri, Jun 1, 2018 at 1:08 PM, Shawn Henry <shawn@w3.org> wrote: > >> > >>> Hi EOWG and WCAG, > >>> > >>> We've updated the How to Meet WCAG 2 (Quickref) tool to include 2.1. > The > >>> goal is to have one tool that meets multiple user needs -- including > people > >>> who only want 2.0, people who want only what's new in 2.1, etc. > >>> > >>> Prototype is here: > >>> https://wai-wcag-quickref.netlify.com > >>> > >>> Changes: > >>> * In the Filter tab, added "WCAG Version" dropdown with options: “WCAG > >>> 2.1”, “WCAG 2.0”, “Only Success Criteria added in 2.1” > >>> * In the "Selected Filters:" (yellow box), added indication of which > >>> version is selected: “WCAG 2.1”, “WCAG 2.0”, "Only what’s added in > WCAG 2.1" > >>> * In the "About" section, added link to WCAG 2.1 TR, and unlinked > >>> Techniques and Understanding. > >>> * Changed some links from 2.0 to 2.1. > >>> * Included with 2.1 SCs "(Added in 2.1)" after the Level > >>> > >>> (Note that the prototype doesn't include the 2.1 Techniques yet, and > will > >>> when released.) > >>> > >>> We plan on making this live with the 2.1 publication. > >>> > >>> We could tweak it later, although it's better to get any changes in now > >>> before people use it. > >>> If you have any significant concerns or changes, please open GitHub > issue > >>> asap, preferably by Monday morning. > >>> <https://github.com/w3c/wai-wcag-quickref/issues/new> > >>> > >>> Thanks, > >>> ~Shawn & Eric > >>> > >>> > >> > > > > > > -- > > Eric Eggert > Web Accessibility Specialist > Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C) > >
Received on Sunday, 3 June 2018 01:18:30 UTC