RE: Supplementary document for WCAG 2.1

+1 - *but*, this is a sloppy way to address us not getting the work done to update 2.1 because we had identified, in my opinion, a too short, unrealistic timeline for development of an important international standard. That is why we are here now, doing this today. Please keep this in mind for a *next* update.

 

 

​​​​​* katie *

 

Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)

 

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

NOTE: The content of this email should be construed to always be an expression of my own personal independent opinion, unless I identify that I am speaking on behalf of Knowbility, as their AC Rep at the W3C - and - that my personal email never expresses the opinion of my employer, Deque Systems.

 

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com] 
Sent: Tuesday, May 23, 2017 12:50 PM
To: WCAG <w3c-wai-gl@w3.org>
Subject: CFC: Supplementary document for WCAG 2.1
Importance: High

 

Resending with the “high priority” flag per our process…

 

Call For Consensus — ends Thursday May 25rd at 12:00pm Boston time.

 

The Working Group has discussed the idea of providing additional guidance for accessibility beyond what is able to be included within WCAG 2.1. The idea is that success criteria proposals that cannot reach consensus or that there is insufficient time to review still have valuable information that might be able to be published for use. This idea was surveyed (https://www.w3.org/2002/09/wbs/35422/WCAG21_supp/results <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2FWCAG21_supp%2Fresults&data=02%7C01%7C%7C0e1bcac07c814137cfe008d4a1f37ca4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636311514529786507&sdata=Z09nKmrz3%2BdDRAlSQIgS6EnTF3tnyKnkhx6IU63M3ds%3D&reserved=0> ) and discussed on the call (https://www.w3.org/2017/05/23-ag-minutes.html#item01 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2017%2F05%2F23-ag-minutes.html%23item01&data=02%7C01%7C%7C0e1bcac07c814137cfe008d4a1f37ca4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636311514529786507&sdata=fuNXCihUvTIK85l38EKARZUd1nbx6vv6mPMVhkv2TNg%3D&reserved=0> ) and a resolution received consensus:

 

RESOLUTION: the working group has agreed to publisihing supplemental guidance in 1 document that is non-normative

 

If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.

 

Thanks,

AWK

 

Andrew Kirkpatrick

Group Product Manager, Standards and Accessibility

Adobe 

 

akirkpat@adobe.com <mailto:akirkpat@adobe.com> 

http://twitter.com/awkawk <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C0e1bcac07c814137cfe008d4a1f37ca4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636311514529786507&sdata=O8WWKVhUNZMueiHT4tYMcpGAwn8CCG0MbtYsKZc6jO4%3D&reserved=0> 

Thanks,

AWK

 

Andrew Kirkpatrick

Group Product Manager, Accessibility

Adobe 

 

akirkpat@adobe.com <mailto:akirkpat@adobe.com> 

http://twitter.com/awkawk <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C0e1bcac07c814137cfe008d4a1f37ca4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636311514529786507&sdata=O8WWKVhUNZMueiHT4tYMcpGAwn8CCG0MbtYsKZc6jO4%3D&reserved=0>