@@ -36,7 +36,13 @@
What to Do
36
36
p >
37
37
< p > This can be achieved by:p >
38
38
< ul >
39
+ < li >
40
+ having a single purpose on the page and limit the number of topics per page,
41
+ li >
39
42
< 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 >
40
46
< li >
41
47
clearly differentiating regions using dividing lines, whitespace, and
42
48
background colors,
@@ -60,9 +66,9 @@
What to Do
60
66
< h5 class ="coga-5 "> How it Helpsh5 >
61
67
62
68
< 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
66
72
may not return to pages that are complicated to use and understand.
67
73
p >
68
74
@@ -103,6 +109,11 @@
How it Helps
103
109
easier to process. Examples of common graphical indicators and visual cues
104
110
include:
105
111
p >
112
+ < p > < strong > Navigation areas:strong > Ensure each page has navigation areas that are easy to find.
113
+ Ensure that users know what to expect in each area. It is also important that users know what to ignore.
114
+ Using fewer navigational areas can improve simplicity.
115
+ If you have many navigation regions, ensure they are clear and accessible, so that users are not overwhelmed.
116
+ p >
106
117
< ul >
107
118
< li > grouping summaries of content,li >
108
119
< li > using a card design using colors or white space,li >
@@ -130,6 +141,14 @@
More Details
130
141
The heading structure should create an outline of the document that could
131
142
serve as an abstract of the whole document.
132
143
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 >
133
152
ul >
134
153
< p >
135
154
Icons should be used consistently. It is also important the graphical
@@ -158,6 +177,8 @@
Examples
158
177
< ol >
159
178
< li > Dense text, with little white space.li >
160
179
< 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 >
161
182
< li > Lack of visually differentiated sections.li >
162
183
< li >
163
184
Sections without headings or icons that define sections. For example: A
@@ -169,3 +190,8 @@
Examples
169
190
< li > Groups and page sections that are not logical.li >
170
191
ol >
171
192
section >
193
+ p>
194
+ < strong > Editorial Note:strong > Need review from John K p>
195
+ < section >
196
+
197
+ section >
0 commit comments