The task force for learning and cognitive disabilities has published an updated version of our roadmap and gap analysis. We would love to hear your comments. It is a long document and we know it can be hard to find your way around it. (We are working on that and hope it will be easier in the ne

It is a long document and we know it can be hard to find your way around it. (We are working on that and hope it will be easier in the next version). In the meantime here are some sections of particular interest

1, The Appendix on how to make content usable for people with learning and cognitive disabilities. This section contains a section with practical advice and content developers may prefer to start here. We hope it will also meet the needs of web developers, content creators and policy makers.

2. The is also a Summary of Issue Papers that addresses some of the issues that people with learning and cognitive disabilities face, such as problems with logging on, safety, voice menu systems, and many other topics. This may be useful for anyone trying to gain more understanding of the topic.

3.There is a section with Tables of User Needs that identify the different needs of the community and proposes suggestions on how standards and technology could be developed to meet these needs. This may be useful for standards groups and policy makers.

We realise there is still a lot to do, but would appreciate your feedback and comments as we move forward. Please send you comments to public-coga-comments@w3.org (subscribe, archives). Thanks and all the best

https://docs.google.com/document/d/1mZakGwwp92Yyem4e5KW6C5fGsv0Q9aqA8Mk9rEF6nlY/edit#

https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#

<kirkwood> design requirments document (above)

<kirkwood> sorry i’ll call in i can hear you

https://w3c.github.io/personalization-semantics/#modules

example of wayfinding

Use short sentences and lines (Mark)

(Technical details:On coga github: chunks.html

wcag issue 24

https://github.com/w3c/wcag21/pull/90)

Use clear spacing (Mark)

(Technical details:Use clear spacing between letters, words , sentences lines, pargraphes and blocks of text. Text is not fully justified and On coga github: isual-presentation.html

wcag issue 51

PR number 113)

Use clear text and voice (Mark)

(Technical details:

On coga github: clear-text-and-voice.html

wcag issue 27

Do not use serif fonts)

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: janina Mark_Wilcock Roy LisaSeemanKestenbaum kirkwood
Regrets: E.A._Draffan John_Rochford Alasrair
No ScribeNick specified.  Guessing ScribeNick: LisaSeemanKestenbaum
Inferring Scribes: LisaSeemanKestenbaum

WARNING: No "Topic:" lines found.


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)