-
Notifications
You must be signed in to change notification settings - Fork 1
/
xero-series2-engineers-session2.html
492 lines (413 loc) · 23.1 KB
/
xero-series2-engineers-session2.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
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>XERO Series 2 - Engineering Session 2</title>
<link rel="shortcut icon" href="favicon.ico">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" href="dist/reveal.css">
<link rel="stylesheet" href="dist/theme/intopia.css">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Source+Sans+Pro:ital,wght@0,400;0,600;0,700;1,400;1,600;1,700&display=swap" rel="stylesheet">
<link href="https://fonts.googleapis.com/css2?family=Roboto:ital,wght@0,300;0,400;0,500;0,700;1,300;1,400;1,500;1,700&display=swap" rel="stylesheet">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'dist/theme/pdf.css' : 'dist/theme/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
</head>
<body>
<div class="reveal">
<div class="slides">
<div class="menu">
<a href="index.html#session01">Home<span class="hidden"> - list of all slide decks</span></a> | <a href="#/">Start<span class="hidden"> of slide deck</span></a>
</div>
<section data-background="#EDEBEB">
<img class="intopia-logo" src="assets/img/logo-intopia.png" alt="Intopia">
<h1>Required fields and errors</h1>
<div class="subtitle">XERO Series 2 - Engineering Session 2</div>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-introduction">
<section data-background="#EDEBEB">
<h5>Recording</h5>
<p>As before, is everyone ok if we record this session?</p>
</section>
<section data-background="#EDEBEB">
<h5>Get involved</h5>
<p>Feel free to jump in any time with questions, comments or suggestions.</p>
</section>
<section data-background="#EDEBEB">
<h5>Today’s agenda:</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span><a href="#slide-screen-readers-and-forms">Screen readers and forms</a></li>
<li><span aria-hidden="true" class="icon icon-check"></span><a href="#slide-lets-review-some-forms">Review a range of your forms</a></li>
</ul>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-screen-readers-and-forms">
<section data-background="#EDEBEB">
<h3>Screen readers and forms</h3>
</section>
<section data-background="#EDEBEB">
<p>It is important to understand <b>how screen readers operate</b>, especially when interacting with form elements.</p>
</section>
<section data-background="#EDEBEB">
<p>Browsers go through a series of steps when <b>creating web documents</b>, starting with the Document Object Model (DOM).</p>
</section>
<section data-background="#EDEBEB">
<p>Browsers also <b>construct an accessibility tree</b> - a simplified version of the DOM.</p>
</section>
<section data-background="#EDEBEB">
<p>Screen readers analyze the accessibility tree and <b>create a linear version of this information</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>This information is then stored locally as a <b>‘virtual document’</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>Screen reader users can navigate this virtual document using <b>a range of keystrokes</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>For example, JAWS and NVDA use the following keys to <b>find and navigate to headings</b>:</p>
</section>
<section data-background="#EDEBEB">
<table>
<thead>
<tr>
<th>Key/function</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td><kbd>H</kbd></td>
<td>Jump to next heading</td>
</tr>
<tr>
<td><kbd>SHIFT</kbd> + <kbd>H</kbd></td>
<td>Jump to previous heading</td>
</tr>
<tr>
<td><kbd>1</kbd>, <kbd>2</kbd>, <kbd>3</kbd>, <kbd>4</kbd>, <kbd>5</kbd>, <kbd>6</kbd></td>
<td>Jump to next heading of that type</td>
</tr>
<tr>
<td><kbd>SHIFT</kbd> + <kbd>1</kbd>, <kbd>2</kbd>, <kbd>3</kbd>, <kbd>4</kbd>, <kbd>5</kbd>, <kbd>6</kbd></td>
<td>Jump to previous heading of that type</td>
</tr>
<tr>
<td>Elements list popup</td>
<td>View all headings</td>
</tr>
</tbody>
</table>
</section>
<section data-background="#EDEBEB">
<p>As screen reader users navigate through this virtual document, <b>the focal position is referred to as a ‘virtual cursor’</b>.</p>
</section>
<section data-background="#EDEBEB">
<h4>Two modes</h4>
</section>
<section data-background="#EDEBEB">
<p>The NVDA and JAWS screen readers have <b>two different modes</b>:</p>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span>Browse mode</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Forms mode (JAWS)/Focus mode (NVDA)</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h4>‘Browse mode’</h4>
</section>
<section data-background="#EDEBEB">
<p><b>‘Browse mode’</b> is used when navigating through the virtual document to read the content.</p>
</section>
<section data-background="#EDEBEB">
<h4>‘Forms/Focus mode’</h4>
</section>
<section data-background="#EDEBEB">
<p><b>‘Forms/Focus mode’</b> is used when interacting with form fields that require user input.</p>
</section>
<section data-background="#EDEBEB">
<p>When tabbing in ‘browse mode’ and reaching an element requiring keyboard input, JAWS and NVDA can automatically <b>switch to ‘forms/focus mode’</b>.</p>
<p class="font-xxs">* Depending on user settings</p>
</section>
<section data-background="#EDEBEB">
<p>When tabbing in ‘browse mode’ and reaching an element requiring keyboard input, JAWS and NVDA can automatically <b>switch to ‘forms/focus mode’</b>.</p>
<p class="font-xxs">* Depending on user settings</p>
</section>
<section data-background="#EDEBEB">
<p>Switching to ‘forms/focus mode’ mode will cause the screen reader to <b>leave the virtual document</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>Some screen reader users prefer to <b>switch manually between these two modes</b>, so that they have more control over the experience.</p>
</section>
<section data-background="#EDEBEB">
<h4>How do screen reader users navigate forms?</h4>
</section>
<section data-background="#EDEBEB">
<p>There are <b>many ways</b> these users may navigate through forms.</p>
</section>
<section data-background="#EDEBEB">
<h5>Method 1:</h5>
<p>Reading line-by-line through the form in ‘Browse mode’ to understand the form’s purpose.</p>
</section>
<section data-background="#EDEBEB">
<h5>Method 2</h5>
<p>Navigating via specific keystrokes (in JAWS and NVDA) to jump directly to form controls.</p>
</section>
<section data-background="#EDEBEB">
<table>
<thead>
<tr>
<th>Key</th>
<th>Task</th>
</tr>
</thead>
<tbody>
<tr>
<td><kbd>F</kbd></td>
<td>Next form field</td>
</tr>
<tr>
<td><kbd>B</kbd></td>
<td>Next button</td>
</tr>
<tr>
<td><kbd>R</kbd> (NVDA) or <kbd>A</kbd> (JAWS)</td>
<td>Next radio button</td>
</tr>
<tr>
<td><kbd>X</kbd></td>
<td>Next checkbox</td>
</tr>
</tbody>
</table>
</section>
<section data-background="#EDEBEB">
<p>After using the <kbd>F</kbd> key to navigate to a form field, users can use <kbd>ENTER</kbd> to switch into ‘Forms/Focus mode’ if they need to <b>type data into the field</b>.</p>
</section>
<section data-background="#EDEBEB">
<h5>Method 3</h5>
<p>Navigating via a list of all form fields - e.g using the Elements List (NVDA and JAWS) or the Rotor (VoiceOver).</p>
</section>
<section data-background="#EDEBEB">
<h5>Method 4</h5>
<p>Navigating via the <kbd>TAB</kbd> key, allowing the user to move to the next element that can receive focus - links, buttons, form fields.</p>
</section>
<section data-background="#EDEBEB">
<h4>‘Forms/Focus mode’ and form content</h4>
</section>
<section data-background="#EDEBEB">
<p>There is something to remember when users <b>navigate through a form</b> using <kbd>F</kbd> or <kbd>TAB</kbd> keys.</p>
</section>
<section data-background="#EDEBEB">
<p>Any content within the form that cannot receive focus or is not programmatically associated with a form field <b>will not be announced</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>For this reason, any information relevant to a form field must be <b>programmatically associated</b> with that field.</p>
</section>
<section data-background="#EDEBEB">
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span>Label text</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Radio group and checkbox group headings</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Form field instructions</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Form field error messages</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Required field notifications</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>Two form examples:</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span><a href="https://codepen.io/intopia-training/live/OJvqyGj" target="_blank">Associated form information - start</a></li>
<li><span aria-hidden="true" class="icon icon-check"></span><a href="https://codepen.io/intopia-training/live/oNQBqYg" target="_blank">Associated form information - finished</a></li>
</ul>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>Any <b>questions or comments</b>?</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/circle-question.svg" alt="">
</div>
</div>
</section>
</section>
<!-- –––––––––––––––––––––––––
SUB-SECTION
–––––––––––––––––––––––––– -->
<section id="slide-how-names-and-descriptions-are-announced">
<section data-background="#EDEBEB">
<h3>How names and descriptions are announced</h3>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>How are the accessible name and description <b>announced in different screen readers</b>?</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/volume-high.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<p>Screen readers announce objects within the accessibility tree <b>in the following order</b>:</p>
</section>
<section data-background="#EDEBEB">
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-volume-high"></span>User value (if present)</li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Accessible name</li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>State (Disabled, checked, unchecked etc.)</li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Role</li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Description</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>OSX / VoiceOver / Firefox and Safari</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Accessible name: <span class="success">‘Address’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>State:<span class="success"> ‘Required’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Role: <span class="success">‘Edit text’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>[Pause]</li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Description: <span class="success">‘Include full street address’</span></li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>OSX / VoiceOver / Chrome</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Accessible name: <span class="success">‘Address’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>State:<span class="success"> ‘Required’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Role: <span class="success">‘Edit text’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>[Pause]</li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Description: <span class="success">‘More content available’</span></li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>Windows / NVDA / Chrome</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Accessible name: <span class="success">‘Address’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Role: <span class="success">‘Edit’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Description: <span class="success">‘Include full street address’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Additional instructions: <span class="success">‘Blank’</span></li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>Windows / JAWS / Chrome</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Accessible name: <span class="success">‘Address’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Role: <span class="success">‘Edit’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Description: <span class="success">‘Include full street address’</span></li>
<li><span aria-hidden="true" class="icon icon-volume-high"></span>Additional instructions: <span class="success">‘Type in text’</span></li>
</ul>
</section>
</section>
<!-- –––––––––––––––––––––––––
SUB-SECTION
–––––––––––––––––––––––––– -->
<section id="slide-lets-review-some-forms">
<section data-background="#EDEBEB">
<h3>Let’s review some forms</h3>
</section>
<section data-background="#EDEBEB">
<h5>Some form examples</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span><a href="https://go.xero.com/app/!!SzBJ/contacts/add" target="_blank">Contacts > New Contact</a></li>
<li><span aria-hidden="true" class="icon icon-check"></span><a href="https://payroll.xero.com/Employee/NZ/details?CID=!!SzBJ&type=employee" target="_blank">Payroll > New employee</a></li>
<li><span aria-hidden="true" class="icon icon-check"></span>Any other form you'd like to review</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>1. Do all form fields have accessible names?</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Do they use matching for and id values?</li>
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Do they rely on lesser methods, such as placeholders?</li>
<li><span aria-hidden="true" class="icon icon-circle-question"></span><a href="https://russmaxdesign.github.io/accessible-forms/accessible-name-input01.html" target="_blank">Test cases</a></li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>2. Do you use fieldsets for radio and checkbox groups?</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Are fieldsets and legends used?</li>
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Is there any misuse of the button group?</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>3. Are your instructions programmatically associated?</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Do your instructions generate an accessible description?</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>4. Are your required fields visually identifiable?</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Do required fields have some sort of visual indicators?
<ul>
<li>Some sort of symbol</li>
<li>Required fields marked with (‘required’)</li>
<li>Optional fields marked with (‘optional’)</li>
</ul>
</li>
<li><span aria-hidden="true" class="icon icon-circle-question"></span>If required fields are not all identified, is there an overall message?</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>5. Are your required fields programmatically identifiable?</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Are required fields defined as <code>required</code> in the accessibility tree?</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>6. Are your error fields programmatically identifiable?</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Do errors generate an accessible description?</li>
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Are invalid fields defined as <code>invalid</code> in the accessibility tree?</li>
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Are error states triggered via <code>onBlur</code> or when submitted?</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h5>7. What happens when a user submits a form with errors?</h5>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Where does focus go?</li>
<li><span aria-hidden="true" class="icon icon-circle-question"></span>Are users informed:
<ul>
<li>That there are errors?</li>
<li>The number of errors?</li>
<li>How to navigate to each error?</li>
</ul>
</li>
</ul>
</section>
</section>
</div>
</div>
<script src="https://cdnjs.cloudflare.com/ajax/libs/headjs/1.0.3/head.min.js"></script>
<script src="dist/reveal.js"></script>
<script src="plugin/notes/notes.js"></script>
<script>
// More info about initialization & config:
// - https://revealjs.com/initialization/
// - https://revealjs.com/config/
Reveal.initialize({
hash: true,
controls: true,
progress: true,
history: true,
center: true,
transition: 'none',
// Learn about plugins: https://revealjs.com/plugins/
plugins: [ RevealNotes ]
});
</script>
</body>
</html>