-
Notifications
You must be signed in to change notification settings - Fork 2
/
LCcomments-20140122.html
2734 lines (2732 loc) · 166 KB
/
LCcomments-20140122.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>
<title>Disposition of Comments on UAAG 2.0 Working Draft of 23 May 2013</title>
<link href="/WAI/wai-main.css" rel="stylesheet" type="text/css"/>
<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;
}
</style>
</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></p>
<div id="skipwrapper"> <a id="skip" shape="rect">-</a></div>
<div>
<h1>Disposition of Comments: <br />
UAAG 2.0 and Implementing UAAG 2.0 Last Call<br />
Working Drafts of 7 November 2013 </h1>
<dl>
<dt>Updated on:</dt>
<dd>22 January, 2014</dd>
<dt>This Version</dt>
<dd><a href="http://w3.org/WAI/UA/2014/LCcomments-20140122.html">http://w3.org/WAI/UA/2014/LCcomments-20140122.html</a></dd>
<dt>Latest Version</dt>
<dd><a href="http://w3.org/WAI/UA/2013/commentsWD.html">http://w3.org/WAI/UA/2013/LCcomments.html</a></dd>
<dt>Previous Version:</dt>
<dd>first draft</dd>
</dl>
<p>This is a working document from the User Agent Accessibility Guidelines Working Group (UAWG) that details action taken on the @@ issues received from @@ commenters on the Last Call working drafts of 7 November 2013 of UAAG 2.0 and Implementing UAAG 2.0. The table includes relevent text from UAAG 2.0 and Implementing UAAG 2.0; the classification of the comment, the UAWG response, and whether the commenter agreed with the change. There may also be highlighted text in the Response column whether or not the change has been accepted into the <a href="http://www.w3.org/WAI/UA/UAAG20/">latest Editors' Draft</a>. </p>
<p>See also: <br />
<a href="http://www.w3.org/TR/2013/WD-UAAG20-20131107/">UAAG 2.0 Last Call Working Draft of 7 November 2013</a><br />
<a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-UAAG20-20131107/">Implementing UAAG 2.0 Working Draft of 7 November 2013 </a></p>
<h2>Comments Received from:</h2>
<dl>
<dt>Education & Outreach Working Group (EO)</dt>
<dd><a href="http://www.w3.org/WAI/EO/wiki/UAAG_review">http://www.w3.org/WAI/EO/wiki/UAAG_review</a></dd>
<dt>Wayne Dick (WD) - 2 issues</dt>
<dd><a href="http://lists.w3.org/Archives/Public/public-uaag2-comments/2013Dec/0000.html">http://lists.w3.org/Archives/Public/public-uaag2-comments/2013Dec/0000.html</a></dd>
<dt>James Craig, Apple (AP) - 2 issue</dt>
<dd>direct email</dd>
<dt>Silas Brown (SB) - 5 issues</dt>
<dd><a href="http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Jan/0000.html">http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Jan/0000.html</a></dd>
<dt>Dominic Mazzilli, Chrome (CR) - 7 issues</dt>
<dd><a href="http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Jan/0001.html">http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Jan/0001.html</a></dd>
<dt>Alex Li, Microsoft (MS)</dt>
<dd><a href="http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Jan/0002.html">http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Jan/0002.html</a></dd>
</dl>
<h2>Legend: </h2>
<ul>
<li><strong>Priority</strong>: The success criteria level (if applicable) A, AA, AAA</li>
<li><strong>Guidelines and Success Criteria</strong>: text from the 7 November 2013 Last Call Working Draft</li>
<li><strong>Comments</strong>: received from reviewer</li>
<li><strong>Type</strong>: substantive, editorial, question</li>
<li><strong>Response</strong>: the action taken by the group with a link to the minutes or survey documenting the decision. </li>
<li><strong>Disposition</strong>: the group response (proposal not accepted, accepted, partial accept, alternative action taken)</li>
<li><strong>Acknowledgement</strong>: from reviewer about our disposition of comment</li>
<li><strong>Highlighting</strong>: orange=Principle (heading level 2), green=Guideline (heading level 3)</li>
</ul>
<h2>Disposition of Comments</h2>
<table frame="void" cellspacing="0" cols="7" rules="none" border="0">
<colgroup>
<col width="5%" />
<col width="20%" />
<col width="20%" />
<col width="20%" />
<col width="15%" />
<col width="5%" />
<col width="10%" />
</colgroup>
<tbody>
<tr class="header">
<th align="center" valign="top" ><strong>Priority</strong></th>
<th align="center" valign="top" ><strong>Whole Line</strong></th>
<th align="center" valign="top" ><strong>Comments</strong></th>
<th align="center" valign="top" ><strong>Response</strong></th>
<th align="center" valign="top" ><strong>Disposition</strong></th>
<th align="center" valign="top" ><strong>type</strong></th>
<th align="center" valign="top" ><strong>Acknowledgment</strong></th>
</tr>
<tr>
<td align="left" valign="top"> </td>
<td align="left" valign="top"><strong>General Comments</strong></td>
<td align="left" valign="top"><p>CR01: Chrome has a general philosophy that users should not be presented with too many settings or switches to control. Settings that are only enabled by a small minority of users increase the perceived complexity for everyone else and also increase the number of possible configurations for the developer to support and test. We prefer many such features to be available via extensions or add-ons instead. This document contains a large number of recommendations for additional configurations a user can specify, presumably via a specific option or setting built-into the browser.</p>
<p> What do you think about having extensions available for each of these features, rather than building them into the browser? Would Chrome be considered compliant with this spec if we implemented all of these guidelines as extensions and published an easy-to-use catalog of these for users to browse and install the ones they want? </p>
<p>The "Implementing" spec even references Firefox add-ons, like Text Equivalent Expand Abbreviations. Do the spec authors feel that such features should be built into the browser, or merely that such an option must be available to users?</p></td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
</tr>
<tr>
<td align="left" valign="top"> </td>
<td align="left" valign="top"><strong>General Comments</strong></td>
<td align="left" valign="top">CR03: Some of the recommendations seem overly technical and narrow: for
example, the use-case for Show Element Hierarchy is that a user might want
to write a custom stylesheet and needs to determine the path to a
particular element within a page to write a style rule for it. However,
there are already more innovative solutions to this problem available. A
popular Chrome extension, StyleBot, lets the user simply click on any
element on the page and modify the custom stylesheet with a friendly dialog
interface. They can explore the classes that this element belongs to and
apply the same style change to all elements in that class. My concern is
just that these guidelines should not specify one narrow solution to a
problem that precludes a more clever implementation.
</td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
</tr>
<tr>
<td align="left" valign="top"> </td>
<td align="left" valign="top"><strong>General Comments</strong></td>
<td align="left" valign="top">CR04: Many of the guidelines are specific to a desktop computer, and written in
a way that's too narrow to apply to a web browser running on a phone,
tablet, or other device that may not have a keyboard. The guidelines should
be written in a way that explain the user need and don't assume that a
keyboard is available.</td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
</tr>
<tr>
<td align="left" valign="top"> </td>
<td align="left" valign="top"><strong>General Comments</strong></td>
<td align="left" valign="top">CR05: Many of the guidelines suggest features that are already available in
existing assistive technology - for example opening an elements list,
navigation by headings, or using voice control to jump to an element. Do
the guidelines really mean to suggest that the browser should reimplement
these as browser features rather than making them features of the AT? It's
not clear to me that browsers should be providing these features directly -
rather, they should expose rich information to AT via accessibility APIs,
and allow AT to innovate ways to present this information to diverse groups
of users.</td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
</tr>
<tr>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top">AP01:
I think most of the UAAG can already be achieved in most browsers with a combination of user style sheets and user scripts.</td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
</tr>
<tr class="h1">
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><h2>UAAG 2.0 Conformance Applicability Notes</h2></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Recognized Content Only</strong> UAAG 2.0 success criteria only apply to web content and its behaviors that can be recognized by user agents.</td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Optional Settings:</strong> Throughout UAAG 2.0, all required behaviors may be provided as optional preference settings unless a success criterion explicitly says otherwise. For example, if a success criteria requires high contrast between foreground text and its background, the user agent may also provide choices with low contrast. A required behavior does not need to be the default option unless the success criteria explicitly says otherwise.</td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>RFC 2119 language not used:</strong> UAAG 2.0 does not use RFC 2119 language (must, may, should) because these are guidelines and not interoperable specifications. These words in UAAG 2.0 don't have the same sense as they do in RFC 2119.</td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Simultaneous satisfaction of success criteria:</strong> Users can access all behaviors required by UAAG 2.0 at the same time (e.g. when the user resizes the viewport per 1.8.9, content is reflowed per 1.8.6), except where those behaviors are mutually exclusive.</td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="h1">
<td align="left" valign="top" ><br /></td>
<td align="left" valign="top" ><h2>PRINCIPLE 1</h2> - Ensure that the user interface and rendered content are <strong>perceivable</strong></td>
<td align="left" valign="top" ><br /></td>
<td align="left" valign="top" ><br /></td>
<td align="left" valign="top" ><br /></td>
<td align="left" valign="top" ><br /></td>
<td align="left" valign="top" ><br /></td>
</tr>
<tr class="h2">
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><h3>Guideline 1.1 - Provide access to alternative content </h3></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Summary: </strong>The user can choose to render any type of alternative content available. (1.1.1). The user can also choose at least one alternative such as alt text to be always displayed (1.1.3), but it's recommended that users also be able to specify a cascade (1.1.5), such as alt text if it's there, otherwise longdesc, otherwise filename, etc. It's recommended that the user can configure the caption text and that text or sign language alternative cannot obscure the video or the controls (1.1.4). The user can configure the size and position of media alternatives (1.1.6).</td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top">A</td>
<td align="left" valign="top"><strong>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)<br />
<br /> <strong>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.</td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top">A</td>
<td align="left" valign="top"><strong>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 align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top">A</td>
<td align="left" valign="top"><strong>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 align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top">AA</td>
<td align="left" valign="top"><strong>1.1.4 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 align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top">AA</td>
<td align="left" valign="top"><p><strong>1.1.5 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 AA)</p>
<ul>
<li><strong>Don't obscure controls:</strong> Displaying time-based media alternatives doesn't obscure recognized controls for the primary time-based media.</li>
<li><strong>Don't obscure primary media:</strong> The user can specify that displaying time-based media alternatives doesn't obscure the primary time-based media.</li>
<li><strong>Use configurable text:</strong> The user can configure recognized text within time-based media alternatives (e.g. captions) in conformance with 1.4.1.</li>
</ul>
<p><strong>Note:</strong> Depending on the screen area available, the display of the primary time-based media may need to be reduced in size to meet this requirement.</p></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AAA">
<td align="left" valign="top">AAA</td>
<td align="left" valign="top"><p><strong>1.1.6 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)</p>
<ul>
<li><strong>Resize:</strong> The user can resize alternative content for time-based media up to the size of the user agent's viewport.</li>
<li><strong>Reposition:</strong> 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.</li>
</ul>
<p><strong>Note 1:</strong> Depending on the screen area available, the display of the primary time-based media may need to be reduced in size or hidden to meet this requirement.</p>
<p><strong>Note 2:</strong> Implementation may involve displaying alternative content for time-based media in a separate viewport, but this is not required.</p></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="h2">
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><h3>Guideline 1.2 - Repair missing content </h3></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Summary: </strong>The user can request useful alternative content when the author fails to provide it. For example, showing metadata in place of missing or empty (1.2.1) alt text. The user can ask the browser to predict missing structural information, such as field labels, table headings or section headings (1.2.2).</td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top">AA</td>
<td align="left" valign="top"><strong>1.2.1 Support Repair by Assistive Technologies:</strong> If text alternatives for non-text content are missing or empty then both of the following are true: (Level AA)
<ul>
<li>The user agent doesn't attempt to repair the text alternatives by substituting text values that are also available to assistive technologies.</li>
<li> The user agent makes available metadata related to the non-text content available programmatically, but not via fields reserved for text alternatives.</li>
</ul></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AAA">
<td align="left" valign="top">AAA</td>
<td align="left" valign="top"><strong>1.2.2 Repair Missing Structure: </strong>The user can specify whether or not the user agent should attempt to insert the following types of structural markup on the basis of author-specified presentation attributes (e.g. position and appearance): (Level AAA)
<ul><li>Labels</li>
<li>Headers (e.g.&nbsp;heading markup, table headers)</li>
</ul></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="h2">
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><h3>Guideline 1.3 - Provide highlighting for selection, keyboard focus, enabled elements, visited links </h3></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Summary:</strong> The user can visually distinguish selected, focused, and enabled items, and recently visited links (1.3.1), with a choice of highlighting options that at least include foreground and background colors, and border color and thickness (1.3.2).</td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top">A</td>
<td align="left" valign="top"><strong>1.3.1 Highlighted Items: The user can specify that the following classes be highlighted so that each is uniquely distinguished: (Level A)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Selection</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Active keyboard focus (indicated by focus cursors and/or text cursors)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Recognized enabled input elements (distinguished from disabled elements)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Recently visited links</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top">AA</td>
<td align="left" valign="top"><strong>1.3.2 Highlighting Options: When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: (Level AA)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Foreground colors</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Background colors</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Borders (color, style, and thickness)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Size when the indicator is an image</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Blink rate (where implemented)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="h2">
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><h3>Guideline 1.4 - Provide text configuration </h3></td>
<td align="left" valign="top"><p>CR02:
Settings that allow the user too much control over the layout and formatting invariably cause some web pages to be unusable. As an example, the minimum font size setting can be great for accessibility. However, it can make many websites with more complicated layouts unusable because the relatives sizes of text vs other elements on the page can now be off by a substantial margin. In contrast, most browsers now support a "zoom" feature that magnifies all elements on the page proportionally. To a web author, this is equivalent to the user modifying the width of the window, a case that already needs to be handled gracefully.</p>
<p> I don't feel that we should be telling users that they can't use a website because the web author is making the text too small, or using a font that's inaccessible to them. However, it's also counterproductive to give the user so much control that too many sites become impossible to use, and web developers will have no incentive or ability to fix their sites since there are so many permutations they need to support. </p>
<p>For example, I worry that the ability to change line spacing, character spacing, or justification might create more compatibility problems than they solve accessibility problems. I don't have any objection to allowing the user to specify font subsitutions, in comparison. <br />
</p>
</pre></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Summary: The user can set text scale, color, and font family globally (1.4.1, Level A); set text size, color, and font family for element types (1.4.2, Level AA); set line spacing, character spacing, word spacing, text style, and justification globally (1.4.3, Level AA); set text style, margins, and borders for elements (1.4.5, Level AAA); set line spacing, capitalization, hyphenation, margins, and borders globally (1.4.6, Level AAA); and print configured and reflowed text (1.4.4 Level AA).</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Note 1: Success criteria 1.4.1, 1.4.3, and 1.4.6 address configuration at a global level, that is, it changes all of the text. Success criteria 1.4.2 and 1.4.5 are at an element type level, such as configuring just the heading text.</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Note 2: All of the success criteria under guideline 1.4 allow users to override the text characteristics specified by authors, and override user agent defaults.</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Note 3: The success criteria in guideline 1.4 can be met through user stylesheets. For platforms without user stylesheets, text configuration needs to be provide to users through the user agent's main user interface.</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top">A</td>
<td align="left" valign="top"><strong>1.4.1 Text Scale, Color, Font (Globally): The user can globally set all of the following characteristics of visually rendered text content: (Level A)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Text scale with preserved size distinctions (e.g. keeping headings proportional to main font)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Text color and background color, choosing from all platform color options</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Font family, choosing from all platform fonts</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top">AA</td>
<td align="left" valign="top"><strong>1.4.2 Text Size, Color and Font (by Element): The user can set all of the following characteristics of visually rendered text content for text element types including at least headings and input fields:(Level AA)</strong></td>
<td align="left" valign="top">WD01:
1.4.2: Problem: Users also need to style hyper links at the element. Solution: Add: "...at least heading input fields and links." <br /></td>
<td align="left" valign="top"><a href="http://www.w3.org/2014/01/16-ua-minutes.html#action01">Change</a> SC as recommended<br /></td>
<td align="left" valign="top">Accepted<br /></td>
<td align="left" valign="top">Substantive<br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Text size</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Text color and background color, choosing from all platform color options</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Font family, choosing from all platform fonts</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top">AA</td>
<td align="left" valign="top"><strong>1.4.3 Text Spacing and Style (Globally):</strong> The user can globally set all of the following characteristics of visually rendered blocks of text:(Level AA)</td>
<td align="left" valign="top">WD02:
1.4.3: Problem: the lengths for character spacing and word spacing appear to be absolutes. This would be wrong. Solution: Add a note. (so you will have Note 1 (as is) and a new Note 2) "
Note 2: The lengths for character and word spacing are interpreted the same as letter and word spacing CSS 2 and up. The length value is added to the default character and word spacing for the font. <br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top"> </td>
<td align="left" valign="top"><strong>1.4.3 Text Spacing and Style (Globally):</strong></td>
<td align="left" valign="top">SB05: 1.4.3 and 1.4.6 BOTH mention "line spacing" - does it really
need to be listed twice? With different settings ranges? or
maybe I've misunderstood (which means others might misunderstand). </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"> </td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Line spacing of at least 1.0, 1.3, 1.5, and 2.0 times the font height</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Character spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Word spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Text style (underline, italic, bold)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Justification (left, right, or full)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Note: For the purposes of UAAG 2.0, the base character width is the font width of the character commonly accepted as the base character for calculating kerning in the typography for that language (e.g. zero character in English).</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top">AA</td>
<td align="left" valign="top"><strong>1.4.4 Configured and Reflowed Text Printing: The user can print any rendered visual, non-time-based content to the user's choice of available printing devices. (Level AA)</strong></td>
<td align="left" valign="top"> </td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Note: The user must be able to print content as it is rendered on screen, reflecting user scaling, highlighting, and other modifications, but reflowable content is reflowed for the print margins.</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AAA">
<td align="left" valign="top">AAA</td>
<td align="left" valign="top"><strong>1.4.5 Text Style, Margins, Borders (by Element): The user can set all of the following characteristics of visually rendered text content for main text and for text element types including at least headings and input fields: (Level AAA)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AAA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Text style (underline, italic, bold)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AAA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Margins (for example, space above headings, indentation of lists)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AAA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Borders</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="AAA">
<td align="left" valign="top">AAA</td>
<td align="left" valign="top"><strong>1.4.6 Spacing, Capitalization and Hyphenation (Globally): The user can globally set all of the following characteristics of visually rendered blocks of text: (Level AAA)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AAA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Line spacing between 0.7 and 3.0 times the font height, at increments of 0.10</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AAA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Capitalization (overriding upper case and small caps style)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AAA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Word-breaking properties (auto-hyphenation)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AAA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Margins</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AAA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Borders</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Note: 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.</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="h2">
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Guideline 1.5 - Provide volume configuration </strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Summary: The user can adjust the volume of each audio track relative to the global volume level (1.5.1).</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top">A</td>
<td align="left" valign="top"><strong>1.5.1 Global Volume: 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)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="h2">
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Guideline 1.6 - Provide synthesized speech configuration </strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Summary: If synthesized speech is produced, the user can specify speech rate, volume, and voice (1.6.1, Level A), pitch and pitch range (1.6.2, Level AA), advanced synthesizer speech characteristics such as emphasis (1.6.3, Level AAA) and features such as spelling (1.6.4, Level AAA).</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top">A</td>
<td align="left" valign="top"><strong>1.6.1 Speech Rate, Volume, and Voice: If synthesized speech is produced, the user can specify the following: (Level A)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Speech rate</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Speech volume (independently of other sources of audio)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="A">
<td align="left" valign="top" bgcolor="#CCCCFF">A</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Voice, when more than one voice is available</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top">AA</td>
<td align="left" valign="top"><strong>1.6.2 Speech Pitch and Range: If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: (Level AA)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Pitch (average frequency of the speaking voice)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* Pitch range (variation in average frequency)</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><strong>Note: 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.</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AAA">
<td align="left" valign="top">AAA</td>
<td align="left" valign="top"><strong>1.6.3 Advanced Speech Characteristics: The user can adjust all of the speech characteristics provided by the speech synthesizer. (Level AAA)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr class="AA">
<td align="left" valign="top">AA</td>
<td align="left" valign="top"><strong>1.6.4 Synthesized Speech Features: If synthesized speech is produced, the following features are provided: (Level AA)</strong></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
<td align="left" valign="top"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF">* User-defined extensions to the synthesized speech dictionary.</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><strong>* "Spell-out": text is spelled one character at a time, or according to language-dependent pronunciation rules.</strong></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><strong>* 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).</strong></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#CCCCFF">AA</td>
<td align="left" valign="top" bgcolor="#CCCCFF"><strong>* At least two ways of speaking punctuation: spoken literally, and with punctuation understood from speech characteristics like pauses.</strong></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
<td align="left" valign="top" bgcolor="#CCCCFF"><br /></td>
</tr>
<tr class="AA">