W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

Re: Proposal for moving COGA SC forward

From: lisa.seeman <lisa.seeman@zoho.com>
Date: Sun, 28 May 2017 20:32:21 +0300
To: Gregg C Vanderheiden <greggvan@umd.edu>
Cc: "Alastair Campbell" <acampbell@nomensa.com>, "Michael Cooper" <cooper@w3.org>, "Mike Pluke" <Mike.Pluke@castle-consult.com>, "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
Message-Id: <15c501bd9d6.11a9efdc542304.2024434434320493854@zoho.com>

How about this

Not all items could go into wcag 2.1 because the group did not have time to process at all the success criteria proposed by the cognitive accessibility task force. 

Some items might take considerable  time to do and some members of the working group did not feel that was appropriate  just to accommodate people with cognitive and learning disabilities.

Some items might take time to understand what to do and the group .......

Should I carry on?

All the best

Lisa Seeman

LinkedIn, Twitter

---- On Fri, 26 May 2017 18:21:34 +0300 Gregg C Vanderheiden&lt;greggvan@umd.edu&gt; wrote ---- 

that is a great idea Alastairwith proper intro…

How about something like this 

Best Practice Checklist for the design of content for people with cognitive, language, and learning disabilities.   
(short name   Checklist or  CLL Checklist  )      or some such for a title

(or checklist could be dropped along with checkboxes —and a separate checklist created from it.  I will leave the checklist/checkboxes in for now since they give a good flavor of ‘do them all’ rather than  ‘bunch of options’.  


The following are best practices that have been identified for consideration in designing pages that will possible or easier for people with cognitive, language, and learning disabilities to understand and use.

Not all items can be applied on all web pages, but implementing as many as you can will help users with cognitive, language, and learning disabilities and all are important for some people. 

Some items might conflict with others if applied on a particular web page - but techniques for implementation to avoid conflicts in different applications are being continually developed.  If you think things conflict - see the techniques. If you don’t see a solution - send a note to the working group so it can be examined and new techniques documented.

Not all items in checklist are testable — but much good practice is not testable and the attempt in this document is to capture all of what is know rather than just what is testable or always applicable

These are organized under same general categories as WCAG to facilitate use by those familiar with the WCAG.   Additional guidelines are added where needed to better group the items.   

[We can revisit if this is a good idea after all the CheckList items are gathered. for example if 80 % fall under UNDERSTAND then we might want to re-look at this rather than force an awkward re-distribution.  but if it works - I think this organization would be helpful]

The relevant SC from WCAG are included here so that this list is complete.   
NOTE: the numbering of the Best Practices are NOT the same as the numbering WCAG beyond the GUIDELINE livel.  



 [   ]  Best Practice 1a.   kldfjaldfjaldkfjasldkfjaslfjasd  



[   ]  Best Practice  3a    kajdf;ajdflaksdjflakdjf

[   ]  Best Practice  3x    [WCAG 3.4]   &lt;text of Wcag 3.4&gt;

something like that? 


Gregg C Vanderheiden

On May 25, 2017, at 7:18 PM, Alastair Campbell &lt;acampbell@nomensa.com&gt; wrote:

Michael Cooper wrote:
I've been thinking of the "pillars" as success criteria.... [but] they do indeed look more like guidelines than SC... But the problem with guidelines is, we have to have SC under them.

I think we need things that are specific 'checks' but are not SCs.

So still use Principle &gt; Guideline &gt; [Something]

In old-school usability terms, these would be 'heuristics', which are more about 'appropriateness'  than an SC. But heuristics isn't a very good term, perhaps 'checks'?

Mike, any suggestions from other standards?

For example, Plain language could be framed as something like (and this is off-the-cuff):

[Guideline] Use plain language for important information.

[Check 1] Double negatives are not used to express a positive statement.
[Check 2] Words, phrases or abbreviations that are the most-common form for the concept.

There would be quite a bit of work to re-categorise things, but perhaps less than the current approach.


Received on Sunday, 28 May 2017 17:32:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:49 UTC