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

Welcome to the WIKI for the Cognitive and Learning Disabilities Accessibility Task Force (COGA)

We are trying to improve Web Accessibility for people with learning and cognitive disabilities.

Do you want to make content usable for people with cognitive and learning disabilities? See our latest draft at

See our 2019 FTF meeting outcomes

What documents do we have?

We are working on documents for research, planning technology for more inclusion, and content with practical advice on what to do

Layer 1. Background Research Documents

This is background level research about the issues and challenges

We have also used the research from Research sources

Layer 2. Gap analysis

road map and gap analysis, (doc).

This is for W3C groups and standard makers looking to understand where the issues lay and how technology could help. It contains:

  • Summary of issues
  • Summary of techniques
  • Roadmap - Tables of user needs and how tech and standards could help
  • We may add challenges from the research module above.

Layer 3. Making it better

Making content usable for people with cognitive and learning disabilities (Content Usable document).Last published version and Editor's working draft

This is for content providers who want to make content more usable for people with cognitive and learning disabilities.

We are currently working on the Design Guide section. For now, this is an Appendix of the Content Usable document but we plan to make it separate stand alone document or web site.

  1. Persona
  2. User needs
  3. User testing
  4. Design Guide - Temporary link:
  5. Guidance for policy makers

You can also look at our [success criteria proposals for WCAG] (or see for our own list). They are based on our [table of user needs ]. These go though different user needs and how to support them.

We also have a page on user need resources to help people understand the user

Drafts in progress include:

If you are in COGA and looking for

  1. design guide as spead sheet :
  2. our priorites :
  3. also see
  4. The mental health issue paper we are working on is at
  5. Terms that will need clarification and to be used consistently are at :


  1. Bots paper drafts /conversational interfaces drafts:
  2. wayfinding issue paper: and ...
  3. conversational interface

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

Send us comments at

Older work include

  1. authoring techniques document,
  2. The techniques also led to a proposal for a coga for WCAG 2.1. See our rewording SC.

Task force work

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.


See the PlanningPage for details out our plan and timelines.

Here are our priorities ...


See Workflows for a descripton of the editorial processes we follow.

Key links

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. An ARIA task force for semantics for adaptive interfaces This should become a WAI-ARIA extension.

Working examples of how this could be used in practice and an HTML page that uses some of the new aria syntax is at Example of adaptive page

  1. 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


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.

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

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