Re: CFC - Description for Guideline 6.2

not for me

All the best

Lisa Seeman

LinkedIn, Twitter





---- On Mon, 15 Jan 2018 04:31:53 +0200 Andrew Kirkpatrick<akirkpat@adobe.com> wrote ---- 

      The pull request shows it pretty clearly:  https://github.com/w3c/wcag21/pull/633
  
  
   Thanks,
 
  AWK
 
   
 
  Andrew Kirkpatrick
 
  Group Product Manager, Accessibility
 
  Adobe 
 
   
 
  akirkpat@adobe.com
 
 
 http://twitter.com/awkawk
  
  From: Jonathan Avila <jon.avila@levelaccess.com>
 Date: Sunday, January 14, 2018 at 18:55
 To: "lisa.seeman@zoho.com" <lisa.seeman@zoho.com>, WCAG <w3c-wai-gl@w3.org>
 Subject: RE: CFC - Description for Guideline 6.2
 Resent-From: WCAG <w3c-wai-gl@w3.org>
 Resent-Date: Sunday, January 14, 2018 at 18:54
 
   
 
 I honestly can’t figure out what’s in the CFC either.  
  
 One link gives a 404.  The other points to github issues and the other to minutes discussing the item.
  
 I appreciate all of the work that people have put in – but it’s not clear what the former and proposed language is and what we are agreeing or not agreeing to.
  
  Jonathan 
 
  
   From: lisa.seeman [mailto:lisa.seeman@zoho.com] 
 Sent: Sunday, January 14, 2018 10:46 AM
 To: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
 Subject: Re: CFC - Description for Guideline 6.2
 
 
  
  please consider this email an objection
  All the best
 
 Lisa Seeman
 
 LinkedIn,  Twitter
 
 
 
 
  
   
 ---- On Fri, 12 Jan 2018 10:41:37 +0200 <lisa.seeman@zoho.com> wrote ---- 
 
    Hi
   
 
  I have clicked on the links of this CFC. The minuets are hard to understand and the link to the pull request mearly takes me to the full specification and I can not tell what this CFC actually is about - IE - What is the original wording and what is the change.
  All the best
 
 Lisa Seeman
 
 LinkedIn,  Twitter
 
 
 
 
  
   
 ---- On Thu, 11 Jan 2018 16:17:44 +0200 Glenda Sims<glenda.sims@deque.com> wrote ---- 
 
    +1
 
   
     glenda sims  |   team a11y lead   |     deque.com    |    512.963.3773      
 *web for everyone. web on everything.* -  w3 goals
 
 
 
 
 
 
 
 
 
 
  
  On Wed, Jan 10, 2018 at 1:48 PM, Andrew Kirkpatrick <akirkpat@adobe.com> wrote:
    Call For Consensus — ends January 12 at 1:30pm Boston time.
  
 The Working Group has discussed a change to add a description to the 2.6 Guideline. This was discussed on the call (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F01%2F10-ag-minutes.html%23item05&data=02%7C01%7Cakirkpat%40adobe.com%7Caed15164ff234e7d3b9a08d55baa51f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636515709442489386&sdata=uokouznuisqXnNd6BzuGj9WpEWDVDNSJu%2BGLHIrLAHM%3D&reserved=0).
  
 The specific changes are detailed in this pull request: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag21%2Fpull%2F633&data=02%7C01%7Cakirkpat%40adobe.com%7Caed15164ff234e7d3b9a08d55baa51f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636515709442489386&sdata=feyDQAvhTBIpMC02lHfOSgYN%2F5pExNHMkMI1IXZZE8c%3D&reserved=0  (see implemented at)
  https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fadditional-sensor-inputs-gl%2Fguidelines%2Findex.html%23additional-sensor-inputs&data=02%7C01%7Cakirkpat%40adobe.com%7Caed15164ff234e7d3b9a08d55baa51f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636515709442489386&sdata=U25wEU2wJTo9DrJsnphIFgnWwIX21U31GgcR6LokMOE%3D&reserved=0
 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, Accessibility
 Adobe 
  
 akirkpat@adobe.com
 http://twitter.com/awkawk