-
Notifications
You must be signed in to change notification settings - Fork 2
/
index.html
2221 lines (2215 loc) · 140 KB
/
index.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>Disposition of Comments on UAAG 2.0 Working Draft of 25 September 2014</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;
}
</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 UAAG 2.0 Reference<br />
Working Drafts of 25 September 2014</h1>
<dl>
<dt>Updated on:</dt>
<dd>7 April, 2015</dd>
<dt>This Version (Github)</dt>
<dd><a href="http://jspellman.github.io/UAAG-LC-Comment/">http://jspellman.github.io/UAAG-LC-Comment/</a></dd>
</dl>
<p>This is a working document from the User Agent Accessibility
Guidelines Working Group (UAWG) that details action taken on the 22 issues received from 5 commenters on the working drafts of <a href="http://www.w3.org/TR/2014/WD-UAAG20-20140925/">25 September 2014 of UAAG 2.0</a> and <a href="http://www.w3.org/TR/2014/WD-UAAG20-Reference-20140925/">UAAG 2.0 Reference</a> (formerly Implementing UAAG 2.0). Most of these comments are in response to the request to accept the changes made to previous comments on the UAAG 2.0 Last Call Working Draft. </p>
<p>The following table includes
relevent text from 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>. If there was extensive discussion in UAWG about the issue, the word "UAWG" in the response is linked to the minutes of that meeting. </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> <br />
<a href="http://jspellman.github.io/UAAG-LC-Comment/LCcomments.html">Previous comments on Last Call Working Draft</a> </p>
<h2>Comments Received from:</h2>
<p>Note: done means that UAWG has process and answered the comment. confirmed means that the group has heard back from the commenter that the comments were accepted or there was no confirmation.
<dl>
<dt>Silas Brown (SB)- 3 issues <span class="done">[done]</span> <span class="done">confirmed</span></dt>
<dd><a href="http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Sep/0013.html">http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Sep/0013.html</a></dd>
<dt>Lisa Seeman (CA - Cognitive Accessibility Task Force) - 1 issue <span class="done">[done]</span> <span class="done">confirmed</span></dt>
<dd><a href="http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Oct/0001.html">http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Oct/0001.html</a></dd>
<dt>Cynthia Shelly (MS -Microsoft) - 6 issues <span class="done">[done]</span> <span class="under-discussion">*needs confirmation"</span></dt>
<dd><a href="http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Oct/0002.html">http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Oct/0002.html</a></dd>
<dt>Joseph Scheuhammer (JS - PFWG) - 3 issues <span class="done">[done]</span> <span class="done">confirmed</span> - Note: one issue was <a href="https://www.w3.org/WAI/UA/work/wiki/Comment_Response_20_March_2015#Follow_up_comment_from_Joseph_from_1_April_2015">continued</a></dt>
<dd><a href="https://lists.w3.org/Archives/Public/w3c-wai-ua/2014OctDec/0080.html">https://lists.w3.org/Archives/Public/w3c-wai-ua/2014OctDec/0080.html</a></dd>
<dt>Shawn Henry (SH - EOWG) - 9 issues <span class="done">[done]</span> <span class="done">confirmed</span> - Note: some issues were <a href="https://www.w3.org/WAI/UA/work/wiki/Comment_Response_20_March_2015">continued</a></dt>
<dd><a href="https://lists.w3.org/Archives/Public/w3c-wai-ua/2014OctDec/0071.html">https://lists.w3.org/Archives/Public/w3c-wai-ua/2014OctDec/0071.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 25 September 2014 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>
</ul>
<h2>Disposition of Comments</h2>
<table cellspacing="0" cols="7" rules="none" border="0">
<colgroup><col width="38" /><col width="281" /><col width="68" /><col width="68" /><col width="68" /><col width="68" /><col width="68" /></colgroup>
<tbody>
<tr>
<td height="17" align="left">Priority</td>
<td align="left">Whole Line</td>
<td align="left">Comments</td>
<td align="left">Response</td>
<td align="left">Disposition</td>
<td align="left">type</td>
<td align="left">Acknowledgment</td>
</tr>
<tr>
<td align="left" valign="top"> </td>
<td align="left" valign="top">Introduction: Definition of User Agent</td>
<td align="left" valign="top"><a name="MS01" id="MS01"></a>MS01: Definition of "User agent" should not include "web-based user agent"
We do not agree that a "web-based user agent" is a legitimate concept. If it's web-based, it's content. WCAG was written to cover web applications, including those that render content. UAAG should not be covering that. The target audience of this document should be user agent implementers, not end users. The fact that end users don't understand how it is engineered is not relevant.</p></td>
<td align="left" valign="top"><p><span class="done">[done]</span> Instead of removing web-based browsers from the scope of UAAG we have: </p><ul>
<li> labeled in UAAG Reference the SCs that typically are implemented at the web-based browser level</li>
<li>added a section explaining this to the UAAG Introduction and/or conformance section</li>
<li>changed the definition of user agent (#def-user-agent) in the glossary to give more specific guidance. </li>
</ul></td>
<td align="left" valign="top">Not accepted</td>
<td align="left" valign="top">substantive</td>
<td align="left" valign="top"> </td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left">General: UAAG Reference</td>
<td id="MS05">MS05: Examples in the implementation document do not make distinction of content, browser, assistive technologies, and OS We still feel that this area of UAAG is fundamentally flawed. UAAG needs to clarify what should be done in the browser, where the browser should rely on OS features, where it should go beyond them, and what should be done by AT. The target audience of this document should be user agent implementers, not end users. We don't believe it to be relevant that end users may not understand the engineering considerations of the accessibility stack.</td>
<td align="left"><span class="done">[done]</span> UAWG added this information to the Reference document in a new section for each SC: "Typically implemented by"</td>
<td align="left">Accepted</td>
<td align="left">substantive</td>
<td align="left"> </td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left">General Comments: Levels</td>
<td id="MS06">MS06: Setting realistic Level A, AA, and AAA success criteria We think that many of the current A success criteria do not meet the test of a,b,c,d as defined in our original comment. For <a href="http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Oct/0002.html">example</a>:</td>
<td align="left"><span class="done">[done]</span>. see individual success criteria</td>
<td align="left">Partial accept</td>
<td align="left">substantive</td>
<td align="left"> </td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">PRINCIPLE 1 - Ensure that the user interface and rendered content are perceivable</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Guideline 1.1 - Provide access to alternative content </td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Summary: The user can choose to render any type of alternative content available (1.1.1) with an indicator that the alternative content is present (1.1.2) or a placeholder replacing the non-text content (1.1.3) . It's recommended that users can also choose at least one alternative, such as alt text, to be displayed by default (1.1.4). It's recommended that caption text or sign language alternative cannot obscure the video or the controls (1.1.5) and that the user can configure the size and position of media alternatives (1.1.6).</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left">A</td>
<td align="left">1.1.1 Render Alternative Content: The user can choose to render any type of recognized alternative content that is present for a content element. (Level A)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Note: 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"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">A</td>
<td align="left">1.1.2 Indicate Unrendered Alternative Content: 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">MS06: 1.1.2 what requirement of WCAG does this support? Also, this would be better handled by AT than by a browser.</td>
<td align="left"><span class="done">[done]</span> It supports UAAG 1.1.1, and provides notification to users who want alternative content but are not using assistive technology. E.g. for example a person who has difficulty processing abbreviations can see which acronyms have definitions. <br /></td>
<td align="left">Answered<br /></td>
<td align="left">Question<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left">A</td>
<td align="left">1.1.3 Replace Non-Text Content: 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">MS06: 1.1.3 What requirement of WCAG does this support?
<br /></td>
<td align="left"><span class="done">[done]</span> People who want low contrast that find high contrast painful. People with cognitive issues who want to suppress icons and see alt text. <br /></td>
<td align="left">Answered<br /></td>
<td align="left">Question<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left">AA</td>
<td align="left">1.1.4 Provide Configurable Alternative Content Defaults: 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">MS06: 1.1.4, 1.1.5 are AA
<br /></td>
<td align="left"><span class="done">[done]</span><br /></td>
<td align="left">Accept<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="66" align="left">AA</td>
<td align="left">1.1.5 Facilitate Clear Display of Alternative Content for Time-based Media: For recognized on-screen alternative content for time-based media (e.g. captions, sign language video), the following are all true: (Level AA)<br /> * Don't obscure controls: Displaying time-based media alternatives doesn't obscure recognized controls for the primary time-based media.<br /> * Don't obscure primary media: The user can specify that displaying time-based media alternatives doesn't obscure the primary time-based media.<br /> * Use configurable text: The user can configure recognized text within time-based media alternatives (e.g. captions) in conformance with 1.4.1.</td>
<td align="left">MS06: 1.1.5 first two bullets seem like A to support WCAG 1.2. I believe the third bullet is required under CVAA but not WCAG, so can stay AA<br /></td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2014/10/28-ua-minutes.html#item05">UAWG</a> agrees. <a href="http://www.w3.org/2014/12/18-ua-minutes.html#item02">UAWG</a> split 1.1.5 into two different SC with different levels.<br /></td>
<td align="left">Accept<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Note: 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.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="50" align="left">AAA</td>
<td align="left">1.1.6 Allow Resize and Reposition of Time-based Media Alternatives: 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 up to the size of the user agent's viewport.<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.</td>
<td align="left">MS06: 1.1.6 is also required by CVAA, but can stay AAA<br /></td>
<td align="left"><span class="done">[done]</span> UAWG agrees. <br /></td>
<td align="left">Accept<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Note 1: 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.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">Note 2: Implementation may involve displaying alternative content for time-based media in a separate viewport, but this is not required.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Guideline 1.2 - Repair missing content </td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">Summary: 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"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="50" align="left">AA</td>
<td align="left">1.2.1 Support Repair by Assistive Technologies: If text alternatives for non-text content are missing or empty then both of the following are true: (Level AA)<br /> * The user agent doesn't attempt to repair the text alternatives by substituting text values that are also available to assistive technologies.<br /> * The user agent makes available metadata related to the non-text content available programmatically, but not via fields reserved for text alternatives.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="50" align="left">AAA</td>
<td align="left">1.2.2 Repair Missing Structure: 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)<br /> * Labels<br /> * Headers (e.g. heading markup, table headers)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Guideline 1.3 - Provide highlighting for selection, keyboard focus, enabled elements, visited links </td>
<td align="left">MS06: 1.3 should be refactored so that level A requires picking up OS settings for these things where they exist, and levels AA or AAA would require adding features beyond what is available on the OS settings, as described in current 1.3.1 and 1.3.2<br /></td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2014/10/28-ua-minutes.html#item09">UAWG</a> agreed 5.1.3 covers the requirement to pick up OS settings. We agree to reword 5.1.3 to make it more clear. 1.3 was also rewritten for effective testing. <br />
<br /></td>
<td align="left">Accept<br /></td>
<td align="left">substantive</td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Summary: The user can visually distinguish between 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"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="97" align="left">A</td>
<td align="left">1.3.1 Highlighted Items: The user can specify that the following classes be highlighted so that each is uniquely distinguished: (Level A)<br /> * Selection<br /> * Active keyboard focus (indicated by focus cursors and/or text cursors)<br /> * Recognized enabled input elements (distinguished from disabled elements)<br /> * Recently visited links<br /> * Found search results</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="97" align="left">AA</td>
<td align="left">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)<br /> * Foreground colors<br /> * Background colors<br /> * Borders (color, style, and thickness)<br /> * Size when the indicator is an image<br /> * Blink rate (where implemented)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Guideline 1.4 - Provide text configuration </td>
<td align="left">MS06: 1.4 Should be refactored so that level A requires picking up OS settings for basic text settings where they exist, and levels AA or AAA would require adding features beyond what is available on the OS settings<br /></td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2015/02/12-ua-minutes.html#item03">UAWG</a> agreed and added a new success criteria 1.4.5. UAWG did not make changes to the levels. <br /></td>
<td align="left">Partial agree<br /></td>
<td align="left">substantial<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"> </td>
<td align="left">Guideline 1.4</td>
<td align="left">SH04: *Inconsistencies*<br />
I'm not sure if the inconsistencies below are on purpose or in error? :-)
<p>* 1.4.1 Basic text formatting (Globally):… Text scale with…<br />
1.4.2 Basic text formatting (by Element): … Text size or scale</p>
<p>* 1.4.1 Basic text formatting (Globally):…<br />
Text color and background color, choosing from all platform color options<br />
Font family, choosing from all installed fonts [this says "installed" &<br />
others say "platform"]<br />
1.4.2 Basic text formatting (by Element):<br />
Text color and background color, choosing from all platform color options<br />
Font family, choosing from at least all platform fonts</p></td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2015/01/08-ua-minutes.html#item05">UAWG</a> choose the wording with care. Globally, text is scaled, but by element it can be sized or scaled. Fonts are installed, but colors are chosen from the platform. We reviewed the other success criteria to make sure the wording was consistent. </td>
<td align="left">Not accepted</td>
<td align="left">editorial</td>
<td align="left">No specific response. Her <a href="https://lists.w3.org/Archives/Public/w3c-wai-ua/2015JanMar/0055.html">email</a> ends with "I am fine with all the other changes noted above."</td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">Summary: The user can set text scale, color, style, line spacing, and font family globally (1.4.1, Level A). It is recommended that users set text size, color, line spacing, text style and font family for element types (1.4.2, Level AA); set character spacing, justification and margin sizes globally (1.4.3, Level AA); set capitalization, hyphenation, and borders globally (1.4.5, Level AAA); and print configured and reflowed text (1.4.4 Level AA).</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Note 1: Success criteria 1.4.1, 1.4.3, and 1.4.5 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.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">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.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">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.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="82" align="left">A</td>
<td align="left">1.4.1 Basic text formatting (Globally): 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</td>
<td id="MS03"><a name="ms03" id="ms03"></a>MS03: Separation between browsers and OS We still believe that 1.4.1 should be separated into a level A criterion to pick up the OS settings where they exist, and level AA or level AAA criterion to go beyond the settings available on the platform.</td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2015/02/12-ua-minutes.html#item03">UAWG</a> added a new success criteria, 1.4.5, to pick up the OS settings. The new SC is Level AA. <a href="http://www.w3.org/2014/10/28-ua-minutes.html#item15">UAWG</a> did not change the other SC levels. UAWG made additional changes to support this, which are itemized under <a href="#sh08">SH08</a><br /></td>
<td align="left">Partial accept<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="97" align="left"> </td>
<td align="left">1.4.1 Basic text formatting (Globally):</td>
<td align="left">SH01: I'm afraid that below isn't specific enough and you need to say<br />
something about specific values &/or increments.
<p>1) * Current text: "Line spacing, choosing from a range with at least three values"<br />
As it is written, a user agent that provided 1.0, 1.1, 1.2 would meet<br />
this criteria; however, that doesn't meet the needs of most users who<br />
need increased line spacing, as most need between 1.25 and 2.0.<br />
</p></td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2015/01/08-ua-minutes.html#item01">UAWG</a> changed 1.4.1 to <br />
* Line spacing, choosing from a range with at least three values up to at least 2 times the default. UAWG added Note 4 to the introduction of 1.4:<br />
Note 4: When it comes to magnification, size, or spacing, the optimum value for a given user would vary based on their visual impairment and the size of the content they’re reading. Therefore it’s recommended that user agents provide a wider range of values, and a greater number of increments, to allow the user to adjust the view for their current task. <br />
UAWG added a sentence to the Intent of 1.4.1:<br />
At a minimum, it is recommended to offer line spacing options of 1, 1.25, 1.5 and 2.0. </td>
<td align="left">Accept</td>
<td align="left">substantive</td>
<td align="left"><p>SLH: Interesting way to cover it. Seems like it will work well along with the specific suggestions in the Reference. SLH: I note 1.4.1 says: * Line spacing, choosing from a range with at least three values up to at least 2 times the default * Text style, choosing to turn on/off underline, italic, bold and 1.4.2 says: * Line spacing, choosing from a range with at least three values * Text style (underline, italic, bold) Should these be the same or is there a reason that they are different? </p>
<p>SLH: [minor] "When it comes to magnification, size, or spacing, the optimum value for a given user would vary based on their visual impairment..." limits users who need this to people with visual impairment; however, many people with cognitive impairments also need uncommon text size and spacing especially. An idea to make it more broadly encompassing and simple is to replace the first sentence with: "Users have varying needs for text size and spacing."</p>
<p>> UAWG added a sentence to the Intent of 1.4.1: <br />
><a href="http://w3c.github.io/UAAG/UAAG20-Reference/#sc_141-i">http://w3c.github.io/UAAG/UAAG20-Reference/#sc_141-i</a> <br />
> At a minimum, it is recommended to offer line spacing options of 1, 1.25, 1.5 and 2.0. </p>
<p>SLH: I agree that it's good to leave some flexibility in the normative standard and then provide specific suggestions in the informative Reference. Good work! </p></td>
</tr>
<tr>
<td height="97" align="left"> </td>
<td align="left">1.4.1 Basic text formatting (Globally):</td>
<td align="left">SH05: *missing* "Text style (underline, italic, bold)"<br />
Current text has it only provided by Element; it is missing from Globally.</td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2015/01/08-ua-minutes.html#item06">UAWG</a> added a bullet to 1.4.1: Text style, choosing to turn on/off underline, italic, bold</td>
<td align="left">Accept</td>
<td align="left">substantive</td>
<td align="left"><p>No specific response. Her <a href="https://lists.w3.org/Archives/Public/w3c-wai-ua/2015JanMar/0055.html">email</a> ends with "I am fine with all the other changes noted above."</p></td>
</tr>
<tr>
<td height="97" align="left"> </td>
<td align="left">1.4.1 Basic text formatting (Globally):</td>
<td align="left"><a name="sh08" id="sh08"></a>SH08: "Note: Any user settings from the platform for these characteristics<br />
are implemented."<br />
I cannot figure out what this means.</td>
<td align="left"><span class="done">[done]</span> This note was added in response to comments from Microsoft in <a href="#ms03">MS03</a>. UAWG removed the note and took the following actions:
a) removed the note from 1.4.1 and 1.3.1 because the notes are too broad
b) added a new success criterion "1.4.5: Default to platform text settings: The user can specify that platform text settings be used as the default values for text configuration. (Level AA)"
c) clarified 5.1.3 so that it only applies to implementing the accessibility guidelines of the platform and not to user settings
d) removed 1.4 note #1 because it was incorporated into the success criteria handles
e) moved 1.4 note to Conformance Applicability Notes</td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left">No specific response. Her <a href="https://lists.w3.org/Archives/Public/w3c-wai-ua/2015JanMar/0055.html">email</a> ends with "I am fine with all the other changes noted above."</td>
</tr>
<tr>
<td height="97" align="left">AA</td>
<td align="left">1.4.2 Basic text formatting (by Element): 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 or scale<br /> * Text color and background color, choosing from all platform color options<br /> * Font family, choosing from at least all platform fonts<br /> * Line spacing, choosing from a range with at least three values<br /> * Text style (underline, italic, bold)</td>
<td align="left">MS06: 1.4.2 should be handled by AT<br /></td>
<td align="left"><p><span class="done">[done]</span> <a href="http://www.w3.org/2014/10/28-ua-minutes.html#item16">UAWG</a> decided that 1.4.2 was important for people who do not necessarily use AT, and there are implementations using user stylesheets or in Extensions. UAWG added a section in Reference "Applies To" for each success criteria. <br />
</p></td>
<td align="left">Not accepted<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="66" align="left">AA</td>
<td align="left">1.4.3 Blocks of text (Globally): 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 align="left">MS06: 1.4.3 should be handled by AT<br /></td>
<td align="left"><span class="done">[done]</span> See 1.4.2 In addition, UAWG removed the note (which no longer applied). UAWG added a section to each success criteria in Reference, "Applies To". <br /></td>
<td align="left">Partial accept<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">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).</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="82" align="left"> </td>
<td align="left">1.4.3 Blocks of text (Globally)</td>
<td align="left">SH03: * Current text: "Character spacing, choosing from a range with at least 5 values"<br />
This may have the same issue as above, although maybe not because the<br />
range of character spacing needed is far less, afaik.</td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2015/01/08-ua-minutes.html#item04">UAWG</a> added a sentence to UAAG Reference: "It is recommended to provide a range of character spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width. "</td>
<td align="left">Accept</td>
<td align="left">substantive</td>
<td align="left">No specific response. Her <a href="https://lists.w3.org/Archives/Public/w3c-wai-ua/2015JanMar/0055.html">email</a> ends with "I am fine with all the other changes noted above."</td>
</tr>
<tr>
<td height="82" align="left">AA</td>
<td align="left">1.4.4 Configured and Reflowed Text Printing: The user can print the rendered content, and the following are all true: (Level AA)<br /> (a) any visual, non-time-based, rendered content can be printed<br /> (b) the user can choose between available printing devices<br /> (c) the user can have content printed as it is rendered on screen, reflecting any user scaling, highlighting, and other modifications<br /> (d) the user can have printed content reflow as if the top-level viewport had been resized to match the horizontal dimension of the printing device's printable area</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="66" align="left">AAA</td>
<td align="left">1.4.5 Advanced text formatting (Globally): 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</td>
<td align="left">MS06: 1.4.5 why is a global setting lower priority than a per-object setting? It seems far easier to implement and more useful.<br /></td>
<td align="left"><span class="done">[done]</span> UAWG decided to remove the word "global". <br /></td>
<td align="left">Accept<br /></td>
<td align="left">Substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left">1.4.5 Advanced text formatting (Globally)</td>
<td align="left">SH06: * I had suggested more element-level customization at Level AAA that is missing from the current text. Given that it at Level AAA, does it make sense to leave it in there?</td>
<td align="left"><span class="done">[done]</span> UAWG moved around the levels of element-level customization and we believe that all of the items are included with the exception of Word spacing, which we had deliberately removed. <br /></td>
<td align="left">Partial accept</td>
<td align="left">substantive</td>
<td align="left"><p>SLH: In the latest Editor's draft, I am still not able to find the following for element-level: * Margins * Borders (fyi, These seem to be commonly-used ways to help indicate different heading levels by advanced user stylesheet users, e.g., see <<a href="http://www.tader.info/ex-displays.html">http://www.tader.info/ex-displays.html</a>>)</p></td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left">1.4.5 Advanced text formatting (Globally)</td>
<td align="left">SH07: Word spacing seems to be missing all together. Is that an error or<br />
conscious decision?</td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2015/01/29-ua-minutes.html#item04">UAWG</a> put word spacing back as a new bullet in 1.4.5 Word spacing, choosing from a range with at least 5 values </td>
<td align="left">Accepted</td>
<td align="left">substantive</td>
<td align="left">No specific response. Her <a href="https://lists.w3.org/Archives/Public/w3c-wai-ua/2015JanMar/0055.html">email</a> ends with "I am fine with all the other changes noted above."</td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">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.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Guideline 1.5 - Provide volume configuration </td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Summary: The user can adjust the volume of each audio track relative to the global volume level (1.5.1).</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left">A</td>
<td align="left">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)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Guideline 1.6 - Provide synthesized speech configuration </td>
<td id="MS02">MS02: Separation of assistive technologies from user agents We accept the UAAG disposition. However, we think it would be useful to take some of the text from your response to our comment and add it as a note in the document.</td>
<td align="left"><span class="done">[done]</span> UAWG added a note to 1.6: <span class="sc-notes">"If browsers provide speech output for mainstream users, they should make the speech configurable enough to be usable by a wide range of individuals. When an extension adds speech output to the user agent, it becomes part of the user agent, and therefore should meet the requirements of 1.6." </span><br /></td>
<td align="left">Accept<br /></td>
<td align="left">substantive</td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">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).</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="66" align="left">A</td>
<td align="left">1.6.1 Speech Rate, Volume, and Voice: If synthesized speech is produced, the user can specify the following: (Level A)<br /> * Speech rate<br /> * Speech volume (independently of other sources of audio)<br /> * Voice, when more than one voice is available</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="50" align="left">AA</td>
<td align="left">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)<br /> * Pitch (average frequency of the speaking voice)<br /> * Pitch range (variation in average frequency)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">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.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left">AAA</td>
<td align="left">1.6.3 Advanced Speech Characteristics: If synthesized speech is produced, the user can adjust all of the speech characteristics provided by the speech synthesizer. (Level AAA)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="82" align="left">AA</td>
<td align="left">1.6.4 Synthesized Speech Features: 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 align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left">AA</td>
<td align="left">1.6.5 Synthesized Speech Language: If synthesized speech is produced and more than one language is available, the user can change the language. (Level AA)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">Guideline 1.7 - Enable configuration of user stylesheets </td>
<td align="left">MS06: 1.7 user style sheets should be AAA. They are not a feasible solution. They don't work with the modern web, where styles are used for UI configuration, and they are too technical for typical end users. Style sheet modification makes some sense as a programmatic interface available to AT developers, but not as an end-user feature.<br /></td>
<td align="left"><span class="done">[done]</span> see success criteria below for individual changes<br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">Summary: The user agent supports user stylesheets (1.7.1, Level A), the user can choose which if any user-supplied (1.7.2, Level A) and author-supplied (1.7.3, Level A) stylesheets to use, and the user can save stylesheets (1.7.4, Level AA).</td>
<td id="MS08">MS08: Realistic expectation of the end users We still do not agree that user stylesheets are a reasonable end user feature. User Stylesheets are too technical to be an end user feature. They make sense only as a programmatic interface available to AT developers. We would be satisfied if the references to "users can" were changed to "AT can" or "developers can".</td>
<td align="left"><span class="done">[done]</span> UAWG has found implementations of user stylesheets and have received positive comment from other major browser to keep user stylesheets. <br /></td>
<td align="left">Not accepted<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">A</td>
<td align="left">1.7.1 Support User Stylesheets: If the user agent supports a mechanism for author stylesheets, the user agent also provides a mechanism for user stylesheets. (Level A)</td>
<td align="left">MS06, MS08<br /></td>
<td align="left"><span class="done">[done]</span> UAWG agreed to change the level to AA. Examples do exist, so we did not want to change it to AAA. There are extensions and browsers that provide a non-expert user interface, so it can be done. <br /></td>
<td align="left">Partial accept<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="50" align="left">A</td>
<td align="left">1.7.2 Apply User Stylesheets: If user stylesheets are supported, then the user can enable or disable user stylesheets for: (Level A)<br /> * All pages on specified websites, or<br /> * All pages</td>
<td align="left">MS06, MS08<br /></td>
<td align="left"><span class="done">[done]</span> UAWG agreed to change the level to AA. Examples do exist, so we did not want to change it to AAA. There are extensions and browsers that provide a non-expert user interface, so it can be done. <br /></td>
<td align="left">Accept<br /></td>
<td align="left">substantive</td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">A</td>
<td align="left">1.7.3 Disable Author Stylesheets: 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 align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">AA</td>
<td align="left">1.7.4 Save Copies of Stylesheets: 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 align="left" id="SB01"><p>SB01: Regarding SB01 (not sure if 1.7.4 Save Copies of Stylesheets is
really needed), yes the new additional explanation is good,
especially the point about making sure the stylesheet is
pretty-printed (which is not usually possible if you simply
inspect the page's source code and fetch the stylesheet URLs
from it, which is what I'm in the habit of doing). </p>
<p>
Highly complex stylesheets can still be difficult to make sense
of though, even when pretty-printed. Some current browsers have
"inspect this element" functionality which can help here - they
tell you exactly which CSS rules were applied to the element
you pointed at, and, as a bonus, include any overrides that were
generated by a script rather than a CSS file.
</p>
<p>
One addition that might be useful is in the case when a page's
styles come from not just one CSS file but quite a lot of them
(I've seen sites with over 20 CSS files all loaded from the same
page, and no they weren't alternates, they were ALL applied) - the
user might choose whether to save them individually or to merge.
But I wouldn't worry too much about a browser lacking that addition.
</p>
<p>
And one reason why it might be a good idea to have this function
from inside the browser (rather than relying on command-line
tools like "wget") is the page might be available only from
behind a "login" page, and it's often quite a chore to set up
wget with the correct authentication cookies just to get a copy
of all the CSS files. (True, some servers will serve the CSS
files even without correct authentication, but that's not always
the case.)</p></td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2014/11/06-ua-minutes.html#item08">UAWG</a> added a new paragraph to the Intent of 1.7.4. <br /></td>
<td align="left">Accept<br /></td>
<td align="left">substantive<br /></td>
<td align="left">
Accepted</td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">Guideline 1.8 - Help users to orient within, and control, windows and viewports </td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">Summary: The user agent provides programmatic and visual cues to keep the user oriented. These include highlighting the viewport (1.8.1, Level A) and customizing the highlighting attributes (1.8.7, Level AA), keeping the focus within the viewport (1.8.2 & 1.8.6, Level A), resizing the viewport (1.8.8, Level A), providing scrollbars that identify when content is outside the visible region (1.8.3, Level A) and which portion is visible (1.8.4, Level A), changing the size of graphical content with zoom (1.8.5, Level A & 1.8.7, Level A), and restoring the focus and point of regard when the user returns to a previously viewed page (1.8.9, Level AA). The user can specify that all viewports have the same user interface elements (1.8.12, Level AA), if and how new viewports open (1.8.10, Level AA), and whether the new viewport automatically gets focus (1.8.11, Level AA). The user can specifiy that multi-column text blocks be reflowed into a single column (1.8.14, Level AA), that the user can override absolute layout dimensions (1.8.15, Level AA), and linearize the content (1.8.16, Level AA). The user can mark items in a web page and use shortcuts to navigate back to marked items. (1.8.17, Level AAA).</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">A</td>
<td align="left">1.8.1 Highlight Viewport: The user can have the viewport with the input focus be highlighted. (Level A)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">A</td>
<td align="left">1.8.2 Move Viewport to Selection and Focus: 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 align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">A</td>
<td align="left">1.8.3 Provide Viewport Scrollbars: 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 align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">A</td>
<td align="left">1.8.4 Indicate Viewport Position: The user can determine the viewport's position relative to the full extent of the rendered content. (Level A)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="50" align="left">A</td>
<td align="left">1.8.5 Allow Zoom: 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 align="left">SH02: * Current text: "1.8.5 Allow Zoom: The user can rescale content within<br />
top-level graphical viewports as follows: (Level A) Zoom in: to 500% or<br />
more of the default size..."<br />
As it is written, a user agent that provided just two options for zoom:<br />
100% and 500%, would meet this criteria; however, that's not<br />
sufficiently accessible because the vast majority of users who need zoom<br />
will need it at a percent in between 100 & 500%.<br /></td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2015/01/08-ua-minutes.html#item03">UAWG</a> does not accept the comment because this is already well implemented, the UA already have nearly infinite zoom up to 500%. UAAG wording is agnostic and allows UAs to use what ever method to provide the scaling to 500%<br /></td>
<td align="left">Not accepted<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><p>SLH: I agree that most UAs today provide zoom at any increment - yeah! I do still think it is *very important that the standard include what users need*, even if it is already implemented in today's UAs -- to ensure that it is included in future UAs. (fyi, A common UA today provides the following zoom options in its interface: 10, 25, 50, 75, 100, 125, 150, 200, 400, 800, 1600, 2400, 3200, 6400. So between 150% and 400% --probably the most commonly-needed range-- there is only one option: 200%, which leaves out a lot of users' needs.) </p>
<p> </p></td>
</tr>
<tr>
<td height="18" align="left">A</td>
<td align="left">1.8.6 Maintain Point of Regard: The point of regard remains visible and at the same location within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed. (Level A)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">AA</td>
<td align="left">1.8.7 Customize Viewport Highlighting: When highlighting viewports as specified by 1.8.1 Highlight Viewport, the user can customize attributes of the viewport highlighting mechanism (e.g. blink rate for blinking, color and width of borders). (Level AA)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">AA</td>
<td align="left">1.8.8 Allow Viewport Resize: The user can resize viewports within restrictions imposed by the platform, overriding any values specified by the author. (Level AA)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="82" align="left">AA</td>
<td align="left">1.8.9 Provide Viewport History: 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<br /> (c) selection, and<br /> (d) user's form field entries</td>
<td align="left">MS06: 1.8.9 seems difficult to implement and should be AAA<br /></td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2014/10/28-ua-minutes.html#item19">UAWG</a> decided to remove selection because it was difficult, and we added an (informative) note that that recommended that selection also be restored. We found implementations of (a), (b) and (d) and did not change the level. <br /></td>
<td align="left">Partial accept<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">AA</td>
<td align="left">1.8.10 Allow Top-Level Viewport Open on Request: The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). (Level AA)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">AA</td>
<td align="left">1.8.11 Allow Top-Level Viewport Focus Control: 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 id="SB03">SB03: Regarding SB03 (1.8.11 Allow Top-Level Viewport Open on
Request), I believe the problem I mentioned is caused by scripts
intercepting the "mousedown" or "mouseup" event (rather than the
"click" event), and therefore intercepting middle-clicks and
(unintentionally?) causing these to perform some action on the
page instead of opening the link in a new window. One solution
might be to allow the user to specify which mouse buttons are
allowed to generate Javascript events. For example, if the user
says "do not allow any mouse buttons to generate Javascript
events" then no click or mousedown / mouseup events are
generated and clicks always perform the default browser
behaviour; if the user says "allow only the left mouse button to
generate Javascript events" then the other buttons will not; if
the user says "allow left and right but not middle" then pages
can override context menus but cannot override whatever the
middle button is bound to (e.g. "open in new tab"). I'm not
sure how exactly these options should be described to the user,
or where to put them (probably in an "advanced" section
somewhere), but being able to tell the browser not to generate
JS events when I middle-click would stop a lot of annoying sites
from overriding this "open link in new tab" shortcut. (Yes,
there will be times when the site is so script-driven that "open
in new tab" can't work anyway, but in these cases the user would
find out soon enough; I find in most cases "open in new tab"
certainly CAN work - and DOES work when you bring up the context
menu and select it from that - but the site simply prevents
middle-click from doing that job.)<br /></td>
<td align="left"><span class="done">[done]</span> UAWG did not accept this comment because 1.8.11 is only concerned about IF the new window captures focus. The middle-button-click is too technology specific to belong in the success-criteria. <br /></td>
<td align="left">Not accepted<br /></td>
<td align="left">substantive<br /></td>
<td align="left">
Accepted</td>
</tr>
<tr>
<td height="18" align="left">AA</td>
<td align="left">1.8.12 Allow Same User Interface: The user can specify that all top-level viewports (e.g. windows or tabs) follow the defined user interface configuration. (Level AA)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">AA</td>
<td align="left">1.8.13 Multi-Column Text Reflow: The user can specify that recognized multi-column text blocks each be reflowed into a single column. (Level AA)</td>
<td align="left">SH09: And some typos-type stuff I noticed:<br />
* "The user can specifiy that multi-column text blocks be reflowed into<br />
a single column (1.8.14, Level AA)"<br />
specifiy -> specify<br />
* "Summary: ... The user can specifiy that multi-column text blocks be<br />
reflowed into a single column (1.8.14, Level AA)"<br />
doesn't match below: "1.8.13 Multi-Column Text Reflow:" ... "1.8.14<br />
Ignore Fixed Unit Dimensions:"<br /></td>
<td align="left"><span class="done">[done]</span><br /></td>
<td align="left">Accept<br /></td>
<td align="left">editorial</td>
<td align="left">No specific response. Her <a href="https://lists.w3.org/Archives/Public/w3c-wai-ua/2015JanMar/0055.html">email</a> ends with "I am fine with all the other changes noted above."</td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">Note: 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.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left">AA</td>
<td align="left">1.8.14 Ignore Absolute Layout Dimensions: The user can have the user agent override author-specified absolute layout dimensions. (Level AA)</td>
<td align="left">MS06: 1.8.14 will break a lot of content and is a bad idea. It is also too technical to be an end user feature, and should only (maybe) exist as a programmatic interface for AT developers. If it is determined that it can be implemented without breaking things, then AAA The rest of 1.8 levels look ok<br /></td>
<td align="left"><span class="done">[done]</span> <a href="http://www.w3.org/2014/10/28-ua-minutes.html#item20">UAWG</a> changed the wording to remove "absolute layout" and added an example in the Reference. <br /></td>
<td align="left">Partial accept<br /></td>
<td align="left">substantive<br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left">AA</td>
<td align="left">1.8.15 Linearize Content: The user can have recognized content rendered as a single column, overriding author-specified formatting of columns, tables, and positioning. (Level AA)</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="18" align="left"><br /></td>
<td align="left">Note: 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.</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left">AAA</td>
<td align="left">1.8.16 Provide Web Page Bookmarks: 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 align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Guideline 1.9 - Provide alternative views </td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
</tr>
<tr>
<td height="17" align="left"><br /></td>
<td align="left">Summary: The user can view the source of content (1.9.2, Level AAA), and an outline view of content. (1.9.1, Level AA).</td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>
<td align="left"><br /></td>