-
Notifications
You must be signed in to change notification settings - Fork 18
/
Copy pathuser-needs-coverage.html
280 lines (275 loc) · 16.5 KB
/
user-needs-coverage.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
<h1>Low Vision User Needs Coverage</h1>
<p>This page analyzes low vision user needs coverage:</p>
<ul>
<li>In WCAG 2.1</li>
<li>Potentially for 2.2</li>
<li>Possible for Silver</li>
<li>Responsibility in content authoring, browser, OS</li>
</ul>
<p><strong><em>Note: </em>Do not change the wording in the first column, since it is taken directly from the <a href-"https://www.w3.org/TR/low-vision-needs/">User Needs/Requirements draft</a>. If you suggest different wording, add it in [brackets] to the first column <strong>or</strong> in the last column "Thoughts".</strong></p>
<table width="100%" border="1" cellpadding="7">
<tr valign="top" align="left">
<th scope="col">User Needs - with links to relevant User Need document section</th>
<th scope="col"><p>Author/Browser/OS<br>
A, B, O<br>
What can authors do to not interfere with these needs? </p></th>
<th scope="col">WCAG 2.1<br>
Success Criteria</th>
<th scope="col">WCAG 2.2</th>
<th scope="col">Silver</th>
<th scope="col">References, Resources, Thoughts, etc.</th>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#proximity-of-related-information">Proximity of Related Information</a>: </strong>Users know about and can find related information.</p></td>
<td>A</td>
<td> </td>
<td>x</td>
<td> </td>
<td>Perhaps a joint COGA - LVTF SC. when page reflows related information is separated. Need to find examples in the wild. How to keep programatically associated information in close proximity when page is zoomed, or viewport changes size. <p>example: large input control (50 characters) label of 'Name' on left edge. 'Required' is aligned on the right. huge amount of white space between. if using screen magnifier info on right is lost. If attention not directed to the right... info is easy to miss. (was in the US gov style guide. it has since been corrected.)<br>
also, Mobile overlap perhaps a use case. Non-responsive sites are an issue.</td>
</tr> <tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#justification">Justification</a>:</strong> Users can change the justification / alignment (left, right, full/both, centered) of blocks of text.</p></td>
<td>B - user CSS, possible UI setting</td>
<td> </td>
<td>x - ??Authors don't use full justification. We have the research to back this up.</td>
<td> </td>
<td>@@Laura I suspect that a justification / alignment SC would not be accepted in 2.2 and would be pushed to Silver.<br>JF thinks it would be easy to add "don't use full justification" as an SC for authors.</td>
</tr> <tr valign="top" align="left">
<td><strong>Visual affordance</strong> - focus and controls</td>
<td> </td>
<td> </td>
<td>x</td>
<td> </td>
<td>perhaps split 1.4.11 into UI and graphics. Focus on requirements for accessible visual affordance of user interface <a href="https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_(Minimum)">User Interface Component Contrast (Minimum)</a>. States are critical. Detlev - functional state (visited/unvisitied) transitional/transactional (checked/unchecked). component should maintain contrast between states. adjacent color applies to current state at current moment (not across states). different states do not need to contrast with each other. visited and non-visited are not adjacent so not covered. So only the visited and non-visited states as they stand on their own are covered. check in the checkbox is a graphical object - you have to be able to see the check. </td>
</tr>
<tr valign="top" align="left">
<td><strong>Page Refresh</strong> - an aspect of Point of Regard. When new information is added to a page [content update/injection or page refresh] maintain focus at current location (do not move focus to top page as it disorients user and workflow).</td>
<td> </td>
<td> </td>
<td>x</td>
<td> </td>
<td>This seems more of a failure technique for 2.2.4 - interrupting workflow on a page</td>
</tr>
<tr valign="top" align="left">
<td><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#brightness-overall">Brightness</a>: </strong>Users can set the overall brightness of a display.</td>
<td><p>B - media players</p>
<p>O - brightness setting</p></td>
<td> </td>
<td> </td>
<td>X</td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#text-contrast">Contrast</a>: </strong>Users can set the background color and the text color from the full color spectrum.</p></td>
<td><p>B - override forground/background in browser settings. User CSS. </p>
<p>O - forground/background color of application</p></td>
<td><p>1.4.11 Non-Text Contrast</p>
<p>1.4.8 Visual Presentation</p></td>
<td> </td>
<td>X</td>
<td>@@Jim - Exception for browser default.</td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#maintain-point-of-regard">Point of Regard</a>: </strong>The point of regard remains visible within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed.</p></td>
<td>B</td>
<td> </td>
<td> </td>
<td>X</td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#using-user-settings">User Settings</a>: </strong>Content picks up all relevant user settings, such as ... [Draft Note: The Task Force plans to add additional information here.]</p></td>
<td>B - possible UI setting. Should inherit OS settings </td>
<td> </td>
<td> </td>
<td>X</td>
<td>@@Laura I suspect that a user settings SC would not be accepted in 2.2 and would be pushed to Silver.</td>
</tr>
<tr valign="top" align="left">
<td><a href="https://www.w3.org/2016/03/09-lvtf-minutes.html#resolution01">[RESOLUTION</a>: add User Need: <strong>Users can see and operate all interface elements that are intended for users to see and operate. This includes when users have changed display settings such as text size, magnification, and cursor</strong>.
(9 March 2016)]</td>
<td> </td>
<td> </td>
<td> </td>
<td>X</td>
<td>@@Laura LVTF pushed the title attribute/tooltip obscured under the screen magnifier's large cursor issue to Silver. Resources:<br>
<ul><li><a href="https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/index.php?title=User_stories_-_use_cases&oldid=752#Size_Limitations">Use Case</a>: TAGLINE: Difficulty reading tooltips for icons, which are obscured under the screen magnifier's large cursor</li>
<li><a href="https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/index.php?title=Metadata_On_Hover&direction=prev&oldid=2450">Wiki page with title attribute evidence</a> (28 November 2016)</li>
<li><a href="https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Mar/0032.html">Email:</a> Obscuring active elements and text email </li>
<li><a href="https://w3c.github.io/low-vision-a11y-tf/requirements.html#seeing-all-interface-elements">User need 7.1 Seeing All Interface Element</a>s (Draft Note: Possible figure to be added: hover hand obscures important tooltip text)</li>
<li><a href="https://www.w3.org/2016/03/09-lvtf-minutes.html#resolution01">RESOLUTION</a>: add User Need: Users can see and operate all interface elements that are intended for users to see and operate. This includes when users have changed display settings such as text size, magnification, and cursor.
(9 March 2016)</li>
</ul></td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#not-relying-on-color">Color</a>: </strong>Color is not the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.</p></td>
<td> </td>
<td>1.4.1 Use of Color</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#rewrap-for-one-direction-scrolling">Rewrap</a>: </strong>Blocks of text rewrap so that only one direction of scrolling is needed, e.g., for left-right and right-left scripts (languages), usually vertical scrolling and not horizontal scrolling.</p></td>
<td> </td>
<td>1.4.10 Reflow</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#reflow-to-single-column">Reflow</a>: </strong>Users can set blocks of text in one continuous block, instead of in multiple columns.</p></td>
<td> </td>
<td>1.4.10 Reflow</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#line-length">Line Length</a>: </strong>Users can set the line length for blocks of text. Often the easiest way to do this (for developers, designers, and users) is for users to resize text areas and the text rewraps to change the line length.</p></td>
<td> </td>
<td>1.4.10 Reflow</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#hyphenation">Hyphenation</a>: </strong>Users can turn hyphenation on or off.</p></td>
<td><p>B - user CSS, possible UI setting</p></td>
<td> </td>
<td> </td>
<td> </td>
<td>@@Laura I suspect that a hyphenation SC would not be accepted in 2.2 and would be pushed to Silver.</td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#text-size">Text Size</a>: </strong>Users can change the text size (font size) of all text, without zooming the entire interface.</p></td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>@@Jim - zoom is adequate for text and text in vector images. There are issues with raster images. Also, Huge issues with Tooltips. </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#font">Font</a>:</strong> Users can change the font face (also called font family or typeface) of all text, choosing from a wide range of fonts including sans serif and serif fonts.</p></td>
<td>B - user CSS, possible UI setting</td>
<td> </td>
<td> </td>
<td> </td>
<td>@@Laura I suspect that a font SC would not be accepted in 2.2 and would be pushed to Silver.</td>
</tr>
<tr valign="top" align="left">
<td><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#style">Style</a>:</strong> Users can change the text style (underline, italic, bold) of blocks of text.</td>
<td>B - user CSS, possible UI setting</td>
<td> </td>
<td> </td>
<td> </td>
<td>@@Laura I suspect that a style SC would not be accepted in 2.2 and would be pushed to Silver.</td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#capitalization">Capitalization</a>: </strong>Users can change the capitalization (all capital letters, small capital letters, sentence style) of blocks of text.</p></td>
<td>B - user CSS, possible UI setting</td>
<td> </td>
<td> </td>
<td> </td>
<td>@@Laura I suspect that a capitalization SC would not be accepted in 2.2 and would be pushed to Silver.</td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#size-of-all-elements">Size of All Elements</a>: </strong>Users can change the size of all elements.</p></td>
<td> </td>
<td>1.4.4 Resize Text</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#line-spacing">Line Spacing</a>: </strong>Users can change the line spacing (leading) for blocks of text.</p></td>
<td> </td>
<td>1.4.12 Text Spacing</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#letter-spacing">Letter Spacing</a>: </strong>Users can change the letter spacing (space between letters/characters) of blocks of text.</p></td>
<td> </td>
<td>1.4.12 Text Spacing</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#word-spacing">Word Spacing</a>: </strong>Users can change the word spacing (space between words) of blocks of text.</p></td>
<td> </td>
<td>1.4.12 Text Spacing</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#margins-and-borders">Margins and Borders</a>: </strong>Users can change the margins (blank space) and borders (including color, width, style) around blocks of text.</p></td>
<td>B - user CSS, possible UI setting</td>
<td> </td>
<td> </td>
<td> </td>
<td>@@Laura I suspect that a margins /borders SC would not be accepted in 2.2 and would be pushed to Silver.</td>
</tr>
<tr valign="top" align="left">
<td><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#spacing-between-elements">Spacing Between Elements</a>:</strong> Spacing groups related elements and separates less related elements.</td>
<td> </td>
<td>1.4.12 Text Spacing</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#element-level-customization">Element-level Customization</a>: </strong>Users can customize text differently for specific elements, such as headings, lists, paragraphs, links, <strong>, <em>, <cite>, etc.<br>
Users can set at least:</p>
<ul>
<li>Text size</li>
<li>Text color and background color</li>
<li>Font</li>
<li>Text style (that is, turn on or off underline, italic, bold)</li>
<li>Line spacing</li>
<li>Margins</li>
<li>Borders — including border line color, width, style</li>
</ul></td>
<td>B - user CSS</td>
<td> </td>
<td> </td>
<td> </td>
<td>@@Jim some covered in 1.4.12.</td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#seeing-all-interface-elements">All Elements</a>:</strong> Users can see all interface elements that are intended for users to see, including when users have changed display settings such as text size.</p></td>
<td><p>B</p>
<p>O </p></td>
<td> </td>
<td> </td>
<td> </td>
<td>@@Laura I suspect that an all interface elements SC would not be accepted in 2.2 and would be pushed to Silver.</td>
</tr>
<tr valign="top" align="left">
<td><p><strong><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#printing-customized-text">Printing</a>: </strong>Users can print content after customizing how the text is displayed.</p></td>
<td>B - user CSS, possible UI setting</td>
<td> </td>
<td> </td>
<td> </td>
<td>@@Laura I suspect that a printing SC would not be accepted in 2.2 and would be pushed to Silver.</td>
</tr>
<tr valign="top" align="left">
<td>[hover, focus...]</td>
<td> </td>
<td>1.4.13 Content on Hover or Focus</td>
<td> </td>
<td> </td>
<td>@@Jim - browser exception for TOOLTIPS. </td>
</tr>
<tr valign="top" align="left">
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>