W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > May 2019

Re: 3rd review of the design guided. . objective 4 until the end!

From: Roy Ran <ran@w3.org>
Date: Sun, 19 May 2019 23:37:19 +0800
To: public-cognitive-a11y-tf@w3.org
Message-ID: <807374b9-3349-ce6f-3dd6-e4047ffa3f47@w3.org>
Hi Lisa,

Thank you for your review, I will add all of those 3 times review into 
main doc as soon.

Best,

Roy

在 2019/5/17 下午11:02, lisa.seeman 写道:
> third review of 
> https://raw.githack.com/w3c/coga/design-doc-transfer/design/index.html#pattern-provide-help-with-directions
>
> please submit any comments by the end of Monday.
>
> *General comments*
>
> The links to old versions are gone. we must compare to older versions
> Heading levels of failure examples need to be fixed
>
>
> *pattern 5.3 *
> *change*
> "Pattern: Build forms so that people make less mistakes
>
> Input errors should be automatic corrected (where the
> correction is reliable) if suggestions for corrections are
> known, the suggestions are provided to the user
>
> In a text field, accept as many formats as possible. For
> example accept different formats of phone numbers and correct
> Input errors automatically
> Use an interface were only valid input can be selected
> Accept voice prompts for people with a speech impairment
> Use the default format of the users location such as currency
> and temperature
> Use autocomplete and personalization of form controls"
>
> *to*
>
> Pattern: Design forms so that people make less mistakes
>
> Choose a form design that reduces the  chance that the user
> will make a mistake. This includes:
>
> - In a text field, accept as many formats as possible. For
> example accept different formats of phone numbers and correct
> Input errors automatically
> -Use an interface were only valid input can be selected
> -Use autocomplete and personalization of form controls
> -Accept voice prompts when supported by the operating system
> -When possible input errors should be automatic corrected
> (where the correction is reliable)
> -If suggestions for corrections are known, the suggestions are
> provided to the user
> "
>
> add an editors note: items may be moved to 5.6
>
> how it helps
> remove:
> " Image of options being restricted to valid inputs
>
> Autocomplete"
>
>
> *pattern 5.4 *
> change"
> Allow the user to check their work before submitting a form so
> that they can correct any mistakes.Once they have fixed their
> mistake it should be easy to get back to the place they were at
> (without redoing extra steps)."
>
> *to*
> "Always allow the user to check their work and  correct any
> mistakes.
> Once the user has fixed their mistake it should be easy to get
> back to the place they were at without redoing additional
> steps.
>
> *pattern 5.5*
> change "Provide clear instructions up front when appropriate that
> is clear, concise, and accessible. Ensure labels are also
> clear."
>
> *to*
> "Provide clear labels and instructions that are:
> -before the field or activity
> -clear, concise, and accessible.
> "
>
> how it helps:
>
> change "Clear instructions help prevent user errors up front. "
> to "Clear instructions help prevent user errors"
>
> change "people new to culture" to "people from a diffrent
> culture"
>
> *pattern 5.6*
>
>
> change editors note to read: this pattern will be reviewed with 5.3 to
> remove any overlap
>
> *pattern *5.7
> I think we can remove the ed not. the standard similar when  compared 
> to the others.
>
> remove"
>
> For situations where the absence of a timed event would
> significantly change the intended functionality of an
> application (e.g., an auction or another real-time event), it
> is important to ensure that users with disabilities are
> properly notified. Notifications should include information
> about timed events, and an indication of the duration of the
> time given. As well, they should include mechanisms clearly
> labelled to adjust, extend, or stop the duration of an event,
> to allow users to fully engage and interact with Web content
> and functionality. For example, if an e-commerce Web site's
> checkout process provides secure credit card transactions, the
> user is notified of the timeout, and is given at least 120
> seconds to extend it. .... Remove intill end of "how it helps!
> untill "This pattern helps people with a variety of
> disabilities including the following:"
>
> *add to more details*
> "For situations where the absence of a timed event would
> significantly change the intended functionality of an
> application (e.g., an auction or another real-time event), it
> is important to ensure that users with disabilities are
> properly notified. "
>
> delete empty sections
>
> add success example:
> "A Web site with sensitive information uses a client-side time
> limit to help protect users who may step away from their
> computers. After a period of inactivity, the Web page asks if
> the user needs more time. If the user does not respond within
> 120 seconds, a timeout occurs. However when the user logs in again all 
> the work is back.
>
> A website  only  times out when sensitive information is given (such as
> the users credit card information).  The sensitive
> information is asked for at the last stage of the process. The user is 
> warned that once they give the cedit card information they should 
> complete th process quickly as the session can time out. After a
> period of inactivity, the Web page asks the user to press any key for 
> more time. If the user does not respond within 120 seconds, a
> timeout occurs. However when the user comes back and logs-in again
> all the content is back.
>
> 5.9 delete empty bullet points and >
>
> 5.10
>
> delete ed note and empty marks
>
> >
>
> add to: Success examples
>
> "
> the user can set to change the rout if more then a specific
> amount of time is saved. They can add more information such as  how 
> many  extra turns
> are acceptable for saving 5 minuets. When a new rout is find that save 
> time the user is asked if they want to change rout, how many extra 
> turns re added and how much time will be saved. The user can go back 
> to the original
> rout in one touch or command."
>
>
> *pattern 5.11*
>
> change:
> Checking how safety and security techniques work with a wide
> range of customized profile including aging, learning and
> cognitive disabilities.
> Using known techniques to keep sensitive user information safe.
> Ensuring all users understand known risk.
>
> *to:*
>
> "Checking how safety and security techniques work with a wide
> range of customized profile including aging users and users
> with learning and cognitive disabilities.
> Using known techniques to keep sensitive user information safe.
> Help all users understand any relevant known risks."
>
>
> *pattern 6.3*
>
> change:
> "If you can not avoid them, make an easy way to delay and
> control interruptions and changes in content, unless they are
> started by the user or involve an emergency.
> "
> *to:*
> "when possible , avoid interruptions
>
> If you can not avoid them, make an easy way to
> control interruptions and changes in content, unless they are
> started by the user or involve an emergency."
>
>
> *pattern *6.4
> Provide users with less than five choices on each screen. This
> can be a simplified version or have extra choices linked from
> clear and descriptive titles.
>
> *to*
> "
> Provide users with  five or less choices on each screen and
> remove unnecessary content.
>
> Extra links that do not relate to the main purpose of the page
> should be limited to the footer section. Extra choices can also
> be provided using clear and descriptive titles.
>
> This can be provided via a simplified version alternative that
> is generated in real time from the same code base as the main
> content.
>
> "
> **pattern **7.4
> change:
> "Let people easily reach an operator without going through
> multiple steps."
>
> to
> "Let people easily reach an operator without:
>
> -memorizing character strings, including remembering digits to
> select for a short time, or pin numbers
> -perform calculations, or
> -coping; or
> -using their executive function to work out the category of the
> service they need;
> -going through multiple steps.
> "
>
> *remove ed note *(you cna add it as an issue if you want!
>
> *change*:
> "Allowing the 0 digit to get to a person, or having the first
> option "to weight for an person who can help you press 0" can
> consistently help"
>
> *to* "
>
> The 0 digit  should be reserved for reaching a person.
> Consistently set the first option for each menu to: "to weight for an 
> person who
> can help you press 0". This can help everyone reach the
> support they need."
>
> change"Not important systems might only use the design
> requirement bellow (XX)
>
> "
>
> to  "Unimportant systems, that do not affect the users health,
> safety, money or rights, could only use pattern 7.5"
>
> 7.5
> change "Each step in a sequential process must contain the
> information necessary to allow a user to proceed (and so must
> not rely on memory from prior steps, and would benefit from a
> summary of info, or a mechanism for traversing the process."
> to
> "Each step in a sequential process must contain the information
> necessary to allow a user to proceed. They must rely on memory
> from prior steps. When useful, provide  a summary of information
> from previous steps, and a mechanism for traversing the
> process.
>
> remove: "Not important systems might only use the design
> requirement bellow (XX)"
>
>
> add the acronym tag to VUI (voice user interfaces)
>
> add ed note : we intend to review this pattern with 7.4 to
> check for overlaps
>
>
> *Theme 8.*
> The user testing and user stories were meant to merge
> with the new material not just replace it! please also add the
> old user testing and user stories.
>
> *pattern 8.3*
> change"Provide explanatory content for complex information and
> tasks, especially if it is important for successful completion
> of a task."
> *to*
> "Content is provided that helps users understand complex
> information"
>
> *add* the following to "getting started"
>
> "Provide explanatory content for complex information that is
> important for successful completion of a task including tasks
> in the real world."
>
>
> move the content from "more details" to the end of "how it helps"
>
> In the more details section copy over the text from
> https://w3c.github.io/coga/design/#provide-help-for-complex-
> information for:
>
> Sufficient techniques for content relating to numbers and
> complex information. (use whichever apply)
>
> and
> Sufficient techniques for content with more than 300 words
>
> *pattern 8.4*
> change
> "Help is provided help with navigational systems and directions."
> to
> "Content is provided that helps users understand directions and 
> navigational systems.:
>
> The content in more details should be added to the "how it helps" section
>
> Remove " Extra help with these ensures navigational systems and 
> directions can easily be used without constant reminders being needed. 
> Especially if it built in directly to the system or directions."
>
>
> "Consider using sing any standard mechanism "  should be "Consider 
> using any standard mechanism "
>
> Heading levels of failure examples need to be fixed
>
>
>
> *pattern 8.5*
>
> change "Provide help for any complex forms, particularly when
> there are multiple steps, unusual interactions or non-standard
> controls."
>
> *to*
> "Provide help for any complex forms, particularly when there
> are multiple steps, unusual interactions, non-standard controls
> and required feilds that do not support autocomplete.
>
> *Add* to the end of the "how it helps" section
>
> "Many standard forms controls provide support automatically. For 
> example, many fields  can be automatically fill it all in the 
> information using autocomplete or personlization semantics. Then the 
> user will not make mistakes filling it out.
>
>
> When you require additional fields and non standard controls many 
> users will have difficulty filling it in. Many users with disabilities 
> will get the information incorrect or be unable to work out how to 
> complete the task. Often this results in the task being completely 
> abandoned. In other cases the user asks a care giver for help to 
> complete the form or work the control. In either case they have not 
> been able to complete the task because of their disability."
>
>
>
> In the "More Details" section
> -delete empty bullet
> -change "Brand new controls like date pickers" to "custom controls 
> like date pickers"
> - add the Sufficient techniques from 8.3.3  at
> https://w3c.github.io/coga/design/#provide-help-for-forms-and-
> non-standard-controls
> -add to the Sufficient techniques : "adding advice to any controls 
> that are not complaint with  "html 5 autocomplete". "
>
> heading levels of failure examples need to be fixed
>
> Technical details
> add
> On coga github: help.html
> wcag issue 32
> pull request 118
> (frem m https://w3c.github.io/coga/design/#technical-details-29)
>
>
>
> (this pattern should be reviewd again when all these changes are made)
>
>
> *pattern 8.6*
>
> move the content of the  "more detail" to the section "how it helps" above
>
> add to success examples
> -A phone number, ideally with a feature to automatically call via an 
> interoperable Voice over IP specification.
> - An email link using the ‘mailto’ protocol with prefilled “to” and 
> “subject” fields. Note will not work on all platforms or depending of 
> the users mail client
>
> *pattern 8.7*
>
> 8.7.1 How it helps
> remove the bullet formatting (the content should not be in bullets)
>
> remove the ed note
>
> *objective 8*
>
> add the first few sections (introduction, user stories and user 
> testing) from the google docs from 
> https://docs.google.com/document/d/1aJE2C0FzzzXgydEp0MNGSdDDvUTTsANViUVvciFK36k/edit#heading=h.hj3ovfr7yhr6
>
> (
>
> 9.3
>
> remove editors note
> remove empty bullet point
> remove "/" at end of bullet point
> change the to the Sufficient techniques on failure examples
>
>
> remove the content and the heading "The Internet of Things (IoT) and 
> the Web of things."
>
> add to more details the content from 
> https://w3c.github.io/coga/design/#how-it-helps-42 until the section 
> The Internet of Things (IoT)"
> and add to the more details
> "
> Exceptions:
>
> -When there is a security or safety requirement, these API's may be 
> disabled for the relevant field
> -If it breaks the main function of the site, such as evaluation and 
> testing applications
> "
>
> *pattern 9.4*
> add full stop at end of second bullet point
>
> in "more detail" remove empty bullet
>
> add technical references from
> https://w3c.github.io/coga/design/#technical-references-3
>
>
> *pattern *9.5
>
> the spacing in the example stops them from making sense
> remove "Example taken from adaptable ui personalisation.
> aui-action="compose"
> A page working with autocorrect" . leave the rest of the text.
>
> Add "install a personlization tool bar"
>
> copy technical details from  the google doc at 
> https://docs.google.com/document/d/1aJE2C0FzzzXgydEp0MNGSdDDvUTTsANViUVvciFK36k/edit#heading=h.qf7qfrl7znc4
>
Received on Sunday, 19 May 2019 15:37:32 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:03 UTC