Skip to content

Commit 87cf606

Browse files
authored
Merge pull request #360 from w3c/MH_Proposals
Mh proposals
2 parents c9e27f0 + f9409bf commit 87cf606

File tree

7 files changed

+266
-62
lines changed

7 files changed

+266
-62
lines changed

content-usable/index.html

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -949,6 +949,7 @@

Design Guide

949949
<section data-include="../design-guide/o2p04-page-important.html">section>
950950
<section data-include="../design-guide/o2p05-chunked-media.html">section>
951951
<section data-include="../design-guide/o2p06-search.html">section>
952+
<section data-include="../design-guide/o1p08-clear-start.html">section>
952953
section>
953954

954955
<section class="objective-3">

design-guide/o1p05-clear-controls.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@
What to Do
5555
<li>
5656
Ensuring items that are not clickable do not look like links or controls.
5757
li>
58-
ul>
58+
ul>
5959
<p>
6060
When this is not possible, provide instructions that explain how to use the
6161
control. Instructions should be on the same page or one click away and
@@ -110,6 +110,7 @@
How it Helps
110110
the controls, regardless of how a user uses the page (vision, auditory,
111111
voice input).
112112
p>
113+
113114
section>
114115
<section>
115116
<h5 class="coga-5">Getting Startedh5>
@@ -126,7 +127,6 @@
Getting Started
126127
<a>cognitive and learning disabilitiesa>.
127128
p>
128129
section>
129-
130130
<section>
131131
<h5 class="coga-5">Examplesh5>
132132
<p><span class="use">span><strong>Use:strong>p>
@@ -141,7 +141,7 @@
Examples
141141
standard user actions and make it clear when they are pressed.
142142
li>
143143
<li>Tabs that look like tabs and make it clear when they are selected.li>
144-
ol>
144+
ol>
145145

146146
<p><span class="avoid">span><strong>Avoid:strong>p>
147147

design-guide/o1p08-clear-start.html

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
<h3>Make it easy to go directly to the home page (Pattern)h3>
2+
<pre class="yaml remove">
3+
title: Make it easy to go directly to the home page
4+
ref: ${{ FILENAME_REF }}
5+
github: ${{ GITHUB_INFO }}
6+
sidebar:
7+
sections:
8+
- name: User Story
9+
items: "Placeholder"
10+
- name: Personas
11+
items: "Placeholder"
12+
pre>
13+
<p class="ednote">This pattern is new, editorial review is needed.p>
14+
<section>
15+
<h5 class="coga-5">User Needh5>
16+
<blockquote>
17+
<p>
18+
I need it to be easy to go to the home page when I get lost or disoriented.
19+
p>
20+
blockquote>
21+
<p>
22+
Related User Story:
23+
<a href="#Placeholder" aria-label="Placeholder"
24+
>Placeholdera>.
25+
p>
26+
<p class="ednote">"Placeholder" needs to be replaced by real content in the section Related User Story [and also in corresponding
27+
Code/Include].p>
28+
section>
29+
<section class="wtd">
30+
<h5 class="coga-5">What to Doh5>
31+
<p>
32+
Make it easy to go directly to the home page of a site, subsite or app.
33+
To help users find the links to home page(s) on each screen, use:
34+
p>
35+
<ul>
36+
<li>a predictable location,li>
37+
<li>large sizes fonts and icons,li>
38+
<li>strong color contrast, andli>
39+
<li>appealing icons or logos.li>
40+
ul>
41+
<p>
42+
Note the home page is sometimes referred to as the main screen (in an app) or
43+
landing page of a set of screens or Web pages.
44+
p>
45+
<p>
46+
This guidance also applies to home pages for subsites and sections of the site.
47+
For example, each department of a university may have its own home page.
48+
In such a case, make it easy to go to the homepage of both the site and the subsite that the user is currently on.
49+
p>
50+
section>
51+
<section>
52+
<h5 class="coga-5">How it Helpsh5>
53+
<p>
54+
People who have cognitive and learning disabilities often get lost and disoriented when using apps and websites.
55+
This is often aggravated by stress, mental health and/or cognitive overload.
56+
Providing an easily identifiable starting point helps users know that they
57+
can always restart if they become disoriented or lost.
58+
p>
59+
<p>
60+
Making links to home page(s) more visible and recognizable provides a more efficient
61+
way for people with cognitive disabilities to reorient themselves
62+
and complete their intended tasks.
63+
p>
64+
<p>
65+
For example, a user with a cognitive and learning disabilities navigates a wrong path during a search attempt
66+
or gets lost while exploring a website. If a home page link and logo are easily identifiable,
67+
the user can directly go to the home page. It assures them that they can restart anytime if lost.
68+
They don't need to press the back button multiple times. This helps them restart their browsing task quickly.
69+
It prevents the negative impact on their efficiency that may be caused by reading
70+
every page on the way back to the home page.
71+
p>
72+
section>
73+
<section>
74+
<h5 class="coga-5">Examplesh5>
75+
<p><span class="use">span><strong>Use:strong>p>
76+
<ul>
77+
<li>
78+
Clearly visible link to the home page with
79+
<ul>
80+
<li>recognizable icon,li>
81+
<li>strong color contrast,li>
82+
<li>large font and icons andli>
83+
<li>predictable location, such as the top left corner for a link to the home page.li>
84+
ul>
85+
li>
86+
<li>
87+
Breadcrumb that includes the link to the home page.
88+
li>
89+
ul>
90+
<p><span class="avoid">span><strong>Avoid:strong>p>
91+
<ul>
92+
<li>Not providing a link to the home page of the site or app.li>
93+
<li>Not providing a link to the subsite that the user is now on.li>
94+
<li>Placing home page links in an inconsistent location, making it difficult for users to find.li>
95+
<li>Using small, low-contrast, or unclear icons or text labels that are hard for users to recognize as a home link.li>
96+
ul>
97+
section>

design-guide/o2p03-page-structure.html

Lines changed: 29 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@

Use a Clear and Understandable Page Structure (Pattern)

1010
- name: Personas
1111
items: "Alison, Amy, Gopal, Kwame, Maria, Sam"
1212
pre>
13-
13+
<p class="ednote">This pattern has been changed, editorial review is needed.p>
1414
<section>
1515
<h5 class="coga-5">User Needh5>
1616
<blockquote>
@@ -36,7 +36,13 @@
What to Do
3636
p>
3737
<p>This can be achieved by:p>
3838
<ul>
39+
<li>
40+
having a single purpose on the page and limit the number of topics per page,
41+
li>
3942
<li>organizing the page content into logical sections,li>
43+
<li>
44+
limiting the number of navigation areas that group links related to a specific topic (such as related resources),
45+
li>
4046
<li>
4147
clearly differentiating regions using dividing lines, whitespace, and
4248
background colors,
@@ -60,9 +66,9 @@
What to Do
6066
<h5 class="coga-5">How it Helpsh5>
6167

6268
<p>
63-
People with <a>cognitive and learning disabilitiesa> may not be able to
64-
use content and applications when the page structure and relationships are
65-
unclear. The user may not complete tasks and miss key information. The user
69+
People with <a>cognitive and learning disabilitiesa> and/or SMI (Severe Mental Illness)
70+
may not be able to use content and applications when the page structure and relationships are
71+
unclear or overwhelming. The user may not complete tasks and miss key information. The user
6672
may not return to pages that are complicated to use and understand.
6773
p>
6874

@@ -112,6 +118,11 @@
How it Helps
112118
speech bubbles.
113119
li>
114120
ul>
121+
<p><strong>Navigation areas: strong>Ensure each page has navigation areas that are easy to find.
122+
Ensure that users know what to expect in each area. It is also important that users know what to ignore.
123+
Using fewer navigational areas can improve simplicity.
124+
If you have many navigation regions, ensure they are clear and accessible, so that users are not overwhelmed.
125+
p>
115126
section>
116127
<section>
117128
<h5 class="coga-5">More Detailsh5>
@@ -130,6 +141,14 @@
More Details
130141
The heading structure should create an outline of the document that could
131142
serve as an abstract of the whole document.
132143
li>
144+
<li>
145+
If you have five or more landmarks, check if they are all needed.
146+
Ensure the landmark names are clear and describe their purpose.
147+
It helps all users, including screen reader users, know what to expect in each section.
148+
Make sure the accessible labels for landmarks are easy to understand.
149+
They can be non-visible, but they still need to be clear
150+
(for example, names like "primary," "secondary," and "tertiary" may not make sense).
151+
li>
133152
ul>
134153
<p>
135154
Icons should be used consistently. It is also important the graphical
@@ -158,6 +177,8 @@
Examples
158177
<ol>
159178
<li>Dense text, with little white space.li>
160179
<li>Unclear page structure and hierarchy.li>
180+
<li>Too many navigational areas that feel confusing and overwhelming.li>
181+
<li>Unclear relationship between links in navigational areas.li>
161182
<li>Lack of visually differentiated sections.li>
162183
<li>
163184
Sections without headings or icons that define sections. For example: A
@@ -169,3 +190,7 @@
Examples
169190
<li>Groups and page sections that are not logical.li>
170191
ol>
171192
section>
193+
<section>
194+
<p class="ednote">This needs further review (By John K). p>
195+
section>
196+

design-guide/o2p06-search.html

Lines changed: 85 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@

Provide Search (Pattern)

1010
- name: Personas
1111
items: "Kwame"
1212
pre>
13-
13+
<p class="ednote">This pattern has been changed, editorial review is needed.p>
1414
<section>
1515
<h5 class="coga-5">User Needh5>
1616
<blockquote>
@@ -25,49 +25,77 @@
User Need
2525
section>
2626
<section class="wtd">
2727
<h5 class="coga-5">What to Doh5>
28-
<p>Provide a friendly search capability. Ideally search should include:p>
28+
<p>Provide user friendly search to your app or website. Ideally, search should include:p>
2929
<ul>
30+
<li>Assistance to start a search, such as:
31+
<ul>
3032
<li>autocomplete,li>
31-
<li>grouping of results when appropriate with headings for each group,li>
32-
<li>ability to easily find previous searches, andli>
33-
<li>spell-checking.li>
33+
<li>ability to easily find previous searches,li>
34+
<li>spell-check, andli>
35+
<li>allowing variations of search terms. For example: Caps or no caps, singular or plural forms, acronyms, or similar terms.li>
36+
ul>
37+
li>
38+
<li>Support for finding useful results (findability), such as:
39+
<ul>
40+
<li>grouping results when appropriate, with headings for each group,li>
41+
<li>useful labels and descriptions for each result,li>
42+
<li>filters to refine users’ search queries, when appropriate, li>
43+
<li>Boolean search operators and modifiers, and explain how to use them, andli>
44+
<li>ability to customize the number and presentation of links in search results.li>
45+
ul>
46+
li>
47+
<li>Reliable search
48+
<ul>
49+
<li>Test the search function with real users. Make sure the search works reliably,
50+
and finds results that match users' intent for common searches.li>
51+
ul>
52+
li>
3453
ul>
3554
section>
3655
<section>
3756
<h5 class="coga-5">How it Helpsh5>
3857
<p>
39-
Having a search capability allows users to find the content they need even
40-
if they cannot use the site menus. A user can learn how to use search and
41-
reuse that skill on many sites.
58+
Having a search capability allows users to find the content they need, even if
59+
they cannot use the site menus. Many users can not manage menu systems for a
60+
variety of reasons. For example, menu systems and most site navigation require
61+
the user to understand the menu categories. Some users may be unable to
62+
identify the correct categories. However, many users learn how to use search and reuse
63+
that skill on many sites.
4264
p>
4365
<p>
44-
Menu systems and most site navigation require the user to understand the
45-
menu categories. Users with impaired <a>executive functiona> may be unable
46-
to identify the correct categories.
66+
Search is most useful when it makes it easier for users to find what they are looking for.
67+
At the input level, this includes correcting misspellings or suggesting auto-corrected versions
68+
of the search terms. Accepting variations of search terms benefits many people,
69+
including people with language impairments, dyslexia, or a memory impairment.
4770
p>
4871
<p>
49-
In some cases, users know the correct category via memory, rather than
50-
logic. For example, most users remember that the print function is often
51-
found under the file menu. Users with impaired memory may not be able to
52-
find these menu items based on recall.
72+
Allowing users to narrow their search prevents them from getting inundated with irrelevant results.
73+
This is especially important for slow readers with impaired memory or users who get easily overwhelmed.
5374
p>
5475
<p>
55-
Users with impaired short-term memory, <a>age related forgetfulnessa>, or
56-
who are easily distracted may also find navigating a site and going to many
57-
pages to look for content difficult. If it takes too long they may lose
58-
focus and forget what they are looking for.
76+
The next step is helping users easily find useful results. Users with impaired short-term memory, <a>age related forgetfulnessa>,
77+
or who are easily distracted may find it difficult to navigate a site and look through many results.
78+
If it takes too long, they may lose focus and forget what they are looking for.
79+
A busy page of search results containing long lists of links can also be overwhelming.
80+
For example, people with obsessive-compulsive disorder (OCD) sometimes feel a need to open and check every result,
81+
even when most of them are not useful.
5982
p>
6083
<p>
61-
Search is most useful when it corrects misspellings, finds appropriate or
62-
related content, and provides suggested auto-corrected versions of the
63-
search terms.
84+
It helps if search results are presented under headings and categories. Advanced search options and
85+
search filters also offer users greater control over search queries, making it easier to find
86+
the right information. Customization can also make it easier for users to recognize the correct
87+
search result and avoid becoming overwhelmed. For example, it may allow the user to set the
88+
number of links and modify their presentation in search results.
6489
p>
90+
Finally, make sure that search options function reliably, consistently, and as expected.
91+
<p>
6592
<p>
66-
If there are many results from related topics, it helps if search results
67-
are presented under the appropriate heading and categories. This helps the
68-
user find the search results they are looking for.
93+
Errors and frustration can worsen anxiety, which in turn reduces overall cognitive function.
94+
This means that by the time the user finds the page or task they are looking for,
95+
they are less likely to be able to complete it. Making the process of finding the right content
96+
easier will help them complete the task.
6997
p>
70-
section>
98+
section>
7199
<section>
72100
<h5 class="coga-5">More Detailsh5>
73101
<p>
@@ -79,13 +107,40 @@
More Details
79107
<h5 class="coga-5">Examplesh5>
80108
<p><span class="use">span><strong>Use:strong>p>
81109
<ol>
82-
<li>Search with spell check or suggested terms.li>
110+
<li>Search that forgives or corrects spelling mistakes and allows similar terms such as acronyms or related terms.
111+
For example:
112+
<ul>
113+
<li>The user asks for information about “adhd” but uses lowercase.
114+
Information about ADHD, ADD, AD(H)D, and attention-related disabilities were also included in the results. li>
115+
ul>
116+
li>
117+
<li>Search that helps the user narrow the results to the most useful. For example:
118+
<ul>
119+
<li>A supermarket supports searching for chocolate by providing filters to reduce
120+
the search results such as vegan, gluten-free, sugar-free, etc. li>
121+
<li>The supermarket allows users to add Boolean terms, such as “chocolate and syrup.”
122+
The site makes it easy to find instructions on how to use these terms to narrow your search.li>
123+
<li>Search results are presented under specific headings that make it easier to find the relevant results. li>
124+
ul>
125+
li>
126+
<li>Personalization so that the users can customize the number and presentation of links in search results.li>
127+
<li>Search that has successful user testing with people with learning and cognitive disabilities find it easy to find the correct content.
128+
li>
83129
ol>
84130
<p><span class="avoid">span><strong>Avoid:strong>p>
85131
<ol>
86-
<li>
87-
Search that presents many results that are not grouped or ordered by their
88-
relationship to the original request.
132+
<li>Search that overwhelms the user with results that are not what they are looking for. For example:
133+
<ul>
134+
<li>A search has lots of results but the user has no way to filter them.li>
135+
ul>
136+
li>
137+
<li>Search that is not flexible and does not correct mistakes. For example:
138+
<ul>
139+
<li>The search does not support similar terms or incorrect spelling li>
140+
ul>
141+
li>
142+
<li>Search that does not have useful labels or descriptions for each search result.
143+
The user has to open the results to know if they are relevant.
89144
li>
90145
ol>
91146
section>

0 commit comments

Comments
 (0)