-
Notifications
You must be signed in to change notification settings - Fork 1
/
2023-accessu.html
895 lines (722 loc) · 37.8 KB
/
2023-accessu.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
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>AccessU 2023: Conducting accessibility testing on complex widgets</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>Conducting accessibility testing on complex widgets</h1>
<div class="subtitle">AccessU 2023</div>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-acknowledgement-of-country">
<section data-background="#C03C0C">
<h2>Introduction</h2>
</section>
<section data-background="#EDEBEB">
<p>Because I am presenting from Australia, I’d like to <b>acknowledge the Traditional Owners of the lands</b> on which I’m presenting today, the Cammeraygal people.</p>
</section>
<section data-background="#EDEBEB">
<p>I’d also like to <b>pay my respects to Elders past and present</b>, and to all First Nations people who may be present or watch a recording of this session.</p>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>I’d like this session to be interactive, so feel free to <b>add any comments or questions into chat</b> at any time!</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/comments.svg" alt="">
</div>
</div>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-two-areas-of-focus">
<section data-background="#C03C0C">
<h2>‘Are the components accessible?’</h2>
</section>
<section data-background="#EDEBEB">
<p>Part of my role over the years has focussed on <b>helping teams build and test</b> a wide range of UI components.</p>
</section>
<section data-background="#EDEBEB">
<p>The term <b>‘components’</b> (sometimes referred to as widgets) means any self-contained UI concept.</p>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>I mainly focussed on components that involved <b>user interaction</b>.</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/bullseye-pointer.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<p>This could mean <b>simple components</b> such as:</p>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span>Links.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Buttons.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Form controls and their associated labels.</li>
</ul>
</section>
<section data-background="#EDEBEB">
<p>But most of my time was spent on <b>complex components</b> such as:</p>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span>Sortable tables.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Accordions.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Dropdown menus.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>Date pickers.</li>
</ul>
</section>
<section data-background="#EDEBEB">
<p>In the earlier days, I would conduct basic accessibility testing on each component, but there were <b>some underlying problems in my approach</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>My testing process <b>lacked rigour</b>, and I did not provide <b>detailed documentation</b> of my test results.</p>
</section>
<section data-background="#EDEBEB">
<p>At one point, a manager <b>asked me the following question</b>:</p>
</section>
<section data-background="#EDEBEB">
<p><i>Are all the components in the design system accessible? Can you guarantee it?</i></p>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>This was a <b>wake-up call</b> that led my to change the way I tested and documented components.</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/circle-exclamation.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>For this presentation, I’ll share how I conducted <b>‘accessibility unit testing’ </b> on individual components.</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/memo-circle-check.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>As we’ll see a bit later, this process can also help when <b>designing or developing</b> new components.</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/check.svg" alt="">
</div>
</div>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-what-is-accessibility-unit-testing">
<section data-background="#C03C0C">
<h2>What is accessibility unit testing?</h2>
</section>
<section data-background="#EDEBEB">
<p>‘accessibility unit testing’ is a process where the smallest parts of a component are <b>individually and independently evaluated</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>The aim of accessibility unit testing is not to make broad, sweeping statements such as <b>‘this component is accessible’</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>Instead, the aim is to test the accessibility of <b>all aspects of the component</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>This process provides teams with a detailed understanding about <b>all possible accessibility issues</b> associated with the component.</p>
</section>
<section data-background="#EDEBEB">
<p>Accessibility unit testing is typically conducted when reviewing:</p>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span>An <b>existing component</b> within the system.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>A <b>new component</b> to be added to the system</li>
</ul>
</section>
<section data-background="#EDEBEB">
<p>Accessibility unit tests are often based on <b>two concepts</b>:</p>
</section>
<section data-background="#EDEBEB">
<p>1. How all aspects of the component are <b>presented to users</b> - either on screen or via assistive technologies.</p>
</section>
<section data-background="#EDEBEB">
<p>2. How users should be able to <b>interact with the component</b> to complete all relevant tasks.</p>
</section>
<section data-background="#EDEBEB">
<p>These tests must include <b>all possible happy and unhappy paths</b> associated with the component.</p>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>A <b>happy path</b> is the error-free path users take to complete a task.</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/face-smile.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>An <b>unhappy path</b> is where users may encounter errors or issues that stop them from completing the task.</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/face-confused.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>Let’s use an example of a <b>date picker</b> - one of the most painful components ever conceived!</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/calendar-days.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<p>A <b>high-level task</b> might be something like:</p>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The user can successfully add a date using the date picker.</p>
</div>
</section>
<section data-background="#EDEBEB">
<p>But <b>numerous small interactions</b> associated with this overall task should be tested.</p>
</section>
<section data-background="#EDEBEB">
<p>And there are <b>different methods that people use</b> to achieve these interactions - mouse, keyboard, assistive technologies etc.</p>
</section>
<section data-background="#EDEBEB">
<p>Each of these needs to be <b>defined as a test</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>For example, what tests would be needed to determine if the date picker overlay <b>could be closed via keystrokes only</b>?</p>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The <kbd>ESC</kbd> key can be used to close the date picker overlay: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>When the <kbd>ESC</kbd> key is triggered, focus returns to the date field: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<p>These are <b>two separate tests</b>, because a date picker may allow users to close the the overlay using <kbd>ESC</kbd>, but send focus to the wrong location.</p>
</section>
<section data-background="#EDEBEB">
<p>An unhappy path could be where the date-picker question is required, but the user <b>does not enter a date value</b> for the field.</p>
</section>
<section data-background="#EDEBEB">
<p>What tests would be needed to determine if users <b>could identify the field as required</b> before deciding whether to enter data?</p>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>A visual means of identifying that the field is required is present: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>Users can programmatically determine that the field is required (e.g. via <code>required</code> or <code>aria-required="true"</code>): <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<p>And what tests would be needed to <b>determine if the field is accessible</b> once it is in a state of error?</p>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The form field uses methods other than colour alone to visually identify that it is in a state of error: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>When the field is in a state of error, an error message is presented on screen: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The error message provides advice on how to fix the problem: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The error message is presented in close proximity to the field in a state of error: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The error message is programmatically associated with the field (e.g. as part of the <code><label></code> or via <code>aria-describedby</code>): <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<p>As you can see, every test must be written as a statement where the only outcome is either <b>a pass or a fail</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>Tests <b>do not have to be tasks</b>. A test may relate to how aspects of the component are presented to users.</p>
</section>
<section data-background="#EDEBEB">
<p>Each test must be <b>repeatable</b> so that it can be re-tested at a later date.</p>
</section>
<section data-background="#EDEBEB">
<p>These tests may need to be performed in <b>complex combinations</b> of different assistive technologies, browsers and operating systems.</p>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>Each of these different test combinations must be <b>documented separately</b>.</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/align-left.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<p>The end result should be a document that <b>defines the following</b>:</p>
</section>
<section data-background="#EDEBEB">
<ul class="icon-list">
<li><span aria-hidden="true" class="icon icon-check"></span>The <b>test</b>.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>The <b>environment</b> in which the task was performed.</li>
<li><span aria-hidden="true" class="icon icon-check"></span>The <b>result of the test</b> within the environment.</li>
</ul>
</section>
<section data-background="#EDEBEB">
<p>Let’s look at an example of an <b>autocomplete component</b> from the last design system I worked on.</p>
<p class="font-sm">(I’m going to open a strange spreadsheet now).</p>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>Before we look at how to create these tasks, 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>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-starting-with-people-and-their-needs">
<section data-background="#C03C0C">
<h2>Starting with people and their needs</h2>
</section>
<section data-background="#EDEBEB">
<p>How could you create <b>a complex series of tests</b> for any component?</p>
</section>
<section data-background="#EDEBEB">
<p>You can start by looking at <b>different groups of people and their needs</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>This means you can focus on one user type and explore <b>how they may need to interact with the component</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>These <b>groups of people</b> could include:</p>
</section>
<section data-background="#EDEBEB">
<ol class="font-sm">
<li>People with some sort of <b>cognitive impairment</b> or <b>neurodivergence</b>.</li>
<li>People with some sort of <b>colour vision deficiency</b>.</li>
<li>People with <b>reduced vision</b>.</li>
<li>People with <b>limited mobility</b>.</li>
<li>People with <b>limited or no sight</b>.</li>
<li>People with <b>limited or no hearing</b>.</li>
</ol>
</section>
<section data-background="#EDEBEB">
<p>For each group, there are some <b>high levels questions</b> that can be asked for any component to help determine possible tests.</p>
</section>
<section data-background="#EDEBEB">
<h4>1. People with some sort of cognitive impairment or neurodivergence</h4>
</section>
<section data-background="#EDEBEB">
<ol class="font-xs">
<li>Is the purpose of the component clear?</li>
<li>Is the component easy to use?</li>
<li>If additional instructions are required, are they clear?</li>
<li>If users make a mistake, can they quickly and easily recover?</li>
<li>Is there any complex language used associated with the component?</li>
<li>Are there any animations or movements that could distract the user?</li>
</ol>
</section>
<section data-background="#EDEBEB">
<h4>2. People with some sort of colour vision deficiency</h4>
</section>
<section data-background="#EDEBEB">
<p>Does the component:</p>
<ol class="font-sm">
<li>Have sufficient colour contrast?</li>
<li>Use alternative methods to display colour information?</li>
</ol>
</section>
<section data-background="#EDEBEB">
<h4>3. People with reduced vision</h4>
</section>
<section data-background="#EDEBEB">
<p>Sometimes, these people may need to <b>customise the user interface or magnify the display</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>Is the component operable/understandable:</p>
<ol class="font-xs">
<li>When the text is scaled to 400%?</li>
<li>When the overall layout is scaled to 400%?</li>
<li>When aspects of the component are magnified?</li>
<li>When displayed in low contrast?</li>
<li>When displayed in different viewport sizes?</li>
</ol>
</section>
<section data-background="#EDEBEB">
<h4>4. People with limited mobility</h4>
</section>
<section data-background="#EDEBEB">
<p>Sometimes, these people may rely on <b>keyboard interactions</b> or <b>voice recognition software</b>.</p>
</section>
<section data-background="#EDEBEB">
<ol class="font-xs">
<li>Does the component need to receive focus?</li>
<li>Is focus managed into, within and out of the component?</li>
<li>Does focus order follow a meaningful sequence?</li>
<li>Can all actions be executed using keystrokes only?</li>
<li>Can all actions be executed using voice controls?</li>
<li>Are keystrokes intuitive for keyboard-only users?</li>
<li>If focus is relevant, are all visible focus states clearly defined?</li>
</ol>
</section>
<section data-background="#EDEBEB">
<h4>5. People with limited or no sight</h4>
</section>
<section data-background="#EDEBEB">
<p>These people may rely on <b>screen reader software</b>.</p>
</section>
<section data-background="#EDEBEB">
<ol class="font-xs">
<li>Does the component have an accessible name?</li>
<li>Does the accessible name clearly define the component's purpose?</li>
<li>Does the component have a role?</li>
<li>Are all of the component's possible states defined?</li>
<li>If a value can be added within the component, is it exposed?</li>
<li>If the component has any dynamically added content, is this announced at the appropriate time?</li>
</ol>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-creating-tests-from-each-question">
<section data-background="#C03C0C">
<h2>Creating tests from each question</h2>
</section>
<section data-background="#EDEBEB">
<p>The next step is to break down each question into <b>a series of individual tests</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>In some cases, the question <b>can almost become the test</b>. For example:</p>
</section>
<section data-background="#EDEBEB">
<h5>Question:</h5>
<p><i>Does the component have an accessible name?</i></p>
</section>
<section data-background="#EDEBEB">
<h5>Test 1:</h5>
<div class="text-example">
<p>The component provides an accessible name: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<h5>Test 2:</h5>
<div class="text-example">
<p>The accessible name is meaningful (e.g. describes the purpose of the element): <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<p>In other cases, you may need <b>multiple tests associated with a question</b>. For example:</p>
</section>
<section data-background="#EDEBEB">
<h5>Question:</h5>
<p><i>Can all actions be executed using keystrokes only?</i></p>
</section>
<section data-background="#EDEBEB">
<p>This question may need a <b>wide range of individual tests</b>, depending on the complexity of the component.</p>
</section>
<section data-background="#EDEBEB">
<p>Let’s <b>dive a bit deeper into tests</b> that could be used to determine the accessibility of a <a href="https://dequeuniversity.com/library/aria/date-picker" target="_blank">date picker</a>.</p>
</section>
<section data-background="#EDEBEB">
<p>For simplicity, we will focus on <b>people with limited mobility</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>How would someone who uses a keyboard-only need to <b>interact with this component</b>?</p>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The user can manually enter a date without using the date picker overlay: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The user can navigate to the date picker icon: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The user can trigger the date picker overlay using <kbd>ENTER</kbd> and <kbd>SPACEBAR</kbd>: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>When the date picker icon is triggered, focus moves to the date picker overlay: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<p>But which part of the date picker overlay should <b>receive focus</b>?</p>
<ul class="icon-list font-sm">
<li><span aria-hidden="true" class="icon icon-check"></span>The date picker overlay container?</li>
<li><span aria-hidden="true" class="icon icon-check"></span>The current date?</li>
<li><span aria-hidden="true" class="icon icon-check"></span>The close button?</li>
<li><span aria-hidden="true" class="icon icon-check"></span>The previous or next month buttons?</li>
</ul>
</section>
<section data-background="#EDEBEB">
<p>You may need to do a <a href="https://russmaxdesign.github.io/accessible-forms/#onsubmit" target="_blank">lot of testing</a> before deciding on <b>the best solution</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>Ideally, you should also <b>test with real users</b> to find out their preferences and expectations.</p>
</section>
<section data-background="#EDEBEB">
<p>This is not a significant issue for keyboard users but becomes <b>very important for screen reader users</b> as they require additional context!</p>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The users can navigate through dates using all variations of <kbd>ARROW</kbd> keys: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The users can navigate to previous or next month dates using all variations of <kbd>ARROW</kbd> keys: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The user can select a date using <kbd>ENTER</kbd> and <kbd>SPACEBAR</kbd>: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>When a date is selected, the date picker overlay closes: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>When a date is selected, focus returns to the form field: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>When focus returns to the form field, the chosen date is injected into the field: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The user can <kbd>TAB</kbd> to the ‘Close’ button: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>When the ‘Close’ button is selected, focus returns to the form field: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The user can close the date picker overlay using the <kbd>ESC</kbd> key: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>When the <kbd>ESC</kbd> key is trigged selected, focus returns to the form field: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>The user can <kbd>TAB</kbd> to the previous and next month buttons: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<div class="text-example">
<p>When the previous or next buttons are triggered, the Month title and date table updates: <span class="badge">PASS/FAIL</span></p>
</div>
</section>
<section data-background="#EDEBEB">
<p>These are just some examples of unit tests that could be <b>conducted using keyboard-only</b>.</p>
</section>
<section data-background="#EDEBEB">
<p>We could then use <b>the same process</b> for other uses, such as ‘People with limited or no sight’.</p>
</section>
<section data-background="#EDEBEB">
<p>Screen readers must be given <b>additional context for each interaction</b> - name, role, states, values etc.</p>
</section>
<section data-background="#EDEBEB">
<p>The names and roles must also <b>clearly define the purpose</b> of the element.</p>
</section>
<section data-background="#EDEBEB">
<p>I always run keyboard-only tests <b>before screen reader tests</b>, as screen reader users need the same basic functionality with additional criteria.</p>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-after-the-tasks-are-finished">
<section data-background="#C03C0C">
<h2>After the tasks are finished?</h2>
</section>
<section data-background="#EDEBEB">
<p>We need to determine if each test can be <b>conducted using a single browser</b> or if multiple browsers are required.</p>
</section>
<section data-background="#EDEBEB">
<p>We also need to determine if any <b>assistive technologies are required</b> for any tests and if these need to be conducted across multiple browser options.</p>
</section>
<section data-background="#EDEBEB">
<p>We can then <b>create a testing spreadsheet</b> and begin testing!</p>
</section>
</section>
<!-- –––––––––––––––––––––––––
****** SECTION ******
–––––––––––––––––––––––––– -->
<section id="slide-circling-back-to-design-and-development">
<section data-background="#C03C0C">
<h2>Circling back to design and development</h2>
</section>
<section data-background="#EDEBEB">
<p>As mentioned earlier, this overall concept can also be used to help <b>design and development new components</b>:</p>
</section>
<section data-background="#EDEBEB">
<p>Teams can ask themselves the <b>following three questions</b>:</p>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>1. What <b>different types of users</b> may interact with the component.</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/circle-1.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>2. How are all aspects of the component <b>presented to these users</b>?</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/circle-2.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>3. What are all the ways that these users <b>may need to interact with the component</b> to complete a task?</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/circle-3.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>If these three questions are considered, you are much more likely to have <b>an accessible component</b>!</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/circle-check.svg" alt="">
</div>
</div>
</section>
<section data-background="#EDEBEB">
<div class="col-container">
<div class="col-75">
<p>And finally, try to include a <b>diverse range of real users</b> as part of the design and development process!</p>
</div>
<div class="col-25">
<img class="icon-soft" src="assets/icons/universal-access.svg" alt="">
</div>
</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>