Gap Analysis Issue Papers
This is a draft page to keep information about the Gap Analysis Issue Papers in one place.
This page may be out of date:
Current drafts
We have so far the following threads
- Web security and privacy technologies issue paper, v. See: 6 http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2014Dec/0001.html
- Voice ML systems. See: http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2014Nov/att-0060/COGAIssuePaperVioceML.html and discussion at http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2014Dec/0018.html
- Online payments: http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2014Nov/0030.html payments]
- Issues with flat design https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Flat_Design
- Safety online: https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2015Jan/att-0045/coga-safety-issue-paper__vers2_.html and updated at safety
- Interoperable symbols for non verbal
- Numbers and the Web
- Web of Things
- preference and adaptability (other then for non verbal)
- Gathering User Preferences https://rawgit.com/w3c/coga/master/issue-papers/preferences.html
- Syntax for adaptable links and buttons https://rawgit.com/w3c/coga/master/issue-papers/links-buttons.html (also see the latest proposal for more ARIA syntax at https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2015Jul/0069.html)
- Providing graded help
- Interoperable preference (word draft - draft 2 on the way)
- adapting content for coga personalization and https://rawgit.com/w3c/coga/master/issue-papers/personalization.html
- meta data support
- Modality issue paper See https://github.com/w3c/coga/blob/master/issue-papers/multi-modal.html
Other suggested issue papers
- Attention and distraction - should we have a user setting at OS level that can stream line the distractions from different apps. how to trun ditistion off with mibile needs to be easy, and back on.
- media-mobility prefrence. I prefer more visio and less text or the other way. I need lowere reading, less numbers
leave for now....
- Identifying when a user needs help
Feel free to add more
We are also need to look at specific topics as mandated in the gap analysis (see https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Gap_Analysis/Introduction)
Use Cases: Addressing specific topics
In the user group research section of the gap analysis, we aim to identify abstract principles for accessibility for people with cognitive and learning disabilities, and core challenges for each user group as well as practical techniques.
However, when trying to identify abstract principles, it is often helpful to look at concrete user scenarios and challenges that different user groups face. For that purpose we have identified the practical and diverse user scenarios that should be considered in user group research. These include:
Communication Making sure users can communicate with people and be part of society. Tasks to investigate:
- Use email and chat effectively
- Being aware of a change
- Share pictures and information
- Play
- Request information
Applications
- Apps to enable work such as document authoring
- Critical DHTML content and applications such as: enroll and manage healthcare, make an appointment, enroll and manage banking, shop online
sign-up / register and manage account profile on a site, book and manage travel
- Enroll in and participate in online education
- Apps such as mobile apps
- Directions / locations
ICT systems
- Use the Web of Things applications such as temperature control, entertainment systems
- Phone menu systems
- Other menu systems
Research and Education
- Understand content and learning material
- Search, research, and find information
- Enroll in and participate in online education
Access to critical information
- Read and share news
- Find weather alerts
- Find and read emergency information
- Find out rites and social service information
We also have the following cross cutting concerns
Using content should be:
- Safe
- Effective
- Minimal frustration