-
Notifications
You must be signed in to change notification settings - Fork 1
/
2024-allybytes.html
516 lines (390 loc) · 19.3 KB
/
2024-allybytes.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
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>A11ybytes Sydney 2024: The joys of focus management and announcing changes</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="#/">Start<span class="hidden"> of slide deck</span></a>
</div>
<section data-background="#EDEBEB">
<div class="instructions">
<h3 class="instructions-heading">Slide instructions</h3>
<p><kbd>SPACEBAR</kbd> to <b>move forward</b> through slides.</p>
<p><kbd>SHIFT</kbd> & <kbd>SPACEBAR</kbd> to <b>move backwards</b> through slides.</p>
<p><kbd>LEFT ARROW</kbd> & <kbd>RIGHT ARROW</kbd> to <b>move through sections</b>.</p>
<p><kbd>ESC</kbd> to <b>see overview</b> and <kbd>ESC</kbd> again to exit.</p>
<p><kbd>F</kbd> to <b>enter presentation mode</b> and <kbd>ESC</kbd> to exit.</p>
</div>
</section>
<section data-background="#EDEBEB">
<img class="intopia-logo" src="assets/img/logo-intopia.png" alt="Intopia">
<h1>The joys of focus management and announcing changes</h1>
<div class="subtitle">A11ybytes Sydney 2024</div>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-setting-the-scene">
<section data-background="#C03C0C">
<h2>Setting the scene</h2>
</section>
<section data-background="#EDEBEB">
<p>We’re going to explore how <b>two people</b> could interacting with aspects of your web site or web application.</p>
</section>
<section data-background="#EDEBEB">
<p><b>Mary</b> has reduced movement. She uses a head switch (keyboard equivalent) and cannot use a mouse.</p>
</section>
<section data-background="#EDEBEB">
<p><b>Hassan</b> is a person who is blind. He uses a screen reader.</p>
</section>
<section data-background="#EDEBEB">
<h4>Focus management</h4>
</section>
<section data-background="#EDEBEB">
<p>For both Mary and Hassan, <b>focus management</b> helps them understand:</p>
</section>
<section data-background="#EDEBEB">
<ul class="icon-list">
<li><span aria-hidden="true" class="icon icon-check"></span>What changes may have occurred in the UI.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>What they may have to do next.</li>
</ul>
</section>
<section data-background="#EDEBEB">
<p>If focus management is poorly managed, it can cause <b>confusion or frustration</b>.</p>
</section>
<section data-background="#EDEBEB">
<h4>Announcing changes</h4>
</section>
<section data-background="#EDEBEB">
<p>For Hassan, <b>announcing all dynamic changes</b> is also important.</p>
</section>
<section data-background="#EDEBEB">
<p>Especially when <b>buttons are used to trigger UI changes</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>Let’s look at how <b>some different scenarios</b> could affect Mary and Hassan.</p>
</section>
<section data-background="#EDEBEB">
<p>By the way, I will be <b>asking for your answers</b>!</p>
</section>
<section data-background="#EDEBEB">
<p>I know it is late. It’s cold. You’d rather be at home <b>in bed watching Netflix</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>So, I have some <b>incentives</b>!</p>
</section>
<section data-background="#EDEBEB">
<p>The first person who answers correctly in each case <b>wins a mini Mars Bar</b>.</p>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-scenario-1-a-form-error">
<section data-background="#C03C0C">
<h2>Scenario 1: A form error</h2>
</section>
<section data-background="#EDEBEB">
<p>Image that Mary and Hassan have attempted to submit a form, but <b>the form contains errors</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>As soon as the submit button is <b>activated</b>:</p>
</section>
<section data-background="#EDEBEB">
<h4>Where should focus go?</h4>
</section>
<section data-background="#EDEBEB">
<p>There are <b>two acceptable answers</b> to this question.</p>
</section>
<section data-background="#EDEBEB">
<p><em>Gimme your answer!</em></p>
</section>
<section data-background="#EDEBEB">
<p>For <b>simple forms</b>, focus can go to the first error within the form.</p>
<p class="font-xs">* Forms with only two questions.</p>
</section>
<section data-background="#EDEBEB">
<p>For <b>more complex forms</b>, focus should go to an error message above the form.</p>
<p class="font-xs">* Forms with more than two questions.</p>
</section>
<section data-background="#EDEBEB">
<h4>Story time</h4>
</section>
<section data-background="#EDEBEB">
<p>Some time ago, I observed Hassan trying to <b>resolve multiple errors</b> in a complex form.</p>
</section>
<section data-background="#EDEBEB">
<p>Initially, he was taken to the <b>first invalid field</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>When he resolved the error, he hit the <kbd>B</kbd> key to take him <b>directly to the submit button</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>It took several cycles of this process to for him to realise <b>the form had multiple errors</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>If he has been sent to an error message above the form, he would have <b>known the exact number of error messages</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>Back to our question... As soon as the submit button is <b>activated</b>:</p>
</section>
<section data-background="#EDEBEB">
<h4>What should be announced?</h4>
</section>
<section data-background="#EDEBEB">
<p>For the simple form, <b>three things shoulds be immediately annonced</b> if focus goes to the first field that is invalid.</p>
</section>
<section data-background="#EDEBEB">
<p><em>Gimme your answer!</em></p>
</section>
<section data-background="#EDEBEB">
<p>For simple forms:</p>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span>The accessible name of the form control.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>The current state of the form control (via <code>aria-invalid="true"</code>).</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Any relevant error message (via <code>aria-describedby</code>).</li>
</ul>
</section>
<section data-background="#EDEBEB">
<p>And for the more complex form, <b>only one thing</b> should be immediately announced.</p>
</section>
<section data-background="#EDEBEB">
<p><em>Gimme your answer!</em></p>
</section>
<section data-background="#EDEBEB">
<p>Content that <b>informs the user that errors have occurred</b> and possibly provides the number of errors.</p>
</section>
<section data-background="#EDEBEB">
<p>Keep in mind, the list of links will <b>not be immediately announced</b>.</p>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-scenario-2-a-toast-popup">
<section data-background="#C03C0C">
<h2>Scenario 2: A toast popup</h2>
</section>
<section data-background="#EDEBEB">
<p>Image that Mary and Hassan have <b>successfully completed a process</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>A toast notification <b>animates into view from the bottom of the screen</b> for a short period of time before disappearing.</p>
</section>
<section data-background="#EDEBEB">
<h4>Where should focus go?</h4>
</section>
<section data-background="#EDEBEB">
<p><em>Gimme your answer!</em></p>
</section>
<section data-background="#EDEBEB">
<p>Ideally, toast notifications are for information that <b>does not require user input</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>For this reason, focus should <b>not go to the toast notification</b>.</p>
</section>
<section data-background="#EDEBEB">
<h4>Story time</h4>
</section>
<section data-background="#EDEBEB">
<p>Recently, I observed Mary <b>interacting with a web app</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>When the toast popup appeared, <b>focus automatically shifted to the toast notification</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>This was <b>disconcerting</b> as she was in the middle of doing a different task, and she was not given any option or warning.</p>
</section>
<section data-background="#EDEBEB">
<p>Even worse, she then had to <b>navigate back to her previous location</b>.</p>
</section>
<section data-background="#EDEBEB">
<h4>When the toast popup appears... what should be announced?</h4>
</section>
<section data-background="#EDEBEB">
<p><em>Gimme your answers!</em></p>
</section>
<section data-background="#EDEBEB">
<p>If the information is displayed on-screen, it is important enough to be <b>made available to all users</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>So, the information could be announced <b>at the next graceful opportunity</b> – using <code>aria-live="polite"</code>.</p>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-scenario-3-a-date-is-selected-from-a-date-picker-popup">
<section data-background="#C03C0C">
<h2>Scenario 3: A date picker popup</h2>
</section>
<section data-background="#EDEBEB">
<p>Image Mary and Hassan have navigated through a date pickup popover and <b>selected a date</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>When they <b>choose a date from the popup</b>:</p>
</section>
<section data-background="#EDEBEB">
<h4>Where should focus go?</h4>
</section>
<section data-background="#EDEBEB">
<p><em>Gimme your answer!</em></p>
</section>
<section data-background="#EDEBEB">
<p>Focus should return to the <b>input</b>.</p>
</section>
<section data-background="#EDEBEB">
<h4>What should be announced?</h4>
</section>
<section data-background="#EDEBEB">
<p><em>Gimme your answer!</em></p>
</section>
<section data-background="#EDEBEB">
<p>When focus returns to the input, the <b>date value should be injected</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>So, the following should be announced:</p>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span>The accessible name of the form control.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>The current value of the form control (i.e. the chosen date).</li>
</ul>
</section>
<section data-background="#EDEBEB">
<h4>Story time</h4>
</section>
<section data-background="#EDEBEB">
<p>I recently observed Hassan <b>interacting with a date picker</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>After choosing a date, <b>focus was sent to the date picker icon</b> rather than the input.</p>
</section>
<section data-background="#EDEBEB">
<p>Hassan had no feedback to tell him the date <b>had been successfully stored</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>He <b>repeated the process several times</b> until he discovered the date had been correctly injected into the form field.</p>
</section>
<section data-background="#EDEBEB">
<p>If focus had been sent to the input, he would have <b>immediately known the process was successful</b>.</p>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-scenario-4-the-user-has-just-re-sorted-the-row-order-in-a-sortable-table">
<section data-background="#C03C0C">
<h2>Scenario 4: An accordion</h2>
</section>
<section data-background="#EDEBEB">
<p>Imagine that Mary and Hassan are <b>navigating a vertical accordion</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>They decide to <b>select an accordion option</b> to find out more.</p>
</section>
<section data-background="#EDEBEB">
<p>When this <b>action is triggered</b>:</p>
</section>
<section data-background="#EDEBEB">
<h4>Where should focus go?</h4>
</section>
<section data-background="#EDEBEB">
<p><em>Gimme your answer!</em></p>
</section>
<section data-background="#EDEBEB">
<p>Focus should <b>remain on the button</b> that triggered the action.</p>
</section>
<section data-background="#EDEBEB">
<h4>What should be announced?</h4>
</section>
<section data-background="#EDEBEB">
<p><em>Gimme your answer!</em></p>
</section>
<section data-background="#EDEBEB">
<p>Remember, we never want Hassan to <b>click something and have silence</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>Hassan should be <b>informed that the accordion option has now been expanded</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>This can be acheived by <b>dynamically switching</b> <code>aria-expanded="true"</code>.</p>
</section>
<section data-background="#222">
<pre><code contenteditable="true"><button <span class="codeHighlight">aria-expanded="false"</span class="codeHighlight"> aria-controls="widget1">
Show widget
</button></code></pre>
</section>
<section data-background="#222">
<pre><code contenteditable="true"><button <span class="codeHighlight">aria-expanded="true"</span> aria-controls="widget1">
Hide widget
</button></code></pre>
</section>
<section data-background="#EDEBEB">
<h4>Story time</h4>
</section>
<section data-background="#EDEBEB">
<p>As before, I observed Hassan <b>interacting with an accordion</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>After triggering an accordion button, there was <b>total silence</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>That's when Hassan said:</p>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p><em>I hate when I click on something and then hear nothing. I have no idea what just happened.</em></p>
</div>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-questions">
<section data-background="#C03C0C">
<h2>Questions or discussion?</h2>
</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>