This Wiki page is edited by participants of the Cognitive and Learning Disabilities Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.

Main Page

From Cognitive Accessibility Task Force
Jump to: navigation, search

About This Page

This page is used by the task force to track our current work. To learn more about the task force take a look at our home page, our public list or our work statement. Send us comments at

See our [success criteria proposals for WCAG]. They are based on our [table of user needs ] and how to support them.

We are making a set of questions and answers COGA-FAQ on our [success criteria proposals for WCAG]

For TPAC: Please look at wcag (Monday and Tuesday) , APA (Monday and Tuesday) Also see personalization semantics groups at

Key items


16:30-18:00 at APA
   Publishing Issues Discussion 


11am-12pm APA/CSS Meeting
13:00-14:00 with APA
   COGA Strategies (with AG-WG) 
       COGA-TF in the APA room  and 2pm-3pm APA/Web Platforms Meeting on Editing


Next version of the roadmap - March 2018 Next version of the research - May 2018

We are currently focused on a gap analysis.

We have first drafts of the following accompanying documents: (Note they are works in progress and may change.)

  1. [Table of user needs ] and how to support them
  1. Background research document. Also see the work on phase 2 research
  1. Issue papers on topics such as security, safety and how they are affected by cognitive disabilities. Works in progress are also available at Gap Analysis Issue Papers.
  1. An authoring techniques document.
  1. The techniques will also lead to a proposal for a coga for WCAG 2.1. See our rewording SC
  1. Draft for a semantics for adaptive interfaces (that may become a WAI-ARIA extension) and personalization syntax to enable adaptable interfaces.

Working examples of how this could be used in practice with user preferences are available. This is a project to help personalization for any use - including people with learning and memory issues. It is described more at:

It is made of 4 parts:

  1. JSON files for user setting:
  2. semantics for adaptive interfaces
  3. An HTML page that uses some of the new aria syntax Example of adaptive page
  4. Scripts that a web author can use or include that read the user settings in the JSON files and adapt the page for the user needs example script

Please add any other implementations

Notes from our Face to Face meeting in London FTF issues and agenda,

Terms and Definitions

Open Issues Simple steps for tiding a page for publication see our pre-publication checklist

Current Mandate

Our current mandate is to:

  • Perform a Gap Analysis;
  • create and suggest techniques; and
  • create a roadmap.

What are we working on now?

Right now we are working on the Gap Analysis including an Gap Analysis Introduction (2), a Gap Analysis Table and Gap Analysis Summary off issues and techniques

A module of the Gap Analysis is user research. We are getting it ready for the first working draft. Note that the current draft of user research is on GitHub. You can also see the published draft at

Rewriting the Success Criteria Proposal. See the SC todo list

Also as part of the Gap Analysis we are:

General To do

  • make prescriptive
  • give good descriptions for user agents like Kurzweil 3000?
  • add draft the business case and user needs

todo - next draft of techniques

  • Make dysculcila consistent -done
  • Add techniques for issue papers
  • Review and edit - make prescriptive

todo - next draft of issue papers

  • Add note of what is missing
  • next draft of each paper ..

  • Security and Privacy Technologies -John R
  • Online Safety - Lisa
  • Voice Menu Systems -Debra Dahl
  • Online Payments - Debra Rue and Neil
  • Flat Design - Jamie?
  • User Preferences - Mike and Lisa
  • Add Providing graded help
  • Add Interoperable preference
  • Adaptable Links and Buttons -lisa
  • Personalization
  • Add meta data support
  • Symbols for Non-Verbal - EA
  • Numbers and Math - Tony
  • Web of Things - Jannina
  • Add Attention and distraction - Neil
  • modality -ea

todo - Gap Analisis

  • Make dysculcila consistent
  • Add techniques for issue papers
  • Review and edit

Lower priority for now

Current schedules

Gap analysis 28th January - Freeze content (as an editors draft) to go into a first Working Draft. Aim to publish first Working Draft 1st March

To contain Issue papers, Techniques , Summary

We will then continue reviewing issue papers

1st March 2016: Working Draft of user research module

This and feedback from the proposals will make second editors draft of

1st April 2016: COGA for ARIA (2nd editors draft) 1st April 2016: COGA for WCAG (2nd editors draft)

1st June 2nd Working Draft of the gap analysis and 1st Working Draft of roadmap

1st December Editors draft of the glossary


Materials published by this task force have a lot of citations. W3C has a particular format and tooling for those. While there is a central database of specifications and other publications, most of the citations used by this group are not in that central database. Therefore the task force maintains a separate database of citations. See instructions for creating and using citations.

Key links

Upcoming Work

Gap Analysis Road Map

Key Resolutions

  1. Name officially needs to include LD or CLL
  2. Term needed for "recommendations" in roadmap as "recommendations" is a reserved word in the W3C. (Suggestion: Proposals and/or Principles)
  3. Helping users improving skills is out of scope but useful for outreach
  4. we will use the term 'intellectual disabilities' rather than just use terms such as Down Syndrome or other specific types of intellectual disability
  5. We are avoiding the phrase ICT with other, Web related terms intellectual disability such as Down Syndrome.
  6. We are using the term intellectual disability rather then specific type of
  7. We can resolve small issues on the calls. Larger resolutions need to be approved on our list. We expect people to bring up opposition to resolution within 48 hours.
  8. Criteria by which we decide what research to accept:Due to practical constraints most research will simply be cited and not examined for credibility. However the following cases will rely on task force consensuses before inclusion:
    1. Commercial research that implies the use of a specific proprietary product will be examined for scientific credibility before being included
    2. Research where the task force is aware of contradictory evidence (including anecdotal) will be examined for scientific credibility before being included.

Links for evaluating what scientific research is good (or not):

Open issues

  1. we have discussed a few times changing our name. There is a huge problem with localization.

The task force name should contain LD, but disabilities may be replaced for impairments or challenges.

Other Relevant Links

Other pages of our work

Technologies to review

Also taken from HTML 5 wishlist:

Authors of User group research modules

Volunteer research groups: John Rochford