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.
- 1 Welcome to the WIKI for the Cognitive and Learning Disabilities Accessibility Task Force (COGA)
- 2 What documents do we have?
- 3 Task force work
- 4 Planning
- 5 Workflows
- 6 Key links
- 7 Citations
- 8 Key Resolutions
- 9 Open issues
- 10 Other Relevant Links
- 11 Other pages of our work
- 12 Technologies to review
- 13 Authors of User group research modules
- 14 Reports
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 https://www.w3.org/TR/coga-usable
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
- Research doc contains: Research by disability (latest draft: https://w3c.github.io/coga/user-research/)
- Issue papers (docs) on topics such as security, safety and how they are affected by cognitive disabilities. (Works in progress are also at https://github.com/w3c/coga/tree/master/issue-papers and https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4919553/)
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
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.
- User needs
- User testing
- Design Guide - Temporary link: https://w3c.github.io/coga/design/
- Guidance for policy makers
You can also look at our [success criteria proposals for WCAG] (or see https://rawgit.com/w3c/coga/master/extension/status.html 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
- design guide as spead sheet :https://docs.google.com/spreadsheets/d/1Rt51xg57oZW56mfTw_t33T9zlPDOV7o4Za6veCCqDtI/edit#gid=0
- our priorites : https://docs.google.com/spreadsheets/d/1YH4YETBmAdhfL9p8FK5ATUiXDGibeJh66psQCSUAvLQ/edit#gid=0
- also see https://www.designpatternsformentalhealth.org/
- The mental health issue paper we are working on is at https://docs.google.com/document/d/1G9SJSiAT-SYDVNxBfwOe7A6VPqsmX4Ua0QT7-NrfQTA/edit?usp=sharing
- Terms that will need clarification and to be used consistently are at : https://docs.google.com/spreadsheets/d/1lWTTYjzoCDx6goBCMH7pI72nsuIGu35JDu1hYGlyCwY/edit#gid=0
- Bots paper drafts /conversational interfaces drafts:
- wayfinding issue paper:https://github.com/w3c/coga/blob/master/issue-papers/wayfinding-indoors.html and ...
- conversational interface https://docs.google.com/document/d/1B1vCqlU1IF5UmqxhJAy8Khdi-kRQNPalVX8f3lCMr7w/edit#heading=h.9j8rnhzb9sv8
Send us comments at firstname.lastname@example.org.
Older work include
- authoring techniques document,
- The techniques also led to a proposal for a coga for WCAG 2.1. See our rewording SC.
Task force work
See the PlanningPage for details out our plan and timelines.
Here are our priorities ...https://docs.google.com/spreadsheets/d/1YH4YETBmAdhfL9p8FK5ATUiXDGibeJh66psQCSUAvLQ/edit?usp=sharing
See Workflows for a descripton of the editorial processes we follow.
- Research sources
- We are currently focused on a gap analysis and roadmap.
- making inclusive content for coga (an appendix for the roadmap )- https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit# (Feb 2018)
- Issue papers -
- voice/converational interfaces https://docs.google.com/document/d/1B1vCqlU1IF5UmqxhJAy8Khdi-kRQNPalVX8f3lCMr7w/edit# (Feb 2018)
- wayfinding (Feb 2018)
- research module on stress anxiety and depression
- methodology for gap analysis
- Issues log
- Good practices and avoid bad practices
We have first drafts of the following accompanying documents: (Note they are works in progress and may change.)
- [Table of user needs ] and how to support them
- 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.
- 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
- 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.
- Identifying known and proposed techniques. If you want to add a technique use the technique template.
- Identifying specific issues that effect our users and need special consideration. A collection of these issue papers is at: Gap Analysis Issue Papers and at github at https://rawgit.com/w3c/coga/master/issue-papers/index.html . Also see the issue paper template.
- Specification for Easy Personalization and Personalization criteria and Providing graded help
- Name officially needs to include LD or CLL
- Term needed for "recommendations" in roadmap as "recommendations" is a reserved word in the W3C. (Suggestion: Proposals and/or Principles)
- Helping users improving skills is out of scope but useful for outreach
- we will use the term 'intellectual disabilities' rather than just use terms such as Down Syndrome or other specific types of intellectual disability
- We are avoiding the phrase ICT with other, Web related terms intellectual disability such as Down Syndrome.
- We are using the term intellectual disability rather then specific type of
- 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.
- 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:
- Commercial research that implies the use of a specific proprietary product will be examined for scientific credibility before being included
- 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): http://www.reportbd.com/articles/57/1/Criteria-Qualities-of-Good-Scientific-Research/Page1.html
- 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
- Assistive technologies such as AAC and AAC core vocabularies
- Reading techs
- Adaptive technologies for learning
- APIP and IMS
- Daisy and epub
- Fluid and FLOE
- Voice ML and menu systems
- Web Security (Including CAPTCHA)
- WebRTC (real time communications)
- Fluid and Floe
- Debra Dahl
- Text Simplification
Also taken from HTML 5 wishlist:
- Full Transcript
- John Foliot is interested in exploring this.
- Media Descriptions
- John Foliot.
- Date UI Widgets
- Input type numeric
- Emotion Markup
- Debra Dahl
- Haptic Output
- Referencing UAAG
- Web Payments
- Footnotes, End notes, Annotations, Definitions
- ePub, ARIA
- Real Time Chat
- John Foliot
Authors of User group research modules
- Communication Difficulties and Disorders including non-vocal: Joshue O Connor Deborah Dahl, Avi Gloden and E.A. Draffan (Prev: Kinshuk)
- Dyslexia: Lisa Seeman
- ADD / ADHD: Neil Milliken, Jim Smith, Susann Keohane and Mary Jo Mueller (Prev: Barry Johnson, Katherine Mancuso, and Michel Fitos )
- Down Syndrome: John Foliot, Kate Dieble, Debra Ruh
- Aging and Dementia:Katie Haritos-Shea, Mary Jo Mueller, Neil Milliken and Susann Keohane(Prev:Elle Waters)
- Autism: John Rochford, Neil Milliken
- Dyscalculia: Neil Milliken.
Volunteer research groups: John Rochford