W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > October 2017

how to make inclusive content / roadmap

From: lisa.seeman <lisa.seeman@zoho.com>
Date: Mon, 30 Oct 2017 15:38:53 +0200
To: "public-cognitive-a11y-tf" <public-cognitive-a11y-tf@w3.org>
Message-Id: <15f6d7fcb0d.129d107153412.3125860897597754299@zoho.com>
Hi Folks

I added our SC to the "how to make inclusive content / roadmap" document


https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#heading=h.dri688yftf4


I realized as I was adding them that, as we wrote them for WCAG, then are not easy to read. But now we do not have the same testability requirements - we can make them easier to read.


So  I added a short sentence that is easy to read for each one and then put the link to the SC under "technical details"


I think we need to add an example and two informal techniques for each one so people know what we are talking about. I did it for the first one. (see Make the purpose of each page clear )
Does that look OK?


Can anyone volunteer to help out with this? Also, please check if the short sentences represent the success criteria.

All the best

Lisa Seeman

LinkedIn, Twitter
Received on Monday, 30 October 2017 13:39:20 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:59 UTC