Re: Proposal for moving COGA SC forward

the point I made were NOT trying to make WCAG look good.’

they were trying to make the SUPPLEMENT look good — by saying that IT was the place to come for best practice — the place to come if you wanted things to be more accessible
— but also being up front as to how it differed from WCAG

just like the WCAG - right at the front - says what its goals and limitations are — this doc needs to talk about what it is and isnt as well. 


your comment made it look like the supplement was a failure document.   
this is a document for things we ran out of time to put into 2.1
here are things the group didn’t think were appropriate for 2.1 


Instead I was proposing 
this is all our bests advice
it includes what is in 2.1 but goes beyond 
it includes things that are not testable . or not always applicable etc 
etc

but I see what you mean — that my wording is clinical or technical and misses the right tone

how about the following

better? 

g
‘



 TITLE:         Best Practice Checklist for the design of content for people with cognitive, language, and learning disabilities.   (CLL Checklist)  or  ( CLL Best Practices)


Introduction 

This document is a compilation of the best practices for designing pages to make them easier (or possible) to use by people with cognitive, language, and learning disabilities.

This document captures all of the success criteria and advice from WCAG 2.1 but goes beyond.   It also includes things that could not go into WCAG 2.1 because they are not strictly testable, or may not be applicable on all pages.  But all are important to individuals with one or another cognitive, language, and learning disability . 

  
The Best Practice Items 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.   The relevant Success Criteria from WCAG are included here so that this list is complete.   However the numbering of the Best Practices are NOT the same as the numbering WCAG beyond the GUIDELINE level to avoid confusion between the Best Practices and the WCAG 
[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]




PERCEIVABLE 


 GUIDELINE 1.1:  Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. 


[   ]  Best Practice 1.1a.   [ WCAG 1.1.1 Non-text Content:]  All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. 
Rationale:   Making sure all content is in machine readable form ensures that it can be easily re-presented in different forms visually and auditorily as well as being translated into different languages and language levels. 

[   ]  Best Practice 1.1b
Rationale: 


OPERABLE 




UNDERSTANDABLE 


 GUIDELINE 1 

[   ]  Best Practice  3a    kajdf;ajdflaksdjflakdjf

[   ]  Best Practice  3x    [WCAG 3.4]   <text of Wcag 3.4>










g 

Gregg C Vanderheiden
greggvan@umd.edu




> On May 29, 2017, at 1:27 PM, lisa.seeman <lisa.seeman@zoho.com> wrote:
> 
> Hi Gregg
> The point I was trying to make is that we will need an introduction that serves the needs of people with disabilities . That needs to be our main focus. I felt the points you had proposed was trying to make wcag look good and down played the usefulness of the supplement.
> 
> That main point of the supplement must be to achieve accessibility for people with cognitive disabilities as much as possible. If not I think it will just be counter productive and controversial 
> 
> 
> 
> All the best
> 
> Lisa Seeman
> 
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter <https://twitter.com/SeemanLisa>
> 
> 
> 
> 
> ---- On Sun, 28 May 2017 20:38:02 +0300 Gregg C Vanderheiden<greggvan@umd.edu> wrote ----
> 
> I think you want the supplement to be something that always exists — and includes all the items IN 2.0 and 2.1 and all the other as well. 
> 
> The MASTER collection of ideas — not bounded by testability.    
> So all of the things that are IN 2.1 would ALSO be in this document.    
> 
> So those sentences would not make sense. 
> 
> PS  (I think they would just make the Working group look lazy or it make it look like  2.1 is being released before it is ready.)    But mostly — those sentences don’t work because what is in 2.1 should also be in this doc so it is complete.  
> 
> 
> g 
> 
> Gregg C Vanderheiden
> greggvan@umd.edu <mailto:greggvan@umd.edu>
> 
> 
> 
> 
> On May 28, 2017, at 1:32 PM, lisa.seeman <lisa.seeman@zoho.com <mailto:lisa.seeman@zoho.com>> wrote:
> 
> 
> 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 <http://il.linkedin.com/in/lisaseeman/>, Twitter <https://twitter.com/SeemanLisa>
> 
> 
> 
> 
> ---- On Fri, 26 May 2017 18:21:34 +0300 Gregg C Vanderheiden<greggvan@umd.edu <mailto:greggvan@umd.edu>> wrote ---- 
> that is a great idea Alastair
> with 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’.  
> 
> 
> Introduction 
> 
> 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.  
> 
> 
> PERCEIVABLE 
> 
> GUIDELINE 1:  
> 
>  [   ]  Best Practice 1a.   kldfjaldfjaldkfjasldkfjaslfjasd  
> 
> 
> 
> UNDERSTANDABLE 
> 
> GUIDELINE 
> 
> [   ]  Best Practice  3a    kajdf;ajdflaksdjflakdjf
> 
> [   ]  Best Practice  3x    [WCAG 3.4]   <text of Wcag 3.4>
> 
> 
> 
> something like that? 
> 
> 
> 
> g 
> 
> Gregg C Vanderheiden
>  <mailto:greggvan@umd.edu>greggvan@umd.edu <mailto:greggvan@umd.edu>
> 
> 
> 
> 
> On May 25, 2017, at 7:18 PM, Alastair Campbell <acampbell@nomensa.com <mailto:acampbell@nomensa.com>> 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 > Guideline > [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.
> 
> Cheers,
> 
> -Alastair
> 
> 
> 
> 
>