W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2018

Re: WCAG2ICT for WCAG 2.1

From: Katie Haritos-Shea <ryladog@gmail.com>
Date: Fri, 21 Sep 2018 14:06:39 -0400
Message-ID: <CAEy-OxH-H37yFjn+smTVge4mwjVxzLJ7Z0WHoo8+DrvxppJoEw@mail.gmail.com>
To: David MacDonald <david@can-adapt.com>
Cc: Jonathan Avila <jon.avila@levelaccess.com>, WCAG <w3c-wai-gl@w3.org>, WCAG Editors <team-wcag-editors@w3.org>
Thank you David!!

** katie **

*Katie Haritos-Shea*


*Principal ICT Accessibility Architect, Vice President of Accessibility at
EverFi, **Board Member and W3C Advisory Committee Rep for Knowbility *

*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Oakton, VA **|* *LinkedIn Profile
<http://www.linkedin.com/in/katieharitosshea/>*

People may forget exactly what it was that you said or did, but they will
never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.




On Fri, Sep 21, 2018 at 10:42 AM David MacDonald <david@can-adapt.com>
wrote:

> Thanks for the feedback Jonathan
>
> I've amended the document so the SC numbers match the final draft of the
> WCAG 2.1, and I've deleted the notes for 1.4.12.
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
> Mobile:  613.806.9005
>
> 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, Sep 21, 2018 at 10:00 AM Jonathan Avila <jon.avila@levelaccess.com>
> wrote:
>
>> Hi David, this is very helpful and I agree.  The only comment I have is
>> that I noticed 1.4.12 is listed as 4.1.12 in the link.  Also the notes for
>> 1.4.12 seem more like 4.1.2.  My main suggestion would be around the
>> language for 1.4.12 which seem to get into the API rather than what the
>> markup language supports.
>>
>>
>>
>> Jonathan
>>
>>
>>
>> *From:* David MacDonald <david@can-adapt.com>
>> *Sent:* Friday, September 21, 2018 5:54 AM
>> *To:* WCAG <w3c-wai-gl@w3.org>; WCAG Editors <team-wcag-editors@w3.org>
>> *Subject:* WCAG2ICT for WCAG 2.1
>>
>>
>>
>> Hi All
>>
>>
>>
>> It has been announced that the new EN 301 549 is referencing the WCAG 2.1
>> and WCAG2ICT for electronic documents which is great news for the WCAG 2.1.
>>
>>
>>
>> This brings up the point that the WCAG2ICT needs an update to 2.1 because
>> it is based on WCAG 2.0. So documents don't have the same requirements
>> around contrast, etc. I've made a pass an unofficial draft of what an
>> updated WCAG2ICT might look like.
>>
>>
>>
>> http://davidmacd.com/WCAG/wcag2ict-21-discussion.html
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Cheers,
>> David MacDonald
>>
>>
>>
>> *Can**Adapt* *Solutions Inc.*
>>
>> Mobile:  613.806.9005
>>
>> 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>
>>
>>
>>
>
Received on Friday, 21 September 2018 18:07:17 UTC

This archive was generated by hypermail 2.3.1 : Friday, 21 September 2018 18:07:20 UTC