RE: CFC (call for consensus) google doc draft of content to publish

Regrets I am afraid that I have clashing meetings.

From: EA Draffan [mailto:ead@ecs.soton.ac.uk]
Sent: 12 March 2018 11:27
To: lisa.seeman <lisa.seeman@zoho.com>; public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Subject: RE: CFC (call for consensus) google doc draft of content to publish

I am so sorry I cannot make the meetings but I have added a few comments and corrected typos etc  Please check version history to undo any of my very minor changes if you do not like them.

Best wishes
E.A.

From: lisa.seeman [mailto:lisa.seeman@zoho.com]
Sent: 09 March 2018 13:27
To: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org<mailto:public-cognitive-a11y-tf@w3.org>>
Subject: CFC (call for consensus) google doc draft of content to publish

Hi Folks

I made a google doc draft of content to publish<https://docs.google.com/document/d/1eyvLsF_akaSx_6xK5Bx3ylJePN0QJC-6wt42pKolLEE/edit?usp=sharing> to put in the next working draft of the road map and gap analysis, as an appendix for Making content usable for people with cognitive and learning disabilities.

Can you look at the document and let us know if you approve it.  Please give your comments over by the 12th of march 2pm EST.

If there are changes that you would like but you can live with the current draft for publication please state that as well. that way we can publish soon. We will also publish. We will hopefully publish the next version in about two months.

You can also write "approved with the following changes" . If the changes are editorial we will not need a new CFC

Note your silence will be considered approval.

once we have approval Alaster will make it into an HTML page on github. Note that editorial changes can still happen after this CFC.

Sections that have changed are:


  *   I have added editors notes about what we =intend to do and removed empty sections
  *   I made a small change to the bulled list in the first section on Usability Testing to address the different types of items included
  *   I added some text to the bulletted list of design theam (on number 8 - Feedback is usable by everyone)
  *   Design requirements  -here I removed most of the content and added an editors note that linked to it and
  *   I then filled in the table based on the wcag proposals short names so that it will make sense, (with an editors note that that will change)
  *   Guidance for policy makers - I tided up this section and wrote a short introduction

Note, I hate having multiple versions of the same content, so the original document<https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit> still has the design requirements / success criteria / items in it that we were working on. We can continue working there. But the content sections that are ready to be published are in the   google doc draft of content to publish<https://docs.google.com/document/d/1eyvLsF_akaSx_6xK5Bx3ylJePN0QJC-6wt42pKolLEE/edit?usp=sharing>. Feel free to add more comments there.



All the best

Lisa Seeman

LinkedIn<http://il.linkedin.com/in/lisaseeman/>, Twitter<https://twitter.com/SeemanLisa>

Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at Second Floor, Mid City Place, 71 High Holborn, London, WC1V 6EA.  The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.