W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > September 2018

Re: Easy Reading Summary & Abstract of Cognitive Accessibility Roadmap and Gap Analysis

From: Glenda Sims <glenda.sims@deque.com>
Date: Thu, 13 Sep 2018 11:25:24 -0500
Message-ID: <CAH2ngET7MWcN3V9_T82fYUSAdu1BepiDmEZG_yQZaaRqSzCo5w@mail.gmail.com>
To: Alastair Campbell <acampbell@nomensa.com>
Cc: "McSorley, Jan" <jan.mcsorley@pearson.com>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
+1 to this latest version of the summary.

P.S.  I have a few minor suggestions for edits.  None of these changes need
to be made...I like it as is.  But if I were the lead editor, I would say:

This document is for people who make web standards and policies. It focuses
on the state of accessibility for people with learning and cognitive
disabilities when using the Web.



This document provides:


   - A summary of issues,
      - Ways to address the issues (techniques),
      - A list of unmet user needs,
      - Suggested ways technology may meet these needs in the future.



For advice for people making web content  see "Making content usable for
people with cognitive and learning disabilities
<https://rawgit.com/w3c/coga/new-titles-and-intros/gap-analysis/index.html#a-appendix-making-content-usable-for-people-with-cognitive-and-learning-disabilities>
".



*glenda sims* <glenda.sims@deque.com>, cpacc
<http://www.accessibilityassociation.org/certification>   | team a11y lead
| 512.963.3773

        deque systems <http://www.deque.com>  accessibility for good

On Thu, Sep 13, 2018 at 10:23 AM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi Jan & everyone,
>
>
>
> I applied JohnK’s comment about the first paragraph and put the links into
> the abstract, and I’ve coped that below for reference.
>
>
>
> Also, can we move the “it builds on” bit to the last paragraph? It doesn’t
> seem as important, and then all the ‘dense’ information is at the end of
> the abstract.
>
>
>
> Jan, you mentioned some improvements to the bullet-points during the call
> but we didn’t have time to talk about that, can we do that over email?
>
>
>
> I did remove some of the ones from JohnR’s version, but mainly because
> we’ve remove the appendix (e.g. with policy guidance), so obviously we
> don’t want to include things which aren’t in the doc!
>
>
>
> I’m also wondering which way around this should be:
>
>    1. Techniques (ways) to address the issues
>    2. Ways to address the issues (Techniques)
>
>
>
> The second reads better to me, but maybe that’s just me?
>
>
>
> Cheers,
>
>
>
> -Alastair
>
>
>
> Current version from the google doc:
>
> ---------------------
>
> This document is for people who make web standards and policies. It
> focuses on the state of accessibility for people with learning and
> cognitive disabilities when using the Web.
>
>
>
> This document provides:
>
>    - A summary of issues,
>    - Techniques (ways) to address the issues,
>    - A list of unmet user needs,
>    - Suggested ways technologies may meet these needs in the future.
>
>
>
> For advice for people making web content  see "Making content usable for
> people with cognitive and learning disabilities
> <https://rawgit.com/w3c/coga/new-titles-and-intros/gap-analysis/index.html#a-appendix-making-content-usable-for-people-with-cognitive-and-learning-disabilities>
> ".
>
>
>
> This document builds on the Cognitive Accessibility User Research
> <https://rawgit.com/w3c/coga/new-titles-and-intros/gap-analysis/index.html#bib-coga-user-research>
> and Cognitive Accessibility Issue Papers
> <https://w3c.github.io/coga/issue-papers/>. It is produced by the Cognitive
> and Learning Disabilities Accessibility Task Force
> <http://www.w3.org/WAI/PF/cognitive-a11y-tf/> (COGA TF), a joint task
> force of the Accessible Platform Architectures Working Group
> <http://www.w3.org/WAI/APA/>(APA WG) and the Accessibility Guidelines
> Working Group <http://www.w3.org/WAI/GL/> (AG WG) of the Web
> Accessibility Initiative <http://www.w3.org/WAI/>.
>
>
Received on Thursday, 13 September 2018 16:25:49 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 13 September 2018 16:25:49 UTC