comments from the SC from the COGA TF on the understanding sections.

Hi folks

I have been gathering comments from the SC  from the COGA TF on the understanding sections.


SO far we have:


1. Look at the  understanding section for identify common purpose 

need to add tabe were we say for each item on the list what specification supports it. 
add example pages?


 2.  understanding section for identify contextual-information. need more examples on how to meet it
add use case were symbols are the natrial language of the user
translations do not work Suggestion: Consider "enable" instead of "allow" because "allow" implies permission


3. Look at the  understanding section for timouts (min). 
need user example to stress that many people can not finish the task,often start things that they can not finish in the time, and therefor lose confidence in using the web.
 
 idealy you keep the user data and make it so that the user can start and finish a task.this includeds the aging and disabilities. however in cases where you can not do that at least warn them before thet start to reduce the fusttration.
 warnings mid-process are a fail. a warning should be given one time , before the user starts a process or task not at each step
Additional clarification when timeouts should be displayed to the user, preferably once at the beginning of that task/process.




4. Look at the  understanding section for accessible authentication.


we can make this better by including the answers and information on the wcag list discussions.
 
 this includeds:
 stressing that a useable alternitive is suffient
 the user is alowed to pay for extra equiment such as a dongle
 diffrent aprouches that may become allowed 
 conformence to the web-authification is a prefered technque
There are significant grammatical problems that make the understanding doc difficult to understand.
The wording is slightly confusing, compared to that of the other understanding sections.


All the best

Lisa Seeman

LinkedIn, Twitter