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

patterns review 1: general comments and the first objective

From: lisa.seeman <lisa.seeman@zoho.com>
Date: Sun, 12 May 2019 19:03:04 +0300
To: "public-cognitive-a11y-tf" <public-cognitive-a11y-tf@w3.org>
Message-Id: <16aacc6a1c0.e7cc8f7f356482.3610698092814003037@zoho.com>
Hi Folks



here is my review of the first section of the patterns document at https://raw.githack.com/w3c/coga/design-doc-transfer/design/index.html#pattern-make-it-clear-what-are-controls-and-how-they-should-be-used

fortunately this section is the longest



I also have some general comments.



please give any objections in the next two days.



.......


general comments

1 "use literal language" is twice 



2. Technical details - should all have the same heading and the same opening sentence



IE

start with the sentence from the template: “The following are proposals for WCAG. They experiment with more testable language”




3. remove any empty examples



4. make a todo list of items to add in the next draft (such as missing examples)



Comments on objective 1



2.2 Make Each Step Clear - simplify first sentence and add paragraph mark 





from

In a multistep process, clearly indicate the steps completed, the current step and the steps pending. Ensure the user can quickly determine the current location and progress within a sequence.



to

In a multistep process, clearly indicate the steps completed, the current step and the steps pending.



Make sure the current location and progress within a sequence is clear.





2.5 Use graphical indicators to help people identify when items that are associated with each other or have a different purpose to surrounding information.



change to



Use graphical indicators to help people identify

- items that are associated with each other or

- items that have a different purpose to surrounding information

- key terms and critical information.





The rest can be moved to the how it helps or more details sections.



Also we can add them to the examples as that section is empty and we need at least one.





2.6 Long pieces of media are divided into logical segments with a description of each segment.



change to:



Long pieces of media are divided into logical segments that are:

 -short

 -labelled

 -easy to reach or jump to.





2.7 Make the purpose of each section clear. Often this involves providing clear headings that briefly defines the purpose of each section. Extraneous information that is not directly relevant to the main purpose of a page should be distinctly separated and programmatically determinable.



change to:


"Make the purpose of each section clear. Often this involves providing clear headings that briefly defines the purpose of each section.



content that is not directly relevant to the main purpose of a page should be distinctly separated and programmatically determinable."





how it helps:  add sentence : " sometimes symbols (with alt text) can be used  to make the sections purpose clear."





examples: most of the examples are todo notes- add example from wai home page





2.8

add bullet point

"items that are not clickable do not look like links or controls" 



how it helps  The example in the "how it helps" section is missing 

add : For example, An older user with age appropriate forgetfulness takes longer to learn new designs. They go to an eCommerce site has boxes around the headers (such as "womens" or "sale") and simple large text for the "add to cart" button.  They click on the headings and not on the add to cart. After a few failures they assume they can not manage it and leave the site.





examples - the text "In the example below" should be removed



Technical Resources and History - should be consitent with other sections



2.9

Add editors note that this pattern may be merged with 2.6



add to the bullted list the sentence "

Avoiding multiple scrolling areas/regions in a page will also help.  " (and delete it from below)



2.10

Add editors note that this pattern may be merged with 2.6 or the differences clarified





2.11

Users should be able to easily identify that there are sub-menu items and how to get to them.





change to



Users should be able to easily identify:

- that there are sub-menus  and

-how to reach sub-menu items.



2.12 

​change pattern name and move the name to be the text under the name. (right now there is no pattern text)





IE:



Pattern:  Sub-menu items are logical



Sub-menu items are clearly associated with the main menu items under which they fall





2.13 add editors note: we intend to remove aspects from this pattern that are repeated in 2.8 or merge the two patterns





2.14 Use a consistent visual design with a stable look and feel.



change to

Use a consistent visual design  groups of pages.





the "how it helps section" needs a rewrite. including adding the example. for now lets add before the bullet points



" For example, An older user with age appropriate forgetfulness takes a long time to learn new designs. When they come to a site the first page takes time to understand, but then they know what to do on the next screen. If the next screen is also difficult to learn, they become tiered and make more mistakes, as they move to a third page the cognitive load becomes to much and they  can not complete the task.



All the best

Lisa Seeman

http://il.linkedin.com/in/lisaseeman/, https://twitter.com/SeemanLisa
Received on Sunday, 12 May 2019 16:03:37 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 12 May 2019 16:03:38 UTC