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

pattens review 2: objective 3 and 4

From: lisa.seeman <lisa.seeman@zoho.com>
Date: Sun, 12 May 2019 21:41:57 +0300
To: "public-cognitive-a11y-tf" <public-cognitive-a11y-tf@w3.org>
Message-Id: <16aad58274b.1285ca9a4359409.1192025401592959993@zoho.com>
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



I am just focusing on the first sentence and trying to make them a bit easier or more consistent.



please give any comments in the next two days



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)"





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:

"Let the user return to a previous point without undoing their work.



The standard back button is the best way to do this as it is familiar to the user and this might be the way they will try first. The user should never lose their work if they try pressing back"



to

"Always let the user return to a previous point.



The standard back button is the best way to do this as it is familiar to the user and this might be the way they will try first.



The user should never lose their work if they press back."





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.







4.3 clear words - first text:  this does not need to be bullet points



Failure example: Using new words - remove this example as the picture is missing





4.4

remove " Success example: Plain text with definition of terms.



4.6.5

Success example: non-literal text  - this should be



failure example : non-literal text



4.8.2

Failure example: separate each step  (2nd example)

should be

Failure example: do not separate each step



4.9



before bullet points add



"Use short blocks of text: "



4.11.3

add exmples from the "more details" section to the example sections





4.12.3 and 4.12.5 remove empty sections



-------



All the best

Lisa Seeman

http://il.linkedin.com/in/lisaseeman/, https://twitter.com/SeemanLisa
Received on Sunday, 12 May 2019 18:42:28 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 12 May 2019 18:42:29 UTC