w3c/wbs-design
or
by mail to sysreq
.
The results of this questionnaire are available to anybody.
This questionnaire was open from 2017-12-06 to 2017-12-31.
3 answers have been received.
Jump to results for question:
Look at the understanding section for identify common purpose (was purpose of controls). Does it give the "what, why and how" for the success criteria.
What would you add?Responder | Personlization 1 |
---|---|
Lisa Seeman-Horwitz | need to add tabe were we say for each item on the list what specification supports it. add example pages? |
John Rochford | "understanding section ..." link is a #404 |
Mark Wilcock | Error 404: Not Found - Therefore cannot comment on this resource. |
Look at the understanding section for identify contextual-information. Does it give the "what, why and how" for the success criteria.
What would you add?Responder | Personlization 2 |
---|---|
Lisa Seeman-Horwitz | need more examples on how to meet it add use case were symbols are the natrial language of the user translations do not work |
John Rochford | Suggestion: Consider "enable" instead of "allow" because "allow" implies permission. Yes, what, why, and how are given. Nothing to add. |
Mark Wilcock | Yes, what, why and how are covered. Additional examples could prove beneficial, possibly of a visual nature. |
Look at the understanding section for timouts (min). Does it give the "what, why and how" for the success criteria.
What would you add?Responder | timeouts |
---|---|
Lisa Seeman-Horwitz | 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 |
John Rochford | Yes, what, why, and how are given. Nothing to add. |
Mark Wilcock | Yes, what, why and how are covered. Additional clarification when timeouts should be displayed to the user, preferably once at the beginning of that task/process. |
Look at the understanding section for interruptions. Does it give the "what, why and how" for the success criteria.
What would you add?Responder | interruptions |
---|---|
Lisa Seeman-Horwitz | |
John Rochford | Yes, what, why, and how are given. Nothing to add. |
Mark Wilcock | Yes, what, why and how are covered. Error 404 for "COGA Techniques" link. Techniques sections could be expanded. |
Look at the understanding section for accessible authentication. Does it give the "what, why and how" for the success criteria.
What would you add?Responder | accessible authentication |
---|---|
Lisa Seeman-Horwitz | we can make this better by including the answers and information on the wcag list discusions. 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 |
John Rochford | There are significant grammatical problems that make the understanding doc difficult to understand. I will fix them. The SC needs a revision. |
Mark Wilcock | Yes, what, why and how are covered. The wording is slightly confusing, compared to that of the other understanding sections. |
The following persons have not answered the questionnaire:
Send an email to all the non-responders.
Compact view of the results / list of email addresses of the responders
WBS home / Questionnaires / WG questionnaires / Answer this questionnaire
w3c/wbs-design
or
by mail to sysreq
.