Open Issues

From Cognitive Accessibility Task Force

This page is for issues that we do not want to forget, but can not yet address.


    • if there are standard semantics for extra instuction and help are they easy to find via the operating system
  • can symbol users use capture in sc

Bots confirm the issue paper covers the follwing

  • Can people in coga use groups use voice menus were they need to say the right words
  • Can people in coga use groups use chat bots , asking for help, losing context, making mistakes, need to write the right words

Sematics context sensitive information such as location that centigrade and meshumants and time are local for the user and it's also worth pointing out that there are also location sensitive events ("remind me to do x when I get home", for example)

personalizing a reminder could include setting a type (e.g. personal, work, family) types user can say the or define of reminder, office, curial how how they are handled

  • Emotions ml, maybe this is a question of where we require it. but this can be done automaticaly.

and emojies but they have cultural . should this a user agent or an auther burden? Also is this effective? (bounce of jamie, and do a mock up page)

  • graded help, IoT, distractions?
  • make sure when we reuire information such as instuctions, we know how to give it theat the auther ca get it

user needs

  • Table 2:restoring context, let me know what i am doing in general turns and the specifics of what I just did.
  • Table 3: Entering data, i need to know what data is needed (clear simple, unabigues and possibly with a picture of how to find it). Also i need them to identify mistakes. I need them to make it easy to enter the data correctly
  • recognizing emotions and sarcasm - solutions can be find at also see Microsoft Project Oxford for automated solutions. solution could fill it in an automated way and author can edit

old open issues

  • issue paper on supporting appropriate user behavior
  • correlating out terms and the who and ccd
  • Look at c6, c7, c9 and c10 (maybe c8) of apip where reserch is from and how it is used
  • Ask gotfreid if we can review urc

Aria proposal

  • how long do you need for time outs
  • importance is subjective, should aria importance be called that? (James Crage and Mike P.) See Resolution: find a better name (if we can) but keep the idea
  • importance - Also critical links should be included even if they are less often used.
  • testing for personlization - can we make it robust and reasonable (James) Resolution: we will recommend to make edge cases for what are allowed personalization criteria with test suit for them. add adaptions that are robust should be enbeled.
  • use @rel in place of aria-desitnation (James) Resolution: doubel check if it is aproiate - if so go for it
  • use HTML alternative in place of hasalternative (as above)
  • rda for context such as mens products

WCAG proposal

  • Imortance - TD talked to a web developers about this, and there was a discussion over advertisements, as well as the revenue generators versus the highest traffic


  1. keep a visual focus to help orientate the user and help them focus (Rich)
  2. provide text for speech (like auto transcript) so that users can recap what happened if focuc was lost (Rich)


  1. Api for speech feedback
  2. Are all web payments and billing techniques included?
  3. How to make multi media more understandable

To do items to consider

  1. Worked examples and before and after examples
  2. Business case
  3. FAQ's of questions we will get over and over...
  4. Emotional disabilities
  5. assessment - how to add support without giving an unfair example

FAQ's of questions we will get over and over

  1. Q you can not make all content usable for all people with all cognitive disabilities
    1. A We define inaccessible as follows: if a disabled user could use content, but can not because of the the design choices of the author, then that content is not accessible.