This repository has been archived by the owner on Jan 25, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
/
Copy pathImplementations-by-feature.html
1104 lines (1098 loc) · 87.2 KB
/
Implementations-by-feature.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
<!--?xml version="1.0" encoding="utf-8"?-->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<title>UAAG 2.0 Implementations by Feature</title>
<link rel="stylesheet" href="http://www.w3.org/WAI/wai-main.css" type="text/css" />
<!--[if IE 7]><link rel="stylesheet" href="/WAI/ie-old.css" type="text/css" media="all" /><![endif]-->
<style type="text/css">
table {
border-collapse:collapse;
}
th, td {
border: 1px solid black;
vertical-align:top;
}
.editor-notes {
border: 1px solid red;
}
.proposed-text: {
background-color: #FFCCFF !important;
}
.editorial {
background-color:#F9F
}
.not-addressed {
background-color:#C00
}
.under-discussion {
background-color: #CF0
}
.done {
background-color:#060;
color:#FFF
}
tr.header {
background-color: #FFFF00;
}
tr.h1 {
background-color: #FF9933;
}
tr.h2 {
background-color: #99FF99;
}
tr.h3 {
background-color: #CCFFFF;
}
tr.h1 td.whole-line, tr.h2 td.whole-line {
font-style: bold;
}
.proposed-text {
BACKGROUND-COLOR:#FFCCFF !important;
}
.summary {
padding: 1em;
font-weight:200;
color:#000000;
background-color:#FFFFFF;
border:thin solid #666666;
}
.summary1 { margin: .5em;
padding: 1em;
font-weight:200;
color:#000000;
background-color:#FFFFFF;
border:thin solid #666666;
}
table { border-collapse:collapse; }
th, td {border: 1px solid black; vertical-align:top;}
.editor-notes { border: 1px solid red; }
.proposed-text: { background-color: #FFCCFF !important; }
tr.header { background-color: #FFFF00; }
tr.h1 { background-color: #FF9933; }
tr.h2 { background-color: #99FF99; }
tr.h3 { background-color: #CCFFFF; }
tr.h4 { background-color: #CCCFFF; }
tr.h1 td.whole-line, tr.h2 td.whole-line { font-style: bold; }
.dfn-instance { border-bottom:1px dotted #585858;
color:#000000 !important;
text-decoration:none;
}
</style>
<!-- Copyright 2000, 2001, 2002, 2003 Macromedia, Inc. All rights reserved. -->
<!-- Copyright 2000, 2001, 2002, 2003 Macromedia, Inc. All rights reserved. -->
<!-- Copyright 2000, 2001, 2002, 2003 Macromedia, Inc. All rights reserved. -->
<!-- Copyright 2000, 2001, 2002, 2003 Macromedia, Inc. All rights reserved. -->
</head>
<body>
<div id="controls">
<ul>
<li><a href="#skip" shape="rect"><img src="/Icons/downinpage.png" alt="" /> Skip to Content </a></li>
<li><a href="/WAI/changedesign.html" shape="rect"> | Change
text size or colors </a> </li>
</ul>
</div>
<div id="masthead">
<p id="logos"><a href="http://www.w3.org/" title="W3C Home" shape="rect"><img alt="W3C logo" src="/Icons/w3c_home" /></a><a href="http://www.w3.org/WAI/" title="WAI Home" shape="rect"><img alt="Web Accessibility initiative" src="/WAI/images/wai-temp" /></a></p>
</div>
<div id="tagline">
<p>WAI: Strategies, guidelines, resources to make the
Web accessible to people with disabilities</p>
</div>
<p><strong>Site Navigation: <a href="http://www.w3.org/">W3C Home</a> > <a href="http://www.w3.org/WAI/">WAI Home</a> > <a href="http://www.w3.org/WAI/UA/">UAWG Home</a></strong> > <a href="index.html"><strong>UAAG Implementations</strong></a></p>
<div id="skipwrapper"> <a id="skip" shape="rect">-</a></div>
<div>
<h1>UAAG 2.0 Identified Implementations Report Detail: Feature by Feature</h1>
<p>Examples of each success criteria informally identified by members of the User Agent Accessibility Guidelines Working Group, but not formally tested. </p>
<dl>
<dt>Updated: </dt>
<dd>22 December 2015</dd>
<dt>This Version (Github)</dt>
<dd><a href="http://w3c.github.io/UAAG-Implementations/Implementations-by-feature">http://w3c.github.io/UAAG-Implementations/Implementations-by-feature</a></dd>
</dl>
<h2>Status</h2>
<p>This report from the <a href="http://w3.org/WAI/UA/">User Agent Accessibility Guidelines Working Group (UAWG)</a> was initially started in anticipation of implementation testing during an anticipated W3C Candidate Recommendation stage for the <a href="http://www.w3.org/TR/UAAG20/">User Agent Accessibility Guidelines</a> (UAAG) 2.0.<br />
<br />
This report identifies implementations of User Agent Accessibility Guidelines (UAAG) 2.0 success criteria based on informal evaluation of these features in a variety of user agents. Even though this stage of work on UAAG 2.0 concluded with a Working Group Note instead of a W3C Recommendation, the Working Group continued to identify candidate implementations of UAAG 2.0 features, as these may be useful examples for other potential implementers to consider. The more consistent the support of basic accessibility is across browsers, media players, and other user agents, the greater access people with disabilities have to Web content that has been made accessible by conforming to the Web Content Accessibility Guidelines (WCAG) 2.0. <br />
<br />
Because the implementations listed below have not been definitively tested, they should not be considered as confirmation of conformance. Those interested in further testing of candidate implementations may be interested in the <a href="https://www.w3.org/WAI/UA/work/wiki/Tests_for_CR">draft UAAG 2.0 test suite</a> which is publicly available. Please let us know if you have any questions. </p>
<p>If the block is <strong>blank</strong>, it means that UAWG has not yet discussed it. </p>
<p>Success criteria: 112<br />Success criteria w/ zero implementations: 3 <br />
Success criteria with one implementation: 8<br />
Percentage implemented with two identified examples: 90.1%
</p>
<p>See also: <br />
<a href="http://www.w3.org/TR/2015/NOTE-UAAG20-20151215/">UAAG 2.0 Working Group Note</a><br />
<a href="http://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/">UAAG 2.0 Reference Working Group Note</a><a href="http://www.w3.org/TR/2013/WD-UAAG20-20131107/"></a><br />
<a href="https://www.w3.org/WAI/UA/work/wiki/Tests_for_CR">UAAG 2.0 Tests for CR Overview</a> </p>
<h2>Implementations</h2>
<p> </p>
<table width="100%">
<tr class="header">
<th> </th>
<th>Success Criteria</th>
<th>Priority</th>
<th>Implementation 1</th>
<th>Implementation 2</th>
</tr>
<tr class="h3">
<td class="line-number">16</td>
<td class"whole-line"><p><strong class="title"> 1.1.1 Render Alternative Content:</strong> The user can choose to render any type of recognized alternative content that is present for a content element. (Level A) </p>
<p> <strong class="title">Note:</strong> It is recommended that the user agent allow the user to choose whether the alternative content replaces or supplements the original content element.</p></td>
<td class="pri">A</td>
<td class="pri"><p>https://www.w3.org/WAI/UA/work/wiki/Appendix_E:_Alternative_Content</p>
<p>Abbreviations</p>
<ul>
<li>http://firefox.cita.illinois.edu/txtequiv/expandabbr.php</li>
</ul>
<p> </p>
<p>ClickToPlugin - safari <a rel="nofollow" href="http://hoyois.github.io/safariextensions/clicktoplugin/">http://hoyois.github.io/safariextensions/clicktoplugin/</a></p>
<p>Chrome londesc </p>
<ul>
<li>https://chrome.google.com/webstore/detail/longdesc/haohljalgapbacpkfefnmhiadanhejmb</li>
<li>https://chrome.google.com/webstore/detail/longdesc/apfomgoblcegnecnacnjdpaemlddlkdb</li>
</ul>
<p> </p></td>
<td class="pri"><p>Image Alt Text Viewer </p>
<ul>
<li>https://chrome.google.com/webstore/detail/image-alt-text-viewer/hinbolcnfifkhlcehoakdledkfjiaeeg </li>
</ul>
<p>Firefox - Long Descriptions https://addons.mozilla.org/en-US/firefox/addon/longdesc/</p>
<p> </p></td>
</tr>
<tr class="h3">
<td class="line-number">18</td>
<td class"whole-line"><strong class="title">1.1.2 Indicate Unrendered Alternative Content:</strong> The user can specify that indicators be displayed along with rendered content when recognized unrendered alternative content is present. (Level A)</td>
<td class="pri">A</td>
<td class="pri"><p>media players - Youtube player https://www.youtube.com/watch?v=9K4WJs94FfY youtube with captions CC button is not grayed out<br />
https://www.youtube.com/watch?v=oe30habM0ls youtube with no captions no CC button </p></td>
<td class="pri">A user stylesheet in any browser supporting user stylesheets: [Greg will send a link to his stylesheet]</td>
</tr>
<tr class="h3">
<td class="line-number">19</td>
<td class"whole-line"><strong class="title">1.1.3 Replace Non-Text Content:</strong> The user can request a placeholder that incorporates recognized text alternative content instead of recognized non-text content, until explicit user request to render the non-text content. (Level A) </td>
<td class="pri">A</td>
<td class="pri"><p>images<br />
Firefox, Chrome, IE, Opera, Safari </p>
<p><a href="https://support.mozilla.org/en-US/questions/981640">Instructions for disabling images in FF</a><br />
</p></td>
<td class="pri"><p><a href="http://smallbusiness.chron.com/turn-off-images-internet-explorer-49962.html">
<!-- MENU-LOCATION=NONE -->
</a>IE</p>
<p><a href="http://smallbusiness.chron.com/turn-off-images-internet-explorer-49962.html">Instructions for disabling images in IE</a></p></td>
</tr>
<tr class="h3">
<td class="line-number">20</td>
<td class"whole-line"><p><strong class="title">1.1.4 Facilitate Clear Display of Alternative Content for Time-based Media:</strong> For recognized on-screen alternative content for time-based media (e.g. captions, sign language video), the following are all true: (Level A)<br/>
a.
Don't obscure controls: Displaying time-based media alternatives doesn't obscure recognized controls for the primary time-based media.<br/>
b.
Don't obscure primary media: The user can specify that displaying time-based media alternatives doesn't obscure the primary time-based media. </p>
<p><strong class="title">Note:</strong> Depending on the screen area available, the display of the primary time-based media can need to be reduced in size to meet this requirement. </p></td>
<td class="pri">A</td>
<td class="pri"><p>media player settings</p>
<p>A & B. quicktime</p></td>
<td class="pri">html5 vido caption placement - CSS https://developer.mozilla.org/en-US/Apps/Build/Audio_and_video_delivery/Adding_captions_and_subtitles_to_HTML5_video</td>
</tr>
<tr class="h3">
<td class="line-number">22</td>
<td class"whole-line"><strong class="title"> 1.1.5 Provide Configurable Alternative Content Defaults:</strong> The user can specify which type(s) of alternative content to render by default for each type of non-text content, including time based media. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri"><p>media players let the user choose to display captions with video
</p>
<p>Extensions that do this:<br />
Webdeveloper toolbar http://chrispederick.com/work/web-developer/</p>
<p>http://www.howtogeek.com/139916/how-to-view-and-disable-installed-browser-plug-ins-in-any-browser/</p>
<p>http://www.howtogeek.com/188059/how-to-enable-click-to-play-plugins-in-every-web-browser/</p></td>
<td class="pri"><p> </p></td>
</tr>
<tr class="h3">
<td class="line-number">23</td>
<td class"whole-line"><strong class="title">1.1.6 Use Configurable Text for Time-based Media Captions:</strong> For recognized on-screen alternative content for time-based media (e.g. captions, sign language video), the user can configure recognized text within time-based media alternatives (e.g. captions) in conformance with 1.4.1. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri"><p>User stylesheet can be used to configure the caption text in any browser that supports user stylesheets</p>
<p> </p></td>
<td class="pri">User stylesheet can be used to configure the caption text in any browser that supports user stylesheets</td>
</tr>
<tr class="h3">
<td class="line-number">24</td>
<td class"whole-line"><p><strong class="title"> 1.1.7 Allow Resize and Reposition of Time-based Media Alternatives:</strong> The user can configure recognized alternative content for time-based media (e.g. captions, sign language video) as follows: (Level AAA)<br/> * Resize: The user can resize alternative content for time-based media to at least 50% of the size of the top-level viewports.<br/> * Reposition: The user can reposition alternative content for time-based media to two or more of the following: above, below, to the right, to the left, and overlapping the primary time-based media.</p>
<p><strong class="title">Note 1:</strong> Depending on the screen area available, the display of the primary time-based media can need to be reduced in size or hidden to meet this requirement. </p>
<p><strong class="title">Note 2:</strong> Implementation can involve displaying alternative content for time-based media in a separate viewport, but this is not required. </p></td>
<td class="pri">AAA</td>
<td class="pri">youtube - captions on top or bottom of video<br />
http://www.whooshtranscription.com/how-to-set-the-position-of-subtitles-on-youtube/<br /></td>
<td class="pri">vlc player - captions/subtitles<br />
https://wiki.videolan.org/Documentation:Subtitles/</td>
</tr>
<tr class="h3">
<td class="line-number">29</td>
<td class"whole-line"><strong class="title"> 1.2.1 Support Repair by Assistive Technologies:</strong> If text alternatives for non-text content are missing or empty, the user agent doesn't attempt to repair the text alternatives by substituting text values that are also available to assistive technologies (e.g. image file name). (Level AA)</td>
<td class="pri">AA</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari </td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari </td>
</tr>
<tr class="h3">
<td class="line-number">32</td>
<td class"whole-line"><strong class="title"> 1.3.1 Distinguishable Highlighting:</strong> The user can have the following types of content uniquely highlighted, overriding any values specified by the author: (Level A)<br/>
a. Selection<br/>
b. In-page search results<br/>
c.
Active keyboard focus (indicated by focus cursors and/or text cursors)<br/>
d. Unvisited links<br/>
e. Visited links </td>
<td class="pri">A</td>
<td class="pri">a,b,c,e: Firefox, IE, Opera, Safari; <br>
d: extension Opera (Chaals extension) </td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">33</td>
<td class"whole-line"><strong class="title"> 1.3.2 Highlighting Options:</strong> The user can set all of the following characteristics of selection highlighting, overriding any values specified by the author: (Level AA)<br/> * Foreground color<br/> * Background color</td>
<td class="pri">AA</td>
<td class="pri">Firefox, IE, Opera, Safari </td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">34</td>
<td class"whole-line"><strong class="title">1.3.3 Highlighting Active Keyboard Focus:</strong> The user can set all of the following characteristics of active keyboard focus highlighting, overriding any values specified by the author: (Level AA)<br/> * Foreground color<br/> * Background color<br/> * Border (color, style, and thickness)<br/> * Text cursor blink rate</td>
<td class="pri">AA</td>
<td class="pri"> extension Stylish works on chrome, ff, safari, opera</td>
<td class="pri">extension Stylish works on chrome, ff, safari, opera</td>
</tr>
<tr class="h3">
<td class="line-number">35</td>
<td class"whole-line"><strong class="title">1.3.4 Distinguishing Enabled Elements:</strong> The user can set all of the following characteristics of enabled element highlighting, overriding any values specified by the author: (Level AA)<br/> * Foreground color<br/> * Background color<br/> * Border (color, style, and thickness)</td>
<td class="pri">AA</td>
<td class="pri">Firefox, IE, Opera, Safari - user stylesheets</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">36</td>
<td class"whole-line"><strong class="title">1.3.5 Distinguishing Enabled Elements:</strong> The user can set all of the following characteristics for visited links and separately for unvisited links, overriding any values specified by the author: (Level AA)<br/> * Foreground color<br/> * Underline</td>
<td class="pri">AA</td>
<td class="pri">Firefox - settings</td>
<td class="pri">IE settings</td>
</tr>
<tr class="h3">
<td class="line-number">41</td>
<td class"whole-line"><strong class="title"> 1.4.1 Basic text formatting (Globally):</strong> The user can globally set all of the following characteristics of visually rendered text content: (Level A)<br/> * Text scale with preserved size distinctions (e.g. keeping headings proportional to main font)<br/> * Text color and background color, choosing from all platform color options<br/> * Font family, choosing from all installed fonts<br/> * Line spacing, choosing from a range with at least three values up to at least 2 times the default<br/> * Text style, choosing to turn on/off underline, italic, bold</td>
<td class="pri">A</td>
<td class="pri"><p>a,b,c - Firefox, IE, Opera, Safari (user style sheets)</p>
<p>stylish - https://addons.mozilla.org/en-US/firefox/addon/stylish/?src=search</p></td>
<td class="pri">stylish - https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe</td>
</tr>
<tr class="h3">
<td class="line-number">42</td>
<td class"whole-line"><strong class="title"> 1.4.2 Basic text formatting (by Element):</strong> The user can set all of the following characteristics of visually rendered text content for text element types including at least headings, input fields, and links: (Level AA)<br/> * Text size (e.g. 18 point) or scale (e.g. 150%)<br/> * Text color and background color, choosing from all platform color options<br/> * Font family, choosing from at least all installed fonts<br/> * Line spacing, choosing from a range with at least three values<br/> * Text style (underline, italic, bold)</td>
<td class="pri">AA</td>
<td class="pri">Firefox, IE, Opera, Safari - user style sheet</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">43</td>
<td class"whole-line"><strong class="title">1.4.3 Blocks of text (Globally):</strong> The user can globally set all of the following characteristics of visually rendered blocks of text: (Level AA)<br/> * Character spacing, choosing from a range with at least 5 values<br/> * Justification (left or right, including turning off full justification)<br/> * Margins around blocks of text</td>
<td class="pri">AA</td>
<td class="pri">Firefox, IE, Opera, Safari - user style sheet</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">44</td>
<td class"whole-line"><strong class="title">1.4.4 Configured and Reflowed Text Printing:</strong> The user can print the rendered content, and the following are all true: (Level AA)<br/> * any visual, non-time-based, rendered content can be printed<br/> * the user can choose between available printing devices<br/> * the user can have content printed as it is rendered on screen, reflecting any user scaling, highlighting, and other modifications<br/> * the user can have printed content reflow as if the top-level viewports had been resized to match the horizontal dimension of the printing device's printable area</td>
<td class="pri">AA</td>
<td class="pri"><p>directions for using the debugger in Chrome to print the rendered view.<br />
<a href="https://superuser.com/questions/456700/how-do-i-print-with-the-screen-stylesheet">https://superuser.com/questions/456700/how-do-i-print-with-the-screen-stylesheet</a></td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">45</td>
<td class"whole-line"><strong class="title">1.4.5 Default to platform text settings:</strong> The user can specify that platform text settings be used as the default values for text configuration.. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri">Many examples of high contrast settings carrying over from OS to the browser.
<!-- MENU-LOCATION=NONE -->But we couldn't find OS text configuration settings that carried over to the browser. May need more research</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">46</td>
<td class"whole-line"><p><strong class="title"> 1.4.6 Advanced text formatting:</strong> The user can globally set all of the following characteristics of visually rendered blocks of text: (Level AAA)<br/> * Capitalization (overriding upper case and small caps style)<br/> * Word-breaking properties (e.g. auto-hyphenation)<br/> * Borders<br/> * Word spacing (choosing from a range of at least 5 values)</p>
<p><strong class="title">Note:</strong> This success criteria does not apply to text entered as all caps. Content authors are encouraged to use styles instead of typing text as all caps.</p></td>
<td class="pri">AAA</td>
<td class="pri">Firefox, IE, Opera, Safari - user style sheet
<!-- MENU-LOCATION=NONE -->including capitalization, auto-hypenation, borders, word-spacing.</td>
<td class="pri">Firefox, IE, Opera, Safari - user style sheet
<!-- MENU-LOCATION=NONE -->
including capitalization, auto-hypenation, borders, word-spacing.</td>
</tr>
<tr class="h3">
<td class="line-number">50</td>
<td class"whole-line"><strong class="title"> 1.5.1 Global Volume:</strong> The user can adjust the volume of each audio tracks independently of other tracks, relative to the global volume level set through operating environment mechanisms. (Level A) </td>
<td class="pri">A</td>
<td class="pri">media players (youtube volume is different from global volume) lots of media players do this. what about video tag in html 5 - volume independent of global?</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">54</td>
<td class"whole-line"><strong class="title"> 1.6.1 Speech Rate, Volume, and Voice:</strong> If synthesized speech is produced, the user can specify the following: (Level A)<br/>
a. Speech rate<br/>
b. Speech volume (independently of other sources of audio)<br/>
c. Voice, when more than one voice is available</td>
<td class="pri">A</td>
<td class="pri">chrome vox - chromevox - rate, volume, voice</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">55</td>
<td class"whole-line"><p><strong class="title"> 1.6.2 Speech Pitch and Range:</strong> If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: (Level AA)<br/> * Pitch (average frequency of the speaking voice)<br/> * Pitch range (variation in average frequency)</p>
<p><strong class="title">Note:</strong> Because the technical implementations of text to speech engines vary (e.g. formant-based synthesis, concatenative synthesis), a specific engine may not support varying pitch or pitch range. A user agent should expose the availability of pitch and pitch range control if the currently selected or installed text to speech engine offers this capability.</p></td>
<td class="pri">AA</td>
<td class="pri">chromevox - pitch only. http://www.chromevox.com/keyboard_shortcuts.html</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">57</td>
<td class"whole-line"><strong class="title"> 1.6.3 Advanced Speech Characteristics:</strong> If synthesized speech is produced, the user can adjust all of the speech characteristics provided by the speech synthesizer. (Level AAA) </td>
<td class="pri">AAA</td>
<td class="pri">none known</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">58</td>
<td class"whole-line"><strong class="title">1.6.4 Synthesized Speech Features:</strong> If synthesized speech is produced, the following features are provided: (Level AA)<br/> * User-defined extensions to the synthesized speech dictionary.<br/> * "Spell-out": text is spelled one character at a time, or according to language-dependent pronunciation rules.<br/> * At least two ways of speaking numerals: spoken as individual digits and punctuation (e.g. "one two zero three point five" for 1203.5 or "one comma two zero three point five" for 1,203.5), and spoken as full numbers are spoken (e.g. "one thousand, two hundred and three point five" for 1203.5).<br/> * At least two ways of speaking punctuation: spoken literally, and with punctuation understood from speech characteristics like pauses.</td>
<td class="pri">AA</td>
<td class="pri">all - only for external screen readers.<br />chromevox - read character by character, punctuation - on/off, no exceptions, one way to read numbers,</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">59</td>
<td class"whole-line"><strong class="title">1.6.5 Synthesized Speech Language:</strong> If synthesized speech is produced and more than one language is available, the user can change the language. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri">chromevox - yes</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">62</td>
<td class"whole-line"><strong class="title"> 1.7.1 Support User Stylesheets:</strong> If the user agent supports a mechanism for author stylesheets, the user agent also provides a mechanism for user stylesheets. (Level A) </td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari - Authors can have multiple style sheet. Chrome, Firefox-Stylish extension https://chrome.google.com/webstore/detail/fjnbnpbmkenffdnngjfgmeleoegfcffe, https://addons.mozilla.org/en-US/firefox/addon/stylish/</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">63</td>
<td class"whole-line"><strong class="title">1.7.2 Apply User Stylesheets:</strong> If user stylesheets are supported, then the user can enable or disable user stylesheets for: (Level A)<br/>
a. All pages on specified websites, or<br/>
b. All pages</td>
<td class="pri">A</td>
<td class="pri"><p>a. Chrome, Firefox-Stylish extension https://chrome.google.com/webstore/detail/fjnbnpbmkenffdnngjfgmeleoegfcffe, https://addons.mozilla.org/en-US/firefox/addon/stylish/ for individual sites</p>
<p>b. Firefox, Chrome, IE, Opera, Safari can do all pages, </p></td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">64</td>
<td class"whole-line"><strong class="title">1.7.3 Disable Author Stylesheets:</strong> If the user agent supports a mechanism for author stylesheets, the user can disable the use of author stylesheets on the current page. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari can do all pages, there are also many extensions the can turn off styles. <br>
Current page may be an issue</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">65</td>
<td class"whole-line"><strong class="title">1.7.4 Save Copies of Stylesheets:</strong> The user can save copies of the stylesheets referenced by the current page. This allows the user to edit and load the copies as user stylesheets. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">68</td>
<td class"whole-line"><strong class="title"> 1.8.1 Highlight Viewport:</strong> The user can have the viewport with the input focus be highlighted. (Level A) </td>
<td class="pri">A</td>
<td class="pri">IE provides a focus for frames and other viewports, don't know if you can style the highlight.</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">69</td>
<td class"whole-line"><strong class="title">1.8.2 Move Viewport to Selection and Focus:</strong> When a viewport's selection or input focus changes, the viewport's content moves as necessary to ensure that the new selection or input focus location is at least partially in the visible portion of the viewport. (Level A) </td>
<td class="pri">A</td>
<td class="pri"><p>O. this is widely supported through scroll bars on desktop browsers, need to check mobile devices. <br>
F does this, doesn't it, despite bug when you change font size or viewport width? </p>
<p>Safari on IOS has scroll bars</p></td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">70</td>
<td class"whole-line"><strong class="title">1.8.3 Provide Viewport Scrollbars:</strong> When the rendered content extends beyond the viewport dimensions, users can have graphical viewports include scrollbars, overriding any values specified by the author. (Level A) </td>
<td class="pri">A</td>
<td class="pri">although overriding author is not widely implemented, there is usually a way to get around it. </td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">71</td>
<td class"whole-line"><strong class="title">1.8.4 Indicate Viewport Position:</strong> The user can determine the viewport's position relative to the full extent of the rendered content. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">72</td>
<td class"whole-line"><strong class="title">1.8.5 Allow Zoom:</strong> The user can rescale content within top-level graphical viewports as follows: (Level A)<br/> * Zoom in: to 500% or more of the default size<br/> * Zoom out: to 10% or less of the default size, so the content fits within the height or width of the viewport</td>
<td class="pri">A</td>
<td class="pri">All zoom, but the user must use Stylish to constrain horizontal scrolling</td>
<td class="pri">All zoom, but the user must use Stylish to constrain horizontal scrolling</td>
</tr>
<tr class="h3">
<td class="line-number">73</td>
<td class"whole-line"><p><strong class="title">1.8.6 Maintain Point of Regard:</strong> The point of regard remains visible within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed. (Level A) </p>
<p><strong class="title">Note:</strong> When the point of regard is larger than the viewport, the user agent keeps visible the beginning of the point of regard according to the current language's reading order (e.g. top-left in English)</p></td>
<td class="pri">A</td>
<td class="pri">Chrome</td>
<td class="pri">Internet Explorer, Safari</td>
</tr>
<tr class="h3">
<td class="line-number">75</td>
<td class"whole-line"><strong class="title"> 1.8.7 Customize Viewport Highlighting:</strong> When highlighting viewports as specified by 1.8.1 Highlight Viewport, the user can customize attributes of the viewport highlighting mechanism (e.g. color and width of borders). (Level AA)</td>
<td class="pri">AA</td>
<td class="pri">@@ Firefox highlights frames, no one else. No customizations. FF puts dotted line around viewports.Can use F6 to move between viewports in all major browsers</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">76</td>
<td class"whole-line"><strong class="title">1.8.8 Allow Viewport Resize:</strong> The user can resize viewports within restrictions imposed by the platform, overriding any values specified by the author. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri"><p>youtube player allow resizing per video, as do most other players. Chrome supports this for edit fields, but F does not. New HTML5 form attrib (resize) in Chome, Safari, and Firefox allows changing size of edit field, but no user override. </p>
<p>No keyboard access to the resize handle is implemented. No resize available for single line edit box.I wonder who supports it for browser generated dialog boxes (need to find these) letting user override any author settings fixing the window size. </p>
<p>1.8.8 is doable for textarea, video players, frames, and iframes with the mouse. May need the addition of Stylish to add resizability in FF, Safari, Chrome. none have functionality from the keyboard. IE8 does not resize textarea.</p></td>
<td class="pri">youtube player allow resizing per video, as do most other players. May need the addition of Stylish to add resizability in FF, Safari, Chrome. </td>
</tr>
<tr class="h3">
<td class="line-number">77</td>
<td class"whole-line"><p><strong class="title">1.8.9 Provide Viewport History:</strong> For user agents that implement a history mechanism for top-level viewports (e.g. "back" button), the user can return to any state in the viewport history that is allowed by the content, including: (Level AA)<br/> (a) restored point of regard<br/> (b) input focus, and<br/> (c) user's form field entries</p>
<p><strong class="title">Note:</strong> It is recommended that selection also be restored.</p></td>
<td class="pri">AA</td>
<td class="pri"><p>IE maintains point of regard and form content and input focus</p>
<p>chrome maintains point of regard and form content but not input focus</p>
<p>change - safari maintains point of regard and form content and input focus</p>
<p>all tested on <a href="https://www.cs.tut.fi/%7Ejkorpela/www/testel.html">https://www.cs.tut.fi/~jkorpela/www/testel.html</a> (plain and simple html)</p>
<p> </p></td>
<td class="pri"><p>FF maintains point of regard and form content and input focus</p>
<p>ff is the only browser to maintain selection highlighting</p></td>
</tr>
<tr class="h3">
<td class="line-number">79</td>
<td class"whole-line"><strong class="title">1.8.10 Allow Top-Level Viewport Open on Request:</strong> The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). (Level AA)</td>
<td class="pri">AA</td>
<td class="pri">FCIOS</td>
<td class="pri">all desktop browsers have a configuration setting for blocking popup window</td>
</tr>
<tr class="h3">
<td class="line-number">80</td>
<td class"whole-line"><strong class="title">1.8.11 Allow Top-Level Viewport Focus Control:</strong> If new top-level viewports (e.g. windows or tabs) are configured to open without explicit user request, the user can specify whether or not top-level viewports take the active keyboard focus when they open. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri"><p>ff Open new windows in a new tab instead and When a link is opened in a new tab, switch to it immediately</p>
<p>safari, IE, chrome, no focus control.</p>
<p>Note: test pages to popup a window.</p>
<p><a href="http://rip747.github.io/popupwindow/">http://rip747.github.io/popupwindow/</a></p>
<p><a href="http://www.textfixer.com/html/javascript-pop-up-window.php">http://www.textfixer.com/html/javascript-pop-up-window.php</a></p></td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">81</td>
<td class"whole-line"><strong class="title">1.8.12 Allow Same User Interface:</strong> The user can specify that all top-level viewports (e.g. windows or tabs) follow the defined user interface configuration. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri"><p>Opening applications in a new tab (FCIOS)</p>
<p>Especially important for web applications where you log in a separate window, then a new window pops up with no browser user interface, so there are no controls or extensions for accessibility. </p></td>
<td class="pri">Opening applications in a new tab (FCIOS)</td>
</tr>
<tr class="h3">
<td class="line-number">82</td>
<td class"whole-line"><p><strong class="title">1.8.13 Multi-Column Text Reflow:</strong> The user can specify that recognized multi-column text blocks each be reflowed into a single column. (Level AA) </p>
<p><strong class="title">Note:</strong> Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off.</p></td>
<td class="pri">AA</td>
<td class="pri">Stylish addon for Firefox, Chrome and Safari</td>
<td class="pri">Stylish addon for Firefox, Chrome and Safari</td>
</tr>
<tr class="h3">
<td class="line-number">84</td>
<td class"whole-line"><strong class="title">1.8.14 Ignore Fixed Unit Dimensions:</strong> The user can have the user agent override author-specified unit dimensions. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri">Stylish addon for Firefox, Chrome and Safari</td>
<td class="pri">Stylish addon for Firefox, Chrome and Safari</td>
</tr>
<tr class="h3">
<td class="line-number">85</td>
<td class"whole-line"><p><strong class="title">1.8.15 Linearize Content:</strong> The user can have recognized content rendered as a single column, overriding author-specified formatting of columns, tables, and positioning. (Level AA) </p>
<p><strong class="title">Note:</strong> Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off.</p></td>
<td class="pri">AA</td>
<td class="pri"><p>Turn off stylesheets FCIOS</p>
webdeveloper - firefox - (MIscellaneous menu -> Linearize page)</td>
<td class="pri"><p>Opera - http://help.opera.com/Windows/12.10/en/stylemodes.html</p>
<p>Web Developer Toolbar for Chrome: <a href="https://chrome.google.com/webstore/detail/yourhere/fkandkgadbpobooanbmiiinlelnhbabm">https://chrome.google.com/webstore/detail/yourhere/fkandkgadbpobooanbmiiinlelnhbabm</a></p></td>
</tr>
<tr class="h3">
<td class="line-number">87</td>
<td class"whole-line"><strong class="title"> 1.8.16 Provide Web Page Bookmarks:</strong> The user can mark items in a web page, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. (Level AAA) </td>
<td class="pri">AAA</td>
<td class="pri"><p>Chrome - scroll marker - chrome - <a href="https://chrome.google.com/webstore/detail/scroll-marker/jdoinodpdahlmpgmpmhonheidpjhhnid?hl=en">https://chrome.google.com/webstore/detail/scroll-marker/jdoinodpdahlmpgmpmhonheidpjhhnid?hl=en</a> </p>
<p>Chrome -yourhere placemarker - chrome - <a href="https://chrome.google.com/webstore/detail/yourhere/fkandkgadbpobooanbmiiinlelnhbabm">https://chrome.google.com/webstore/detail/yourhere/fkandkgadbpobooanbmiiinlelnhbabm</a> </p></td>
<td class="pri">Safari - canisbos Placemarker - safari <a href="http://canisbos.com/placemarker">http://canisbos.com/placemarker</a> </td>
</tr>
<tr class="h3">
<td class="line-number">90</td>
<td class"whole-line"><p><strong class="title">1.9.1 Outline View:</strong> Users can view a navigable outline of the headings in rendered content that allows focus to be moved to the corresponding element in the main viewport. (Level AA) </p>
<p><strong class="title">Note:</strong> Note: An outline view might also include other named elements such as document landmarks.</p></td>
<td class="pri">AA</td>
<td class="pri"><p>https://addons.mozilla.org/es/firefox/addon/headingsmap/</p>
<p>http://fae20.cita.illinois.edu/</p></td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">92</td>
<td class"whole-line"><strong class="title">1.9.2 Source View:</strong> The user can view all source text that is available to the user agent. (Level AAA) </td>
<td class="pri">AAA</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">95</td>
<td class"whole-line"><strong class="title">1.10.1 Show Related Elements:</strong> The user can access the information from explicitly-defined relationships in the content, including at least the following: (Level AA)<br/> (a) calculated accessible name for images<br/> (b) calculated accessible name for controls (e.g. form fields, buttons)<br/> (c) caption for a table<br/> (d) row and column labels for a table cell</td>
<td class="pri">AA</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">96</td>
<td class"whole-line"><strong class="title">1.10.2 Show Element Hierarchy:</strong> The user can determine the path of element nodes going from the root element of the element hierarchy to the currently focused or selected element. (Level AAA)</td>
<td class="pri">AAA</td>
<td class="pri">web inspector - chrome https://chrome.google.com/webstore/detail/web-inspector/enibedkmbpadhfofcgjcphipflcbpelf?hl=en</td>
<td class="pri">webdeveloper for chrome and opera also</td>
</tr>
<tr class="h3">
<td class="line-number">101</td>
<td class"whole-line"><strong class="title">2.1.1 Provide Full Keyboard Functionality:</strong> All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing other input methods in addition to keyboard operation including mouse, touch, gesture and speech. (Level A) </td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari - except tooltips for title element, scrolling in overflow (css) elements.</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">102</td>
<td class"whole-line"><strong class="title">2.1.2 Has Keyboard Focus:</strong> Every viewport has an active or inactive keyboard focus at all times. (Level A) </td>
<td class="pri">A</td>
<td class="pri"><p>Firefox, Chrome, IE, Opera, Safari</p>
<p>Everyone except some mobile browsers (e.g. Safari for iOS).<br>
Many browsers have some lapses, such as keyboard access to hover text.<br>
F fails with plug-ins (e.g. Flash).</p></td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">103</td>
<td class"whole-line"><strong class="title">2.1.3 Avoid Keyboard Traps:</strong> If keyboard focus can be moved to a component using a keyboard interface (including nested user agents), then focus can be moved away from that component using only a keyboard interface. If this requires more than unmodified arrow or Tab keys (or standard exit methods like Escape), users are advised of the method for moving focus away. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari - need more checking</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">104</td>
<td class"whole-line"><strong class="title">2.1.4 Separate Selection from Activation:</strong> The user can specify that focus and selection can be moved without causing further changes in focus, selection, or the state of controls, by either the user agent or author-supplied content. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Everyone does it except the radio button. Does it behave this way because it is specified in HTML5? 2007 wiki page with instructions for that behavior: http://www.w3.org/wiki/RadioButton - should be an example for Meets WCAG by default</td>
<td class="pri">Everyone does this for everything except the radio button. </td>
</tr>
<tr class="h3">
<td class="line-number">105</td>
<td class"whole-line"><strong class="title">2.1.5 Follow Text Keyboard Conventions:</strong> The user agent follows keyboard conventions for the operating environment. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">106</td>
<td class"whole-line"><strong class="title">2.1.6 Make Keyboard Access Efficient:</strong> The user agent user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari, IOS(mac) browsers have no keyboard</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">109</td>
<td class"whole-line"><strong class="title">2.2.1 Sequential Navigation Between Elements:</strong> The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the rendered content of the current top-level viewports. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari - generally using F6 key</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">110</td>
<td class"whole-line"><p><strong class="title">2.2.2 Sequential Navigation Between Landmarks:</strong> The user can move the keyboard focus backwards and forwards between regions identified by document landmarks. Note: The user agent might also include other regions, such as viewports, in the sequential navigation.</p></td>
<td class="pri">A</td>
<td class="pri"><p>Firefox - https://github.com/matatk/landmarks</p>
<p> </p></td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">112</td>
<td class"whole-line"><strong class="title">2.2.3 Default Navigation Order:</strong> If the author has not specified a navigation order, the user can have the default sequential navigation order be the source order. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">113</td>
<td class"whole-line"><strong class="title">2.2.4 Options for Wrapping in Navigation:</strong> The user can request notification when sequential navigation wraps at the beginning or end of a document, and can prevent such wrapping. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri">We know of no examples.<br>
It could be implemented using an add-on.</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">116</td>
<td class"whole-line"><strong class="title">2.3.1 Allow Direct Navigation to Enabled Elements:</strong> The user can move keyboard focus directly to any enabled element in the rendered content. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri">Firefox - mouseless browsing</td>
<td class="pri">IE - Accessibility toolbar</td>
</tr>
<tr class="h3">
<td class="line-number">117</td>
<td class"whole-line"><strong class="title">2.3.2 Allow Direct Activation of Enabled Elements:</strong> The user can, in a single action, move keyboard focus directly to any enabled element in the rendered content and perform an activation action on that element. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri">Firefox - mouseless browsing</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">118</td>
<td class"whole-line"><strong class="title">2.3.3 Present Direct Commands from Rendered Content:</strong> The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements (e.g. Alt+R to reply to a web email). (Level AA) </td>
<td class="pri">AA</td>
<td class="pri">landmarks - <a rel="nofollow" href="https://github.com/davidtodd/landmarks">https://github.com/davidtodd/landmarks</a></td>
<td class="pri">accesskey - https://chrome.google.com/webstore/detail/xkey-discover-website-key/hhkgjbankdehdhlgpnbhnbeodknolokk</td>
</tr>
<tr class="h3">
<td class="line-number">119</td>
<td class"whole-line"><strong class="title">2.3.4 Present Direct Commands in User Interface:</strong> The user can have any direct commands in the UA user interface (e.g. keyboard shortcuts) be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). (Level AA)</td>
<td class="pri">AA</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari majority of menu options are assigned keyboard shortcuts</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">120</td>
<td class"whole-line"><strong class="title">2.3.5 Allow Customized Keyboard Commands:</strong> The user can remap any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and UA user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). (Level AA) </td>
<td class="pri">AA</td>
<td class="pri"><p>F add-ons KeyConfig and GreaseMonkey; </p>
<p>Opera addons;</p></td>
<td class="pri">Office allows changing UI keystrokes.</td>
</tr>
<tr class="h3">
<td class="line-number">123</td>
<td class"whole-line"><strong class="title">2.4.1 Text Search:</strong> The user can perform a search within rendered content, including rendered text alternatives and rendered generated content, for any sequence of printing characters from the document character set. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">124</td>
<td class"whole-line"><strong class="title">2.4.2 Search Direction:</strong> The user can search forward or backward in rendered content. (Level A) </td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">125</td>
<td class"whole-line"><strong class="title">2.4.3 Match Found:</strong> When a search operation produces a match, the matched content is highlighted, the viewport is scrolled if necessary so that the matched content is within its visible area, and the user can search from the location of the match. (Level A) </td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">126</td>
<td class"whole-line"><strong class="title">2.4.4 Alert on Wrap or No Match:</strong> The user can choose to receive notification when there is no match to a search operation. The user can choose to receive notification when the search continues from the beginning or end of content. (Level A) </td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">127</td>
<td class"whole-line"><strong class="title">2.4.5 Alternative Content Search:</strong> The user can perform text searches within alternative content that is text (e.g. text alternatives for non-text content, captions) even when the alternative content is not rendered onscreen. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri"><p>for alt text - webdeveloper - firefox - https://chrome.google.com/webstore/detail/yourhere/fkandkgadbpobooanbmiiinlelnhbabm reveal alt then you can search</p>
<p>The extension reveals it and then it is searchable. The extension doesn't make it searchable. <br />
<br />
chrome bug https://code.google.com/p/chromium/issues/detail?id=496232<br />
ff bug https://bugzilla.mozilla.org/show_bug.cgi?id=158757</p></td>
<td class="pri">webdeveloper - chrome https://chrome.google.com/webstore/detail/web-developer/bfbameneiokkgbdmiekhjnmfkcnldhhm?hl=en reveal alt then search</td>
</tr>
<tr class="h3">
<td class="line-number">131</td>
<td class"whole-line"><strong class="title">2.5.1 Provide Structural Navigation by Heading and within Tables:</strong> The user agent provides at least the following types of structural navigation, where the structure types are recognized: (Level AA)<br/> * By heading<br/> * By content sections<br/> * Within tables</td>
<td class="pri">AA</td>
<td class="pri"><p>headingsMap - Firefox https://addons.mozilla.org/en-us/firefox/addon/headingsmap/</p>
<p>landmark nav - Firefox - https://github.com/matatk/landmarks </p>
<p>Chrome with ChromeVox add-on provides next/previous navigation through elements of various types.</p></td>
<td class="pri">scrollbar of content - chrome https://chrome.google.com/webstore/detail/scrollbar-of-contents/cfmkncejaemmcobmaabfigljmnkeecdm</td>
</tr>
<tr class="h3">
<td class="line-number">138</td>
<td class"whole-line"><p><strong class="title">2.6.1 Allow Persistent Accessibility Settings:</strong> User agent accessibility preference settings persist between sessions. (Level A) </p>
<p><strong class="title">Note:</strong> User agents may have a public access setting that turns this off. </p></td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">140</td>
<td class"whole-line"><strong class="title">2.6.2 Allow Restore All to Default:</strong> The user can restore all preference settings to default values. (Level A) </td>
<td class="pri">A</td>
<td class="pri"><p>Chrome "reset browser", Google Chrome has an option that will reset itself to its default settings. To find this option, open Chrome's menu and select Settings. Perform a search for “reset browser” and you'll see the Reset browser settings button.</p>
<p>IE has a button in Settings</p></td>
<td class="pri"> <p>Refresh Firefox - reset add-ons and settings | Firefox Help https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings<br />
"The refresh feature works by creating a new profile folder for you while saving your important data.<br />
Add-ons which are normally stored inside the Firefox profile folder, such as extensions and themes, will be removed. Add-ons stored in other locations, such as plugins, will not be removed but any modified preferences (such as plugins you have disabled) will be reset."</p>
ff has extension for retore to default without removing addons http://chrispederick.com/</td>
</tr>
<tr class="h3">
<td class="line-number">141</td>
<td class"whole-line"><strong class="title">2.6.3 Allow Multiple Sets of Preference Settings:</strong> The user can save and retrieve multiple sets of user agent preference settings. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri">Firefox can do Profiles https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles</td>
<td class="pri"><p>Chrome - Browser User Profile (can it be used across one Google ID?) http://www.pcworld.com/article/2089364/how-to-create-and-manage-multiple-user-profiles-in-chrome.html</p></td>
</tr>
<tr class="h3">
<td class="line-number">142</td>
<td class"whole-line"><strong class="title">2.6.4 Allow Preference Changes from outside the User Interface:</strong> The user can adjust any preference settings required to meet the User Agent Accessibility Guidelines (UAAG) 2.0 from outside the UA user interface. (Level AAA)</td>
<td class="pri">AAA</td>
<td class="pri"><p>All Desktop browsers used to have .ini files in WIndows. Firefox profile files can be changed by expert users. On Mac, Profiles folder under User -> Libraries -> Application Support -> Firefox. There is access from Inside FF Help menu. </p>
<p>Stupid Geek Tricks: Hacking the Firefox Profile Data Storage<br />
http://www.howtogeek.com/69051/stupid-geek-tricks-hacking-the-firefox-profile-data-storage/<br /> "Using an open source program, SQLite Database Browser, you can not only see the structure of the individual databases but browse and, if you are so inclined, manipulate all the data in each of the tables."</p></td>
<td class="pri">Chrome Windows - %LOCALAPPDATA%\Google\Chrome\User Data\ huge folder - not user friendly , but it is possible to edit</td>
</tr>
<tr class="h3">
<td class="line-number">143</td>
<td class"whole-line"><strong class="title">2.6.5 Make Preference Settings Transferable:</strong> The user can transfer all compatible user agent preference settings between devices. (Level AAA) </td>
<td class="pri">AAA</td>
<td class="pri">Transfer the Profile to Another Computer. Close Mozilla Firefox, press "Windows-X" to open the Windows Power User menu and then click "Run" to open the Run utility. Type "%APPDATA%\Mozilla\Firefox\Profiles\" (without the quotation marks) and press "Enter" to open Firefox's Profiles folder. <a href="http://smallbusiness.chron.com/transfer-firefox-profile-new-computer-78755.html"> http://smallbusiness.chron.com/transfer-firefox-profile-new-computer-78755.html</a></td>
<td class="pri">chrome - windows - %LOCALAPPDATA%\Google\Chrome\User Data\ huge folder - just transfer the "default" folder</td>
</tr>
<tr class="h3">
<td class="line-number">146</td>
<td class"whole-line"><strong class="title">2.7.1 Customize Display of Controls for User Interface Commands, Functions, and Extensions:</strong> The user can customize which user agent commands, functions, and extensions are displayed within the user agent user interface as follows: (Level AA)<br/> * Show: The user can choose to display any controls available within the user agent user interface, including user-installed extensions. It is acceptable to limit the total number of controls that are displayed onscreen.<br/> * Simplify: The user can simplify the default user interface by choosing to display only commands essential for basic operation (e.g. by hiding some controls).<br/> * Reposition: The user can choose to reposition individual controls within containers (e.g. toolbars or tool palettes), as well as reposition the containers themselves to facilitate physical access (e.g. to minimize hand travel on touch screens, or to facilitate preferred hand access on handheld mobile devices).<br/> * Assign Activation Keystrokes or Gestures: The user can choose to view, assign or change default keystrokes or gestures used to activate controls.<br/> * Reset: The user has the option to reset the containers and controls to their default configuration. </td>
<td class="pri">AA</td>
<td class="pri"><p>a) SHOW: Firefox and IE allow hiding and revealing toolbars and putting them in different orders.</p>
<p>b) SIMPLIFY: Firefox allows show and hide, and hide = Simplify. S3 & Menu Wizard extensions</p>
<p>c) REPOSITION: FIrefox has reposition in Menu Wizard at the item level https://addons.mozilla.org/en-us/firefox/addon/s3menu-wizard/</p>
<p>d) GESTURES: FIrefox can assign keystrokes with an extension: Customizable Shortcuts https://addons.mozilla.org/en-US/firefox/addon/customizable-shortcuts/</p>
<p>e) RESET: IE and Firefox have a "restore to default" </p>
<p>Firefox: "The menu button new fx menu gives you convenient access to your favorite Firefox features. Don't like the default arrangement? It's easy to customize." <br />Customize Firefox controls, buttons and toolbars | Firefox Help<br />
https://support.mozilla.org/en-US/kb/customize-firefox-controls-buttons-and-toolbars</p>
<p>Customize Your Menus in Firefox http://www.howtogeek.com/howto/6985/customize-your-menus-in-firefox/ "Would you like a way to edit menus and remove the extra entries that you do not use or need? Now you can with the Menu Editor extension for Firefox."</p>
<p>Chrome Customize Toolbar: https://support.google.com/toolbar/answer/2392132?hl=en </p>
<p>Mercury browser can turn controls on/off but won't allow positioning. </p>
<p> </p></td>
<td class="pri"><p>a) SHOW: Firefox and IE allow hiding and revealing toolbars and putting them in different orders. Chrome - Proper Menubar - https://chrome.google.com/webstore/detail/proper-menubar/egclcjdpndeoioimlbbbmdhcaopnedkp?hl=en</p>
<p>b) SIMPLIFY:IE allows hiding toolbars</p>
<p>c) REPOSITION: IE has reposition of toolbars</p>
<p>d) GESTURES: Opera keyboard control mapper. Apple has Gesture Wizard on iOS. Safari: Swipe Safari Adds Configurable Gestures to Safari on iPhone http://lifehacker.com/5911935/swipe-safari-adds-tons-of-configurable-gestures-to-safari-on-iphone</p>
<p>e) RESET: IE has a "restore to default" </p>
<p> </p></td>
</tr>
<tr class="h3">
<td class="line-number">149</td>
<td class"whole-line"><strong class="title">2.8.1 Adjustable Time Limits:</strong> The UA user interface does not include time limits or at least one of the following is true: (Level A)<br/> (a) Turn Off: Users are allowed to turn off the time limit before encountering it; or<br/> (b) Adjust: Users are allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or<br/> (c) Extend: Users are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g. "press the space bar"), and users are allowed to extend the time limit at least ten times; or<br/> (d) Real-time Exception: The time limit is a required part of a real-time event and no alternative to the time limit is possible; or<br/> (e) Essential Exception: The time limit is essential and extending it would invalidate the activity; or<br/> (f) 20 Hour Exception: The time limit is longer than 20 hours. </td>
<td class="pri">A</td>
<td class="pri"><p>For the brower UI, not content UI. Hard to find examples of UI events that time out. Suggest Time Out on Hover on links. Firefox and Chrome don't have timeouts. IE times out in 5 seconds on hover on link (failure). </p>
<p>FIrefox has no timeouts</p>
<p>No examples of customized timeouts, but 2 examples with no timeouts is sufficient for implementations. </p></td>
<td class="pri">Chrome has no timeouts</td>
</tr>
<tr class="h3">
<td class="line-number">152</td>
<td class"whole-line"><strong class="title">2.9.1 Three Flashes or Below Threshold:</strong> In its default configuration, the user agent does not display any UA user interface components that flashes more than three times in any one-second period, unless the flash is below general flash and red flash thresholds. (Level A) </td>
<td class="pri">A</td>
<td class="pri">All browsers pass. No examples of flashing UI. </td>
<td class="pri">All browsers pass. No examples of flashing UI. </td>
</tr>
<tr class="h3">
<td class="line-number">153</td>
<td class"whole-line"><strong class="title">2.9.2 Three Flashes:</strong> In its default configuration, the user agent does not display any UA user interface components that flashes more than three times in any one-second period (regardless of whether not the flash is below the general flash and red flash thresholds). (Level AAA) </td>
<td class="pri">AAA</td>
<td class="pri">All browsers pass. No examples of flashing UI. </td>
<td class="pri">All browsers pass. No examples of flashing UI. </td>
</tr>
<tr class="h3">
<td class="line-number">156</td>
<td class"whole-line"><strong class="title">2.10.1 Time-Based Media Load-Only:</strong> The user can override the play on load of recognized time-based media content such that the content is not played until explicit user request. (Level A)</td>
<td class="pri">A</td>
<td class="pri"><p>Chrome: native Open Plug-in On Request</p></td>
<td class="pri"><p>Safari </p>
<p>Firefox Options -> Applications allows option of Always Ask. </p>
<p> </p></td>
</tr>
<tr class="h3">
<td class="line-number">157</td>
<td class"whole-line"><strong class="title">2.10.2 Execution Placeholder:</strong> The user can request a placeholder instead of executable content that would normally be contained within an on-screen area (e.g. Applet, Flash), until explicit user request to execute. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Firefox shows placeholder when "Always Ask" is selected</td>
<td class="pri">Also Chrome and Safari automatically show placeholder. </td>
</tr>
<tr class="h3">
<td class="line-number">158</td>
<td class"whole-line"><strong class="title">2.10.3 Execution Toggle:</strong> The user can turn on/off the execution of dynamic or executable content (e.g. Javascript, canvas, media). (Level A) </td>
<td class="pri">A</td>
<td class="pri">Firefox extension: NoScript</td>
<td class="pri">Safari (native): execution toggle by site</td>
</tr>
<tr class="h3">
<td class="line-number">159</td>
<td class"whole-line"><strong class="title">2.10.4 Adjustable Playback Rate for Prerecorded Content:</strong> The user can adjust the playback rate of prerecorded time-based media content, such that all of the following are true: (Level AA)<br/> * Playback Rate: The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time.<br/> * Pitch: Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality.<br/> * Synchronization: Audio and video tracks remain synchronized across this required range of playback rates.<br/> * Reset: The user agent provides a function that resets the playback rate to normal (100%).</td>
<td class="pri">AA</td>
<td class="pri"><p>Accessible media players: BBC Player, JW Player, VLC, OzPlayer</p>
<p>Adjustable playback rate is built into HTML5. How to enable in YouTube: http://lifehacker.com/5491852/enable-variable-speed-playback-in-youtube</p>
<p>BBC Player: BBC player<br />
http://support.panopto.com/documentation/viewing/variable-speed-playback-vsp</p>
<p> Html5 Youtube Video Speed Controller :: Add-ons for Firefox https://addons.mozilla.org/en-uS/firefox/addon/youtubevideospeedcontroller/ "Html5 Youtube Video Speed Controller helps to change the playback speed of html5 video on youtube." </p>
<p>Enounce MySpeed Player https://www.raymond.cc/blog/download/did/2987/</p></td>
<td class="pri"><p>Chrome: https://chrome.google.com/webstore/detail/video-speed-controller/nffaoalbilbmmfgbnbgppjihopabppdk?hl=en</p>
<p>Learning API http://www.learningapi.com/2012/04/variable-speed-playback-html5-video-feature/</p>
<p> </p></td>
</tr>
<tr class="h3">
<td class="line-number">160</td>
<td class"whole-line"><strong class="title">2.10.5 Stop/Pause/Resume Time-Based Media:</strong> The user can stop, pause, and resume rendered audio and animation content (e.g video, animation, changing text) that lasts three or more seconds at the default playback rate. (Level A) </td>
<td class="pri">A</td>
<td class="pri">IE supports this by hitting Escape to stop recognized animation. </td>
<td class="pri"><p>Toggle animated GIFs :: Add-ons for Firefox https://addons.mozilla.org/en-us/firefox/addon/toggle-animated-gifs/</p>
<p>Firefox intentionally disabled the ability to stop animated gifs in 2012. 825486 – Escape no longer stops animated GIFs https://bugzilla.mozilla.org/show_bug.cgi?id=825486. [Insert insulting term here.]</p></td>
</tr>
<tr class="h3">
<td class="line-number">161</td>
<td class"whole-line"><strong class="title">2.10.6 Navigation of Time-Based Media by Time:</strong> If time-based media lasts three or more seconds at the default playback rate, the user can navigate it using a continuous scale and by relative time units. (Level A)</td>
<td class="pri">A</td>
<td class="pri">All major players do this: Quicktime, Real and Windows Media player, JWPlayer, YouTube, Oz Player, and Paypal player. All of these allow relative units (5, 10, 15, 20, 30 seconds).</td>
<td class="pri">All major players do this: Quicktime, Real and Windows Media player,JWPlayer, YouTube</td>
</tr>
<tr class="h3">
<td class="line-number">162</td>
<td class"whole-line"><strong class="title">2.10.7 Navigation of Time-Based Media by Semantics:</strong> The user can navigate by semantic structure within the time-based media, such as by chapters or scenes present in the media. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri">Quicktime, JWplayer</td>
<td class="pri">Youtube allows nav by chapter (section) they are highlighted in the timeline(sample https://www.youtube.com/watch?v=O8Ja4u8_RGQ)</td>
</tr>
<tr class="h3">
<td class="line-number">163</td>
<td class"whole-line"><strong class="title">2.10.8 Video Contrast and Brightness:</strong> Users can adjust the contrast and brightness of visual time-based media. (Level AAA)</td>
<td class="pri">AAA</td>
<td class="pri">Quicktime, REAL, VLC and WMP stand alone players (VLC -> http://www.addictivetips.com/windows-tips/15-features-of-vlc-player-that-you-probably-dont-know-about/)</td>
<td class="pri">Quicktime, REAL, VLC and WMP stand alone players</td>
</tr>
<tr class="h3">
<td class="line-number">166</td>
<td class"whole-line"><strong class="title">2.11.1 Platform Text Input Devices:</strong> <span class="sc-text">If an input device is supported by the <a class="dfn-instance"
href="#def-platform" rel="glossary" title="definition: platform">platform</a>, all user agent functionality including text input can be operated using that device. </span> (Level AA) </td>
<td class="pri">A</td>
<td class="pri">Braille keyboard, onscreen keyboards, onscreen keyboards all work on all major browsers. On mobile iOS see: https://support.apple.com/kb/PH13833?locale=en_US</td>
<td class="pri">All major desktop browsers.</td>
</tr>
<tr class="h3">
<td class="line-number">172</td>
<td class"whole-line"><p><strong class="title">3.1.1 Text Entry Undo:</strong> The user can reverse recognized text entry actions prior to submission. (Level A) </p>
<p><strong class="title">Note:</strong> Submission can be triggered in many different ways, such as clicking a submit button, typing a key in a control with an onkeypress event, or by a script responding to a timer. </p></td>
<td class="pri">A</td>
<td class="pri">All desktop browsers support (Chrome, IE, Firefox, Safari). Not on mobile at this time. </td>
<td class="pri">Chrome, IE, Firefox, Safari</td>
</tr>
<tr class="h3">
<td class="line-number">174</td>
<td class"whole-line"><strong class="title">3.1.2 Settings Changes can be Reversed or Confirmed:</strong> If the user agent provides mechanisms for changing its user interface settings, it either allows the user to reverse the setting changes, or the user agent can require user confirmation to proceed. (Level A)</td>
<td class="pri">A</td>
<td class="pri">IE has reset, FIrefox has refresh which removes all extenstions sets browser to default settings</td>
<td class="pri">Chrome has reset. </td>
</tr>
<tr class="h3">
<td class="line-number">175</td>
<td class"whole-line"><strong class="title">3.1.3 Retrieval Progress:</strong> By default, the user agent shows the state of content retrieval activity. (Level A)</td>
<td class="pri">A</td>
<td class="pri">Firefox, Chrome, IE, Opera, Safari</td>
<td class="pri">Chrome</td>
</tr>
<tr class="h3">
<td class="line-number">176</td>
<td class"whole-line"><strong class="title">3.1.4 Spell Check:</strong> The user can have spelling assistance for editable text in rendered content. (Level AA)</td>
<td class="pri">AA</td>
<td class="pri"> FF checks spelling in 'area' but not in type="text"</td>
<td class="pri">Safari on OS X has both spell-checking and auto-correct, in both multi-line and single-line input fields.</td>
</tr>
<tr class="h3">
<td class="line-number">177</td>
<td class"whole-line"><strong class="title">3.1.5 Back Button:</strong> The user can reverse recognized navigation between web addresses (e.g. standard "back button" functionality). (Level AA) </td>
<td class="pri">AA</td>
<td class="pri">All Browsers</td>
<td class="pri">All Browsers</td>
</tr>
<tr class="h3">
<td class="line-number">178</td>
<td class"whole-line"><strong class="title">3.1.6 Form Submission Confirm:</strong> The user can specify whether or not recognized form submissions must be confirmed. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri">None Known</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">179</td>
<td class"whole-line"><strong class="title">3.1.7 Form Auto-Fill:</strong> The user can have the following information stored and used to auto-fill form fields by request: (Level AA)<br/> (a) user's name<br/> (b) user's email address<br/> (c) user's phone number</td>
<td class="pri">AA</td>
<td class="pri"><a href="https://support.mozilla.org/en-US/kb/control-whether-firefox-automatically-fills-forms">Firefox</a></td>
<td class="pri"><a href="https://support.google.com/chrome/answer/142893?hl=en">Chrome</a></td>
</tr>
<tr class="h3">
<td class="line-number">180</td>
<td class"whole-line"><strong class="title">3.1.8 Save Form Entries:</strong> If the user agent provides a feature to save local versions of web content, then any form fields the user has filled retain any entries in the saved version. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri"><a href="https://addons.mozilla.org/en-US/firefox/addon/form-history-control/">Firefox - Form History Control</a> </td>
<td class="pri"><a hre="https://chrome.google.com/webstore/detail/lazarus-form-recovery/loljledaigphbcpfhfmgopdkppkifgno?hl=en">Chrome - Lazarus From Recovery</a></td>
</tr>
<tr class="h3">
<td class="line-number">183</td>
<td class"whole-line"><strong class="title">3.2.1 Accessible Documentation:</strong> Product documentation is available in a format that meets success criteria of WCAG 2.0 level "A" or greater. (Level A) </td>
<td class="pri">A</td>
<td class="pri">All browsers</td>
<td class="pri">Puffin (mobile)</td>
</tr>
<tr class="h3">
<td class="line-number">184</td>
<td class"whole-line"><strong class="title">3.2.2 Describe Accessibility Features:</strong> For each user agent feature that is used to meet UAAG 2.0, at least one of the following is true: (Level A)<br/> (a) Described in the Documentation: Use of the feature is explained in the user agent's documentation; or<br/> (b) Described in the Interface: Use of the feature is explained in the UA user interface; or<br/> (c) Platform Service: The feature is a service provided by an underlying platform; or<br/> (d) Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service). </td>
<td class="pri">A</td>
<td class="pri">Note: we did not test every browser feature to document implementation<br /><a href="https://support.mozilla.org/en-US/products/firefox/get-started">Firefox Documentation</a> </td>
<td class="pri"><a href="https://support.google.com/chrome/?p=help&ctx=menu#topic=3227046">Chrome Documentation</a> </td>
</tr>
<tr class="h3">
<td class="line-number">185</td>
<td class"whole-line"><strong class="title">3.2.3 Document All Features:</strong> For each user agent feature, at least one of the following is true: (Level AA)<br/> (a) Described in the Documentation: Use of the feature is explained in the user agent's documentation; or<br/> (b) Described in the Interface: Use of the feature is explained in the UA user interface; or<br/> (c) Platform Service: The feature is a service provided by an underlying platform; or<br/> (d) Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service). </td>
<td class="pri">AA</td>
<td class="pri">Note: we did not test every browser feature to document implementation<br /><a href="https://support.mozilla.org/en-US/products/firefox/get-started">Firefox Documentation</a> </td>
<td class="pri"><a href="https://support.google.com/chrome/?p=help&ctx=menu#topic=3227046">Chrome Documentation</a> </td>
</tr>
<tr class="h3">
<td class="line-number">186</td>
<td class"whole-line"><strong class="title">3.2.4 Changes Between Versions:</strong> Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. (Level AA) </td>
<td class="pri">AA</td>
<td class="pri"><a href="http://googlechromereleases.blogspot.com/">chrome: log of all revisions by version</a></td>
<td class="pri"><a href="https://www.mozilla.org/en-US/firefox/releases/"></a> Firefox changelogs for each version</a></td>
</tr>
<tr class="h3">
<td class="line-number">187</td>
<td class"whole-line"><strong class="title">3.2.5 Centralized View:</strong> There is a dedicated section of the documentation that presents a view of all features of the user agent necessary to meet the requirements of User Agent Accessibility Guidelines 2.0. (Level AAA)</td>
<td class="pri">AAA</td>
<td class="pri"><a href="https://support.mozilla.org/en-US/kb/accessibility-features-firefox-make-firefox-and-we">Documentation of accessibility features in Firefox</a></td>
<td class="pri"><a href="https://www.google.com/accessibility/all-products-features.html">chrome accessibility features for all products (chrome listed on the page)</a>
</td>
</tr>
<tr class="h3">
<td class="line-number">190</td>
<td class"whole-line"><strong class="title">3.3.1 Avoid Unpredictable Focus:</strong> The user can prevent focus changes that are not a result of explicit user request. (Level A) </td>
<td class="pri">A</td>
<td class="pri"> greasemonkey or something similar for IE, Chrome, Safari, FF is a possible solution. No other implementation or extensions were found.</td>
<td class="pri"> </td>
</tr>
<tr class="h3">
<td class="line-number">195</td>
<td class"whole-line"><strong class="title">4.1.1 Support Platform Accessibility Services:</strong> The user agent supports relevant platform accessibility services. (Level A) </td>
<td class="pri">A</td>
<td class="pri">Chrome, IE, Firefox, Safari</td>
<td class="pri">Chrome, IE, Firefox, Safari</td>
</tr>
<tr class="h3">
<td class="line-number">196</td>