forked from bobbijvoet/a11y
-
Notifications
You must be signed in to change notification settings - Fork 0
/
article.html
1332 lines (1144 loc) · 66.9 KB
/
article.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
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=5.0, minimum-scale=0.5, user-scalable=yes">
<title>Accessible Article Page - Good and Bad Demonstration - ING</title>
<link href="https://fonts.googleapis.com/css?family=Roboto:400,400i,500,700,900" rel="stylesheet">
<link rel="stylesheet" href="styles/libs/bootstrap/bootstrap.processed.css">
<link rel="stylesheet" href="styles/style.processed.min.css">
<link rel="stylesheet" href="https://www.ing.nl/assets/web/ng/css/bb4d737d.the-guide-styles-responsive.min.css">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
<script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.min.js"></script>
<script>
hljs.initHighlightingOnLoad();
</script>
</head>
<body class="body" id="totop">
<header class="site-header" role="banner">
<div class="skip-links">
<a href="#main-menu">Skip to Main Menu</a>
<a href="#main-content">Skip to Main Content</a>
</div>
<div class="bg-faded pt-2">
<div class="container">
<div class="row">
<div class="col-md-6">
<div class="pipe-links">
<ul class="list-inline m-0" aria-label="section links">
<li class="list-inline-item"><a href="http://bit.ly/a11y-dev-champs">Champ Lessons</a></li>
<li class="list-inline-item">Good / Bad</li>
<li class="list-inline-item"><a href="http://bit.ly/a11y-quiz">Quiz</a></li>
</ul>
</div>
</div>
<div class="col-md-6 pipe-rechts">
<label class="mr-1 d-inline-block" for="language">Language</label>
<div class="d-inline-block p-relative">
<select class="mr-2" name="language" id="language">
<option value="english" selected>English</option>
<option value="nederlands" lang="nl">Nederlands</option>
</select>
</div>
<button class="btn btn-secondary btn-sm" id="annotations01">Annotations</button>
</div>
</div>
</div>
</div>
<div class="navbar navbar-toggleable-md navbar-light">
<nav class="container" role="navigation" aria-labelledby="main-nav">
<div class="sr-only" id="main-nav">Main Menu</div>
<a href="index.html" class="navbar-brand">
<img class="avatar-img" src="https://s3-us-west-2.amazonaws.com/s.cdpn.io/1182308/a11y-logo.png" alt="Accessibility Portal">
</a>
<button class="navbar-toggler navbar-toggler-right" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false">
<span class="navbar-toggler-icon"></span>
<span class="sr-only">Toggle navigation</span>
</button>
<div class="collapse navbar-collapse" id="navbarSupportedContent">
<div class="mr-auto">
<ul class="navbar-nav" aria-labelledby="main-nav">
<li class="nav-item">
<a class="nav-link" href="index.html" id="main-menu">Home</a>
</li>
<li class="nav-item active">
<a class="nav-link" href="article.html" aria-current="page">Article <span class="sr-only">(current)</span></a>
<ul class="pagination pagination-navbar" aria-label="Sub navigation Main Menu">
<li class="page-item"><a class="page-link active" href="article.html" aria-current="page">Good <span class="sr-only">(current)</span></a></li>
<li class="page-item"><a class="page-link" href="article-bad.html">Bad</a></li>
</ul>
</li>
<li class="nav-item">
<a class="nav-link" href="media.html">Media</a>
</li>
<li class="nav-item">
<a class="nav-link" href="request.html">Request</a>
</li>
<li class="nav-item">
<a class="nav-link" href="table.html">Tables</a>
</li>
</ul>
</div>
<nav class="form-inline my-2 my-lg-0" role="search">
<form class="form-inline">
<label for="search">Search</label>
<input class="form-control form-control-search mr-2" type="text" id="search">
<button class="btn btn-tertiary search-button my-2 my-sm-0 ml-0" type="submit">
<span class="icon icon-search icon-lg text-orange" aria-hidden="true"></span>
<span class="sr-only">Search</span>
</button>
</form>
</nav>
</div>
</nav>
</div>
<div class="brandbar brandbar-a">
<div class="brandbar-image brandbar-image-article"></div>
<div class="container">
<header class="brandbar-header">
<div class="brandbar-heading">
<span class="d-block annot-relative">
<h1 class="brandbar-title btn-annot-outline">Accessible Article Page</h1>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal01">01</button>
</span>
<span class="d-block annot-relative">
<p class="brandbar-lead btn-annot-outline">Good and Bad Demonstration</p>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal02">02</button>
</span>
<span class="d-block mt-2 annot-relative">
<a href="https://dequeuniversity.com/class/content-contributors1/introduction" class="link-primary btn-annot-outline">
Web Accessibility for Content Contributors
</a>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal03">03</button>
</span>
</div>
</header>
</div>
</div>
</header>
<main role="main" id="main-content">
<article class="full-cover article-main" aria-labelledby="article-main">
<div class="container">
<h2 id="article-main" class="sr-only">The social model of disability</h2>
<div class="row">
<div class="col-md-7 col-lg-8 pr-5">
<span class="d-block annot-relative">
<p class="lead mb-4 btn-annot-outline">The social model of disability is a way of thinking which states that disability is caused by barriers within society rather than an individual’s impairment. Through this lens, it’s possible to conceive that if all barriers could be removed, disability would cease to exist.</p>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal04">04</button>
</span>
<p>Team Accessibility (Team <abbr class="annot-relative btn-annot-outline" title="accessibility">A11Y <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal05">05</button></abbr>) helps squads to remove the digital barriers and make ING websites and apps accessible to all people, with or without disabilities. The help consists of co-creation, laying out the digital baseline and provide training for accessibility champions.</p>
<h3 class="heading-l annot-relative btn-annot-outline">Why we promote accessibility <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal06">06</button></h3>
<p>Our believe is that <strong class="annot-relative btn-annot-outline">digital equality is a human right <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal07">07</button></strong> for websites, mobile applications, and digital content. <span class="d-block mt-2">But it doesn’t stop there. We need to do it for quality, innovation, compliance, relations, user experience and much much more.</span>
<span class="d-block mt-4 mb-4 annot-relative">
<a href="https://the-pastry-box-project.net/anne-gibson/2014-july-31" class="link-linklist btn-annot-outline" target="_blank">An Alphabet of Accessibility Issues <span class="icon icon-arrow-f-up-right icon-md icon-gray-dark mt-n2" role="img" aria-label="Opens in new window"></span></a>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal08">08</button>
</span>
<span class="d-block annot-relative">
<button type="button" class="btn btn-primary btn-annot-outline" data-toggle="modal" data-target="#a11ycasts">Introducing A11Ycasts!</button>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal03">03</button>
</span>
</p>
<h3 class="heading-l annot-relative btn-annot-outline">How we strive for accessibility <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal06">06</button></h3>
<p>With greatest passion we support and train people who can make that vision a reality.<span class="d-block mt-2">By providing insights and good examples in how people and technology absorb information.</span></p>
<figure class="btn-annot-outline" role="group" aria-labelledby="figcaption">
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal09">09</button>
<img src="https://s3-us-west-2.amazonaws.com/s.cdpn.io/1182308/tile-ForwardPlanning.jpg" class="img-radius-l img-fluid" alt="People in the ING Emphathy Lab">
<figcaption class="annot-relative btn-annot-outline" id="figcaption"><span><em>Four people in a room at desks with a laptop in an informal setting. One person is standing beside another, looking at a screen, seemingly helping out.</em> <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal07">07</button></span></figcaption>
</figure>
<div class="annot-relative btn-annot-outline">
<h4 class="heading-s" id="training-material">Training material</h4>
<p>For our A11Y Champion Training we offer the following materials:</p>
<ul class="list-icons list-linklist" aria-labelledby="training-material">
<li><a href="index.html">Lessons pages</a></li>
<li><a href="index.html">Specials</a></li>
<li><a href="index.html">Good / Bad site</a></li>
<li><a href="index.html">Quiz questions</a></li>
<li><a href="index.html">Deque University</a></li>
</ul>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal10">10</button>
</div>
<h3 class="heading-l annot-relative btn-annot-outline">What we deliver for accessibility <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal06">06</button></h3>
<p class="annot-relative btn-annot-outline">By simplifying <a href="index.html"><abbr title="accessibility">A11Y</abbr> guidelines</a> with <a href="index.html">easy checklists</a>, <span class="annot-relative btn-annot-outline"><a href="index.html">hands on examples</a> <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal12">12</button></span> and with proper <span class="annot-relative btn-annot-outline"><a href="index.html">training material</a> <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal12">12</button></span> we give you a head start. <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal11">11</button></p>
<p>On a strategic level we elaborate what is necessary at which stage for the life cycles of all different company dimensions like development, procurement, testing and more.</p>
<h4 class="heading-s">Add these steps to your <abbr class="annot-relative btn-annot-outline" title="Definition of Done">DoD <button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal05">05</button></abbr></h4>
<div class="annot-relative btn-annot-outline">
<ol aria-label="Add these steps to your Definition of Done">
<li>Persona's used</li>
<li>Standards followed</li>
<li>User tests done</li>
<li>WCAG 2.0 AA compliant</li>
</ol>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal10">10</button>
</div>
<p>By adding these steps to your <span class="annot-relative btn-annot-outline"> Definition of Done<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal13">13</button></span> (<abbr class="annot-relative btn-annot-outline" title="Definition of Done">DoD<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal05">05</button></abbr>) it will be easier to secure accessibility in your process.</p>
<p>Interested in knowing more about accessibility? Let us know and we will visit you!</p>
<span class="d-block mt-2">
<a href="index.html" class="link-primary">
Presentation on location
</a>
</span>
</div>
<div class="col-md-5 col-lg-4">
<div class="card mb-4">
<div class="card-block">
<h3 class="card-title" id="responsibilities">Content Best Practices</h3>
<ul class="list-icons list-checklist m-0 mt-2" aria-labelledby="responsibilities">
<li>Avoid unnecessary words</li>
<li>Reduce to its essence</li>
<li>Avoid slang and informal jargon</li>
<li>Use active rather than passive phrases</li>
<li>Use direct commands where appropriate</li>
<li>Identify and define pronunciations</li>
</ul>
<a href="http://a11y.ing.net" class="link-primary mt-2">
<abbr title="accessibility">A11Y</abbr> for Content Contributors
</a>
</div>
</div>
<div class="card mb-4 btn-annot-outline">
<div class="card-block">
<h3 class="card-title">Text align left</h3>
<p>Centered and left aligned text are the most widely used text alignments.</p>
<p class="m-0"> How you use these text alignments can either help or harm your users when they read.</p>
<a href="https://www.w3.org/WAI/WCAG20/quickref/?showtechniques=31#meaning" class="link-primary mt-4">Guideline 3.1 – Readable</a>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal14">14</button>
</div>
</div>
<div class="card mb-4 btn-annot-outline">
<div class="card-block">
<h3 class="card-title">Text justification</h3>
<p>Avoiding text that is fully justified (to both left and right margins) in a way that causes poor spacing between words or characters.</p>
<p class="m-0">Using left-justified text for languages that are written left to right and right-justified text for languages that are written right-to-left.</p>
<a href="https://www.w3.org/TR/WCAG20-TECHS/F88.html" class="link-primary mt-4">F88: WCAG Failure</a>
<button type="button" class="btn btn-annot" data-toggle="modal" data-target="#annotModal15">15</button>
</div>
</div>
</div>
</div>
</div>
</article>
</main>
<footer class="full-cover site-footer bg-grey" role="contentinfo">
<div class="container text-center">
<div class="d-inline-block annot-relative">
<ul class="pipe-links list-inline mt-2" aria-label="footer links">
<li class="list-inline-item">
<a href="index.html">About <abbr title="accessibility">A11Y</abbr></a>
</li>
<li class="list-inline-item">
<a href="index.html">Universal Design</a>
</li>
<li class="list-inline-item">
<a href="index.html">Privacy en cookies</a>
</li>
<li class="list-inline-item">
<a href="index.html">Disclaimer</a>
</li>
<li class="list-inline-item">
<a href="index.html">Accessibility</a>
</li>
</ul>
</div>
</div>
<div class="footer-copyright py-2">
<p class="m-0">© 2017 Copyright</p>
</div>
</footer>
<div class="modal fade" id="a11ycasts" tabindex="-1" role="dialog" aria-labelledby="a11ycastsHeading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="a11ycastsHeading">Introducing A11ycasts! -- A11ycasts #01</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<iframe width="100%" class="modal-youtube" src="https://www.youtube.com/embed/HtTyRajRuyY?ecver=1" frameborder="0" allowfullscreen></iframe>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<section class="full-cover bg-faded annotations" role="region" aria-labelledby="annotationsSection">
<div class="container">
<h2 class="full-cover-title" id="annotationsSection">Annotations</h2>
<div class="modal fade modal-annot" id="annotModal01" tabindex="-1" role="dialog" aria-labelledby="annotModal01Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal01Heading">01. Content provides a logical and hierarchical heading structure</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>A good heading structure enables people to scan a page/screen quickly and understand the structure of the content. Screen reader users can also use headings to quickly navigate within a page or screen.</p>
<p>Other things to consider, in order to make headings more usable for screen reader users:</p>
<ul>
<li>Lists and headings used together to mark up content should be avoided</li>
<li>For a correct heading outline it is sometimes necessary to hide them visually</li>
<li>Headings should be coded around content that doesn’t change, i.e. a category name such as ‘Banking News’ rather than a news item that will update frequently</li>
<li>Headings should not overwhelm a page as this can undermine their usefulness for screen reader users when navigating, a maximum of 7-9 headings should suffice</li>
</ul>
<div class="alert alert-info">
<p>
<strong>Note!</strong> Improvements on the template are propagated throughout the entire website
</p>
</div>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<h1>Accessible Article Page</h1>
<h2>Why we promote accessibility</h2>
<h2>How we strive for accessibility</h2>
<h3>Training material</h3>
<h2>What we deliver for accessibility</h2>
<h3>Add these steps to your DoD</h3>
...
<!-- Optional hidden heading -->
<h2 class="sr-only">Selected for you</h2>
<h3>...</h3>
<h4>...</h4>
...
<!-- Optional with ARIA -->
<div role="heading" aria-level="2">...</div>
<div role="heading" aria-level="3">...</div>
...
</code>
</pre>
<h4 class="heading-s">WCAG Success Criteria</h4>
<ul class="list-group list-group-lessons">
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation-programmatic">1.3.1 Info and Relationships Level A</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/H42">H42: Using h1-h6 to identify headings</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G141">G141: Organizing a page using headings</a></li>
</ul>
</div>
</li>
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#navigation-mechanisms-headings">2.4.10 Section Headings Level AAA</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G141">G141: Organizing a page using headings</a></li>
<li><a href="http://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H69">H69: Providing heading elements at the beginning of each section of content</a></li>
</ul>
</div>
</li>
</ul>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal02" tabindex="-1" role="dialog" aria-labelledby="annotModal02Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal02Heading">02. Correct use of lead paragraph</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>Under the main heading <code><h1></code> a paragraph is present with a <code>class="lead"</code>. Although the text is bigger than the body text a paragraph provides good context in the document ouline opposed to placing another heading (stand alone <code><h1></code> without content) underneath the <code><h1></code>.</p>
<div class="alert alert-info">
<strong>Note!</strong> Improvements on the template are propagated throughout the entire website
</div>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<h1>Accessible Article Page</h1>
<p class="lead">Good and Bad Demonstration</p>
</code>
</pre>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal03" tabindex="-1" role="dialog" aria-labelledby="annotModal03Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal03Heading">03. Links are Links and Buttons are Buttons</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>How to choose between a link and a button:</p>
<ol>
<li>Will this control be used to initiate an immediate action? It’s a button!</li>
<li>Is the action to navigate to another page? It’s a link!</li>
</ol>
<p>General guidelines on making the choice:</p>
<ul>
<li>Use command buttons for:
<ul>
<li>Primary commands</li>
<li>Displaying windows used to gather input or making choices, even if they are secondary commands</li>
<li>Destructive or irreversible actions, as well as commitment within wizards and page flows</li>
</ul>
</li>
<li>Use links for navigation to another page, window, or Help topic; display definitions; and command menus</li>
</ul>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
Go to other page:
<!-- Link in code and link styling, goes to other page -->
<a href="index.html" class="link-primary">More on Expert</a>
Staying on same page:
<!-- Button in code and button styling, stays on page -->
<button type="button" class="btn btn-primary">Watch the video</button>
</code>
</pre>
<h4 class="heading-s">WCAG Success Criteria</h4>
<ul class="list-group list-group-lessons">
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation-programmatic">1.3.1 Info and Relationships Level A</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G115.html">G115: Using semantic elements to mark up structure</a></li>
</ul>
</div>
</li>
</ul>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal04" tabindex="-1" role="dialog" aria-labelledby="annotModal04Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal04Heading">04. Max width of links, lists, input fields and paragraphs</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>Links, lists, input fields and paragraphs will have a max width of 600 CSS pixels to keep everything readable. Selects, text fields, radio buttons, checkboxes etc are considered input fields. Note that the max label width is often a bit smaller, as lots of components have elements that take in space as well, for instance, the actually checkbox in a checkbox component.</p>
<p>For those who are into the subject of readability, we know this is in the upper regions of an ideally desired max length. So this means that in a card of let’s say 800px the width of a paragraph or input field label will never be larger than 600px. So yes, that means white space at some point.</p>
<div class="alert alert-info">
<strong>Note!</strong> The max label width is often a bit smaller, as lots of components have elements that take in space as well, for instance, the actually checkbox in a checkbox component.
</div>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<!-- HTML -->
<p>The social model of disability...</p>
<!-- CSS -->
p { max-width: 580px; }
ol, ul, dl { max-width: 580px; }
a { max-width: 580px; }
input, .form-control { max-width: 580px; }
</code>
</pre>
<h4 class="heading-s">WCAG Success Criteria</h4>
<ul class="list-group list-group-lessons">
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-scale">1.4.4 Resize text Level AA</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/C20.html">C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized</a></li>
</ul>
</div>
</li>
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-visual-presentation">1.4.8 Visual Presentation Level AAA</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/C20.html">C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized</a></li>
</ul>
</div>
</li>
</ul>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal05" tabindex="-1" role="dialog" aria-labelledby="annotModal05Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal05Heading">05. Accessibility and DoD are spelt out in full</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>Accessibility and Dod are spelt out in full the first time on the page and acronyms in general are avoided as much as possible. The objective of this technique is to provide expansions or definitions for abbreviations by using the abbr element.</p>
<div class="alert alert-info">
<p>
<strong>Note!</strong> It is always appropriate to use the <code><abbr></code> element for any abbreviation, including acronyms and initialisms. When using HTML 4 and XHTML, initialisms and acronyms may be marked up using the acronym element. In HTML5 and newer versions of HTML the acronym element was marked as obsolete in favor of the more general <code><abbr></code> element.
</p>
</div>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<p>Team Accessibility (Team <abbr title="accessibility">A11Y</abbr>)...</p>
<p>Definition of Done (<abbr title="Definition of Done">DoD</abbr>)...</p>
</code>
</pre>
<h4 class="heading-s">WCAG Success Criteria</h4>
<ul class="list-group list-group-lessons">
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#meaning-located">3.1.4 Abbreviations Level AAA</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/H28.html">H28: Providing definitions for abbreviations by using the abbr element</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G102">G102: Providing the expansion or explanation of an abbreviation</a></li>
</ul>
</div>
</li>
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#meaning-supplements">3.1.5 Reading Level Level AAA</a>
<ul>
<li>Advisory Technique: Using the clearest and simplest language appropriate for the content</li>
</ul>
</div>
</li>
</ul>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal06" tabindex="-1" role="dialog" aria-labelledby="annotModal06Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal06Heading">06. Headings describe topic or purpose.</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>Descriptive headings identify sections of the content in relation both to the Web page as a whole and to other sections of the same Web page. Descriptive headings help users find specific content and orient themselves within the Web page.</p>
<div class="alert alert-info">
<p>
<strong>Note!</strong> Users of assistive technology like screen reader use headings as a primary way of navigating. This is often done by a heading lists. Descriptive headings provide a good way of identifying what can be found in the paragraph following the heading.
</p>
</div>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<h3>Why we promote accessibility</h3>
<h3>How we strive for accessibility</h3>
<h3>What we deliver for accessibility</h3>
</code>
</pre>
<h4 class="heading-s">WCAG Success Criteria</h4>
<ul class="list-group list-group-lessons">
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#navigation-mechanisms-descriptive">2.4.6 Headings and Labels Level AA</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G130.html">G130: Providing descriptive headings</a></li>
</ul>
</div>
</li>
</ul>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal07" tabindex="-1" role="dialog" aria-labelledby="annotModal07Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal07Heading">07. Emphasized text marked up as such using structure to convey semantic meaning</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>The text "digital equality is a human right" is emphasized using the <code><strong></code> element. The <code><figcaption></code> elements is emphasized using the <code><em></code> element.</p>
<div class="alert alert-info">
<p><strong>Note!</strong> Semantic mark-up such as <code><strong></code>, <code><em></code>, etc. should be used over purely visual formatting using CSS to indicate meaningful aspects such as text formatting. Additionally, structures such as lists, and headings should be used to indicate relationships of items.</p>
<p>As the <code><b></code> (bold) and <code><i></code> (italic) elements are both only styling elements we should avoid using those as they don't convey programmatic meaning / additional importance.</p>
</div>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<strong>digital equality is a human right</strong>
<figcaption><em>Four people in a room...</em></figcaption>
</code>
</pre>
<h4 class="heading-s">WCAG Success Criteria</h4>
<ul class="list-group list-group-lessons">
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation-programmatic">1.3.1 Info and Relationships Level A</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G115">G115: Using semantic elements to mark up structure</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/H49">H49: Using semantic markup to mark emphasized or special text</a></li>
</ul>
</div>
</li>
</ul>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal08" tabindex="-1" role="dialog" aria-labelledby="annotModal08Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal08Heading">08. Links with distinctive appearance and communicating function</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>Links have a distinctive appearance using icons, the functional icon name and the non-color cues: underline and "open in new window" icon. The functional icon has a WAI-ARIA role of image and descriptive accessible name.</p>
<div class="alert alert-info">
<p><strong>Note!</strong> Opening pages in a new tab / window is higly discouraged whenever possible. The best practice for all links is to stay in the same tab / window as lots of people don't know what browser tabs are, have no idea pages open in new tabs and can't figure out why the back button doesn't work. This is even more often experienced on mobile.</p>
<p>Opening new windows automatically when a link is activated can be disorienting for people who have difficulty perceiving visual content, and for some people with cognitive disabilities, if they are not warned in advance.</p>
<p>When the choice is to open links in a new window all users must be informed of this function. Also users who use screen readers / assistive technology.</p>
</div>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<a href="index.html" target="_blank">
An Alphabet of Accessibility Issues
<span class="icon" role="img" aria-label="Opens in new window"></span>
</a>
</code>
</pre>
<h4 class="heading-s">WCAG Success Criteria</h4>
<ul class="list-group list-group-lessons">
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#text-equiv-all">1.1.1 Non-text Content Level A</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G94.html">G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/ARIA6.html">ARIA6: Using aria-label to provide labels for objects</a></li>
</ul>
</div>
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation-programmatic">1.3.1 Info and Relationships Level A</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/C22.html">C22: Using CSS to control visual presentation of text</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G115">G115: Using semantic elements to mark up structure</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G140">G140: Separating information and structure from presentation to enable different presentations</a></li>
</ul>
</div>
</li>
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-visual-presentation">1.4.8 Visual Presentation Level AAA</a>
<ul>
<li>Advisory Technique: Making links visually distinct</li>
</ul>
</div>
</li>
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/consistent-behavior.html">Predictable: Understanding Guideline 3.2</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G201.html">G201: Giving users advanced warning when opening a new window</a></li>
</ul>
</div>
</li>
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/tutorials/images/functional/">Functional Images - Web Accessibility Tutorials - WAI</a>
</div>
</li>
</ul>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal09" tabindex="-1" role="dialog" aria-labelledby="annotModal09Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal09Heading">09. Figure element with proper role and label</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>The picture of the "Empathy Lab" is considered informative, so a text alternative has been provided and the picture is also placed in a <code><figure></code> element to briefly describe the image visually in text.</p>
<div class="alert alert-info">
<p><strong>Note!</strong> The WAI-ARIA <code>role="group"</code> attribute with the value of group is used to indicate grouping to assistive technologies, <code>aria-labelledby</code> makes sure that the figcaption elements are used as labels for the individual groups. The web browser and assistive technology support vary for this particular WAI-ARIA attribute and value.</p>
</div>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<figure role="group" aria-labelledby="figcaption">
<img src="/planning.jpg" alt="People in the ING Emphathy Lab">
<figcaption id="figcaption">
<em>Four people in a room at desks...</em>
</figcaption>
</figure>
</code>
</pre>
<h4 class="heading-s">WCAG Success Criteria</h4>
<ul class="list-group list-group-lessons">
<li class="list-group-item">
<div class="w-100">
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/ARIA13">ARIA13: Using aria-labelledby to name regions and landmarks</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G196">G196: Using a text alternative on one item within a group of images that describes all items in the group</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/H67">H67: Using null alt text and no title attribute on img elements for images that AT should ignore</a></li>
</ul>
</div>
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/tutorials/images/groups/">Groups of Images - Web Accessibility Tutorials - WAI</a>
</div>
</li>
</ul>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal10" tabindex="-1" role="dialog" aria-labelledby="annotModal10Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal10Heading">10. Lists marked up as such and given an accessible name</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>These lists are marked up using an HTML list structure.</p>
<p>Extending on the "4.1.2 Name, Role, Value" success criteria it's a best practice to provide a name for each list so people using a screen reader can distinguish the lists on the page</p>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<!-- Accessible name via aria-labelledby -->
<h4 class="heading-s" id="training-material">Training material</h4>
<p>For our...</p>
<ul aria-labelledby="training-material">
<li><a href="index.html">Lessons pages</a></li>
<li><a href="index.html">Specials</a></li>
<li><a href="index.html">Good / Bad site</a></li>
<li><a href="index.html">Quiz questions</a></li>
<li><a href="index.html">Deque University</a></li>
</ul>
<!-- Accessible name via aria-label -->
<ol aria-label="Add these steps to your Definition of Done">
<li>Persona's used</li>
<li>Standards followed</li>
<li>User tests done</li>
<li>WCAG 2.0 AA compliant</li>
</ol>
</code>
</pre>
<h4 class="heading-s">WCAG Success Criteria</h4>
<ul class="list-group list-group-lessons">
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation-programmatic">1.3.1 Info and Relationships Level A</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G140">G140: Separating information and structure from presentation to enable different presentations</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/H48">H48: Using ol, ul and dl for lists or groups of links</a></li>
</ul>
</div>
</li>
<li class="list-group-item">
<div class="w-100">
<a href="https://www.w3.org/WAI/WCAG20/quickref/#ensure-compat-rsv">4.1.2 Name, Role, Value Level A</a>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/ARIA14.html">ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/ARIA16.html">ARIA16: Using aria-labelledby to provide a name for user interface controls</a></li>
</ul>
</div>
</li>
</ul>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="text-right">
<a href="#totop">To Top</a>
</div>
<div class="modal fade modal-annot" id="annotModal11" tabindex="-1" role="dialog" aria-labelledby="annotModal11Heading">
<div class="modal-dialog modal-lg" role="document">
<div class="modal-content">
<div class="modal-header">
<h3 class="modal-title" id="annotModal11Heading">11. Link text visually distinct from its surrounding</h3>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<p>The links uses color and a border bottom that is distinct from the surrounding text to make it easier to identify the link. Hovering over the link makes the border bottom disappear.</p>
<h4 class="heading-s">HTML Example</h4>
<pre class="highlight">
<code class="html">
<!-- HTML -->
<p>By simplifying <a href="index.html">A11Y guidelines</a> with <a href="index.html">easy checklists</a>...</p>
<!-- CSS -->
p { color: #333333; }
a {