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

Re: pattens review 2: objective 3 and 4

From: Steve Lee <stevelee@w3.org>
Date: Tue, 14 May 2019 13:46:24 +0100
To: public-cognitive-a11y-tf@w3.org
Message-ID: <6b23ffde-9eba-aae3-df78-f2b53b612ae4@w3.org>
On 12/05/2019 19:41, lisa.seeman wrote:
> Here is my review of objective 3 and 4. See
> https://raw.githack.com/w3c/coga/design-doc-transfer/design/index.html#objective-help-the-user-find-what-they-need

[snip]

> *3.3 *
> change"
> Key content such as:
> 
> Interactions for critical features (e.g login forms)
> Important information (e.g health warnings)
> Must visually stand out and be visible to users without needing to 
> scroll the page."
> 
> to
> "
> Key content must visually stand out and be visible to users without 
> needing to scroll the page. This included:
> 
> Interactions for critical features (e.g login forms, send butons )
> Important information (e.g health warnings or information that can 
> affect safety)"

This included -> This includes
butons-> buttons

> 
> how it helps: add example
> 
> For example, An elementary school publishes a weekly newsletter with 
> interesting stories about activities and important announcements. 
> Important announcements include early school dismissal. If the 
> newsletter has a good heading structure, it will be easier for a parent 
> who is a slow reader to find the important announcements about early 
> school dismissal. This important information about early dismissal 
> information can be easily missed.
> 
> In another example, a user is writing a comment, but the send button is 
> not visible when the view focuses on the text area. As a result she can 
> not see how to send her feedback. The company will then not receive any 
> feedback from groups who are not able to find the feedback button.
> 
> 
> *3.4*
> 
> "Search: Provide a search capability."
> 
> change to:
> "Provide a search capability."
> 
> 
> 
> *3.5* change:
> 
> I would like to add another example to the how it helps section:
> 
> "A user is watching a video. they try to increase the volume  but  touch 
> a different link instead. A new video now loads. The user can press the 
> back button and return to the video they were watching before. They now 
> know they can try and increase the volume and if they make a mistake, 
> they can easily go back and try again.
> 
> In another example, the back button did not worked as expected, but 
> took  them somewhere else (such as the home page). When they try to 
> change the volume or add a comment they often lose the video they were 
> watching and can not find the way to get back to it. They now feel they 
> can not use any of the features of the website in case they lose their 
> main content again. They do not use larger screen, change the volume, or 
> leave comments.
> 

+1

I often find the back button just does nothing - maybe make this an 
example or new failure example


Steve
Received on Tuesday, 14 May 2019 12:46:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 May 2019 12:46:28 UTC