-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathcapabilities.html
747 lines (608 loc) · 28 KB
/
capabilities.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
<!DOCTYPE html>
<html lang="EN-US">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<title>Overlay Capabilities Inventory, Accessibility at the Edge Community
Group</title>
<style>
</style>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
<script src="respec-config.js" class="remove"></script>
</head>
<body>
<a href=https://www.w3.org/><img alt=W3C height=48 src=https://www.w3.org/Icons/w3c_home width=72></a>
<h1><b>Overlay Capabilities Inventory</b></h1>
<p>Copyright © 2022 & 2023 by Contributors to the REPORT Overlay Capabilities Inventory (Version 0.1), published by the <a href="https://www.w3.org/community/a11yedge/">Accessibility at the Edge Community Group</a> under the <a href="https://www.w3.org/community/about/agreements/cla/
">W3C Community Contributor License Agreement (CLA)</a>. A human-readable <a href="https://www.w3.org/community/about/agreements/cla-deed/">summary</a> is available.
</p>
<p><b>This report was published by the <a href="https://www.w3.org/community/a11yedge/">Accessibility at the Edge Community Group</a></b> in the W3C.. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the <a href="https://www.w3.org/
community/about/agreements/cla/">W3C Community Contributor License Agreement (CLA)</a> there is a limited opt-out and other conditions apply. Learn more about <a href="https://www.w3.org/community/">W3C Community and
Business Groups</a>.</p>
<p>Last modified Saturday 11 March 2023</p>
<section id="abstract">
<h2>Abstract</h2>
</section>
<section id="sotd"></section>
<section id="introduction">
<h2>Introduction</h2>
<p>This document describes some capabilities that can be provided by overlays "at the edge", and attempts to answer several questions about them. The questions are:</p>
<ul>
<li>Source: What is the role of the author (or content source code developer) in providing this capability and ensuring that it is accessible.</li>
<li>Trade-offs When this capability is enabled on the edge, does it potentially duplicate functionality elsewhere in the stack? In particular, we consider all the possibilities near the edge namely the CDN, operating system, user-agent, browser extension, assistive technology, and/or javascript overlay. If so, can (and should) this redundancy be avoided?</li>
<li>Benefit: What is the potential benefit of performing this capability at the edge?</li>
<li>Related topics</li>
</ul>
<p><strong>EDITOR'S NOTE</strong><br /> The <q>Related Items</q> list item is a placeholder to remind us that this document is in active development. Suggestions welcome!</p>
<section>
<h2>Capabilities Inventory</h2>
<section>
<h3>User-triggered interactions/opt-ins</h3>
<p>User opt-ins via interactive personalization menus: The end-user can access a list of available enhancements and enable those they require. </p>
<dl>
<dt>Source</dt>
<dd>Users tend to require the same types of accomodations across all sites and all content sources. Therefore, facilitating this capability in the source is likely the least useful place to locate it, because that would require the user to select the same enhancements time and again across the succession of sites visited and likely with different menu organization site to site. </dd>
<dt>Trade-offs</dt>
<dd>Many of the capabilities made available by user-triggered opt-ins are often also found in multiple places at the edge. For example, contrast adjustment is generally found in operating system display settings, in browser and app user-agents (e.g. dark mode/light mode), and in browser extensions, and in javascripted (CDN hosted) overlays. Such redundancy can easily lead to confusion. This confusion may be further exacerbated because certain settings the user finds helpful may be available only in one of these locations, and not in all of them. Furthermore, users are frequently not particularly knowledgeable about their operating system settings menus, especially as these tend to move with each OS revision (to take one example). This can make it difficult to locate these features, especially when we recognize that once satisfactorily configured they are generally not reset (meaning that the user doesn't need to revisit that menu location and soon forgets where it is). On the other hand, locating the accommodation consistently proximate to the user offers the highest likelihood of maximal benefit provided the accommodation is easily identified and invoked without conflicts. This also provides the best opportunity for easing the burden of invoking the same accommodation across a user's multiple devices.</dd>
<dt>Benefit</dt>
<dd>Users can select and optimally tune the types of accomodations that they require. Any device on the edge may also have knowledge of other devices on the edge, that may need the same adjustments, and the edge could propagate these settings to those other devices. MacOS Ventura (MacOS 13.2) is already doing this for wifi passwords when an IOS device configured for the same network is proximate.</dd>
</dl>
</section>
<section>
<h3>Automated Background U-X Processing, no user action invoked</h3>
<p>Users will not care how a functional and accessible experience is assembled as long as their needs are met. However, they are, and must always be understood as the ultimate arbiters of whether their needs are actually being met.
Consequently,
U-X processing should be easily discoverable and defeatable. Users need to be empowered to act should they believe an unmediated experience would be superior. Preserving user agency is simply smart business strategy no matter how excellent the the technology may actually be.
</p>
<dl>
<dt>Source</dt>
<dd>Content providers have long sought to tailor U-X behavior based on what capabilities could be discovered about the user's operating environment. What browser is in use? Is a screen reader in use? Indeed, <a href="https://www.w3.org/TR/turingtest/#recap3">Google's automated Recaptcha 3 is deeply dependent on just such data gathering</a>.
</dd>
<dt>Trade-offs</dt> <dd><q>Nothing about us without us</q> is a deeply held
principle in disability advocacy. While a well-crafted remediation
technology may disappear from users' consciousness, it is both
risky and presumptuous to assume there will be no users who who will not
experience some kind of accessibility challenge even among the best crafted remediation technologies. For this reason alone it is
important to preserve user agency by offering a defeat option. Nothing is
gained when users are forced to contend with a remediation technology they
suspect may be contributing to their accessibility challenges, even if the
ultimate reality demonstrates that their suspicion is actually incorrect.
Furthermore, persons with disabilities tend to be concerned about content
providers discovering and monetizing user data. Their lived reality has made
them highly desirous to preserve their privacy because of perceived and actual
experience of discrimination over many years.
<p><strong>EDITOR'S NOTE</strong><br /> This needs more work.</p>
However, the approach provides clear benefits especially in real-time applications such as <a href="https://www.w3.org/TR/raur/">Real Time Communications (RTC)</a>.
Immediacy matters. ASR captions may not provide the desired quality, but the alternative may too often be no captions whatsoever.
Similarly missing image descriptions generated by A-I may prove more helpful to the user coping with a substandard page than no alternative text at all.
Not only does the continued presence of unremediated content provide user substandard access, it also does not provide A-I engines corrective feedback that could train them to do better in future.</dd>
Pages whose content remains unremediated however, can tend to encourage users to seek alternative source providers.
There's also an unrealized opportunity for crowd-sourced correctives to help train smarter A-I generated output, though burden-shifting does encumber this potential use.</dd>
</dd>
<dt>Benefit</dt>
<dd>Users do indeed expect their technologies will operate automatically and seamlessly to provide an accessible and functional experience. This is an accepted technological expectation. Content providers do not err in attempting to meet this expectation. The error arises from leaving the user out of the decision loop. Also, technologically mediated privacy preservation is only feasible in edge technologies, though it can be subverted even there.</dd>
</dl>
</section>
<section>
<h3>Portable cross-site profile expressing accessibility-oriented preferences</h3>
<p>Users now frequently use several devices. Furthermore, users tend to have the same or very similar accessibility requirements regardless of the device they may be using in the moment.
It is therefore an emerging goal in web accomodations to support the user in configuring once and having their configured preference propagate across all their devices.
This propagation should function across all vendors and operating environments.</p>
<dl>
<dt>Source</dt>
<dd>While technically feasible in source, this is not being done by content source today, and we are not aware of any proposals to add such functionality in content source—likely for a multiplicity of reasons.
People, regardless of ability or disability, may often want to withhold this information from a source provider, and would certainly not want it to propagate to
source providers outside of their knowledge or control.</dd>
<dt>Trade-offs</dt>
<dd>
A privacy-preserving, cross-platform U-I configuring capability is now a <a href="https://www.w3.org/2017/vc/WG/Meetings/Minutes/2022-09-15-vcwg#section8">long-term goal in the W3C Accessible Platform Architectures (APA) Working Group.</a>
Such a capability has long been desired and is arguably now more achievable than ever before.
It would clearly be valuable to users.
For example, blind users and people on slow internet connections will benefit from setting their browsers to not download images.
It will nevertheless require nuanced implementation, e.g. screen size and consequent decisions over preferred fonts, spacing, and contrasts will likely vary by screen size and environmental conditions.
Another example of a nuanced consideration is the likely desire of a screen reader user to operate sometimes with TTS, but other times with braille (or both braille and TTS).
</dd>
<dt>Benefit</dt>
<dd>Configure once and deploy everywhere, with the setting propagating to other contexts.</dd>
</dl>
</section>
<section>
<h3>Automated Detection of WCAG Violations</h3>
<p>Algorithmic detection of violations of WCAG 2.x success criteria is considered here as a vector for providing the user a more conformant experience.
Large, complex and highly dynamic source sites are literally unable to reproduce every user experience permutation in their test beds. Automated detection and
reporting can bridge this gap.
There is, of course, the other application, where violation detection serves as a step in a source remediation process. We address the former here..</p>
<dl>
<dt>Source</dt>
<dd>
If source got this right (as WCAG 2.x seems to expect), we wouldn't have a need for this capability.
</dd>
<dt>Trade-offs</dt>
<dd> In-browser scanners and online scanners are used to detect WCAG violations.
This is the business model for many companies.
False positives, false negatives, certainty and confidence scores are well-known factors affecting the success and usefulness of this approach.
It is unfortunate when such violations remain unremediated in source content, but sometimes this can't be helped.
An indication of violations at the edge, however rough, is better than none.
<dt>Benefit</dt>
<dd>
Automated detection is useful in-and-of-itself.
Something is most often better than nothing, especially in the moment.
It looms ever larger as it stacks, and automated detection is often the first step in a chain of capabilities.
</dl>
</section>
<section>
<h3>Notifications</h3>
<p>Messages shown to the end-user to
alert them to an event, some specific datapoint, or to some state. </p>
<dl>
<dt>Source</dt>
<dd>It seems unlikely source could fully take on this responsibility.
On the other hand it seems equally unlikely that edge technology alone can fully meet this need effectively without API-based data interchange with source content.
There is particularly cogent needs in <q>augmented reality</q> which are potentially very exciting.
</dd>
<dt>Trade-offs</dt>
<dd>What a user may want or need to know in any given situation or moment is a complex calculation at best.
It's far too easy to overdo notifications, though failing to notify judiciously and appropriately would constitute a major technological opportunity missed.
We need better models and privacy-preserving context awareness to realize all the benefits conceivable in this application of automated opportunities.</dd>
<dt>Benefit</dt>
<dd>Controlling the firehose of notifications is best filtered and managed at the edge.
The right information at just the right time can serve as a tremendous quality of life enhancement.
</dd>
</dl>
</section>
<section>
<h3>Human in the loop on automated remediation suggestions</h3>
<p>Overlay owner is asked to accept
programmatic suggestions. This enables democratization of accessibility tasks
and acceleration.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type.</dd>
</dl>
</section>
<section>
<h3>Accessibility provider visibly displayed </h3>
<p>Display to website users the name
of the primary accessibility provider, who stands behind the accessibility of
the site, offering transparency. This may be part of the accessibility
statement.</p>
<p>[2] The provider can be listed in
the source text.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type. Sometimes (rarely) the accessibility provider
is mentioned in the accessibility statement or accessibility policy. </dd>
</dl>
</section>
<section>
<h3>Accessibility statement access</h3>
<p>A link to the site's accessibility
statement</p>
<p>The link can be hosted on the
source page.</p>
<dl>
<dt>Trade-offs</dt>
<dd> The link in the footer of the
site</dd>
</dl>
</section>
<section>
<h3>Accessibility issue reporting</h3>
<p>A form, or email link, enabling
end-users to report barriers to accessibility to the website owner</p>
<dl>
<dt>Trade-offs</dt>
<dd> Contact us in the
accessibility statement</dd>
<dt>Related Topics:</dt>
<dd> Responsibility for responding.
Requires that the company receiving the report has expertise to respond. </dd>
</dl>
</section>
<section>
<h3>Profile enabling a bundle of user-triggered interactions/opt-ins (on a
site)</h3>
<p>Optional profiles that group
interactive features together into bundles, making it easier to turn on groups
of features, e.g. high contrast and larger text size.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type. </dd>
</dl>
</section>
<section>
<h3>Accessibility editing, by site owner</h3>
<p>An interface in the overlay,
available to authorized users, enabling manual editing of code that affects
accessibility, e.g. alt tags for images, or ARIA labels.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type. Provides an alternative to standard methods of
coding the site, either via source code, web platform templates/CSS
adjustments, etc.</dd>
<dt>Related Topics:</dt>
<dd> This editing needs to be done
by people with expertise. Can be a source of information for a subject matter
expert.</dd>
</dl>
</section>
<section>
<h3>Accessibility editing, by 3rd party</h3>
<p>A third party, via the overlay,
codes the accessibility of the site.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type. Without an overlay, this could be an
outsourced remediation team that has login authorization to the source code
and/or admin of the CMS/Platform.</dd>
</dl>
</section>
<section>
<h3>Change Text Size</h3>
<p>Increase or decrease font size, by
clicking an interactive widget.</p>
<p>[2] Source code specifies text
size as per the original target audience and design, but only for content
coming from the source.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Text sizes are configurable in
the operating system. Not clear if this propagates across all dynamically
loaded content.</dd>
<dt>Benefit of being on the Edge:</dt>
<dd> Learning how to make such
changes in browser and/or operating system configurations is challenging for
many, and particularly challenging for the communities that most need it.
Offering overlay access raises awareness that such capabilities are present and
does not prevent users from learning how to configure it in other places.
Overlays are site-specific, making such accomodations on the sites where they
are requested. An overlay could propagate such preferences across sites,
browsers, operating systems and/or devices, to manage the complete experience
including injected and/or dynamic content.</dd>
</dl>
</section>
<section>
<h3>Change Text Spacing</h3>
<p>Modify text and line spacing for
improved readability for dyslexic and visually impaired users. Offers three
degrees of adjustments for a personalized and more accessible reading
experience. ,</p>
<dl>
<dt>Trade-offs</dt>
<dd> Defaults are configurable in
the operating system.</dd>
</dl>
</section>
<section>
<h3>Change Cursor Size</h3>
<p>Increases the standard cursor size
by 400% to ensure the pointer always remains in sight. Allows for faster and
more accessible navigation through hyperlinks, tabs. and form elements.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Defaults are configurable in
the operating system.</dd>
</dl>
</section>
<section>
<h3>Change Link Highlights Visibility</h3>
<p>Selecting the text or image that serves
as a hyperlink and causing it to be displayed in a different, more visible way,
to help identify the links on a page more easily. </p>
<dl>
<dt>Trade-offs</dt>
<dd> Defaults are configurable in
the browser.</dd>
</dl>
</section>
<section>
<h3>Pause Animations</h3>
<p>The ability to stop animations or
other moving elements on a web page from playing. </p>
<dl>
<dt>Trade-offs</dt>
<dd> Some players offer a pause.
Context menu or developer tools. </dd>
</dl>
</section>
<section>
<h3>Apply Light Contrast, Dark Contrast, Invert Colors, Color Desaturation</h3>
<p>Color modifications that are useful
to people with visual impairments. They modify the difference between the
lightest and darkest parts of a web page, reverse colors, or reduce their
intensity.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Defaults are configurable in
the operating system.</dd>
</dl>
</section>
<section>
<h3>Tooltips</h3>
<p>small pop-up window that appears
on hover to display additional information about an element on the page,
providing context or clarification.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type.</dd>
</dl>
</section>
<section>
<h3>Reading Guide</h3>
<p>A horizontal line that appears
below text to help the reader keep their place as they read, follow along with
the text and stay focused. </p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type. There may be browser extensions that provide
this functionality.</dd>
</dl>
</section>
<section>
<h3>Accessible Fonts</h3>
<p>Fonts selected for their
legibility, that are generally found to be easier to read, especially for
people with low vision or reading difficulties.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Defaults are configurable in
the operating system.</dd>
</dl>
</section>
<section>
<h3>Dyslexia Friendly Font </h3>
<p>Fonts considered to be more
dyslexia-friendly as they have more distinctive symbols that avoid confusion,
increased baselines and thinner tops, and a larger x-height. </p>
<dl>
<dt>Trade-offs</dt>
<dd> Fonts can be configured in the
operating system.</dd>
</dl>
</section>
<section>
<h3>Page Structure Show Headings, Links, Landmarks</h3>
<p>Alternative navigation methods
that are commonly used by screen readers, made available to the sighted user.
These include the ability to browse a page by its headings, which can be
helpful for understanding the overall structure of the page; links; buttons. </p>
<dl>
<dt>Trade-offs</dt>
<dd> Available in screen readers</dd>
</dl>
</section>
<section>
<h3>Reset All</h3>
<p>One button click to reset any user
triggered enhancement and restore the page to its default state.</p>
<dl>
<dt>Trade-offs</dt>
<dd> No need.</dd>
</dl>
</section>
<section>
<h3>Screen Reader</h3>
<p>On page screen reader</p>
<dl>
<dt>Trade-offs</dt>
<dd> Screen reader installed at the
operating system level and used as a standalone application. Also (less common)
screen readers in an application such as a browser.</dd>
</dl>
</section>
<section>
<h3>Keyboard Navigation</h3>
<p>Enhance visual indicators that
support keyboard navigation such as underlines or color changes; optionally
provide other assistance such as mapping interactive elements to keyboard
shortcuts. </p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type. Some aspects can be enhanced in the operating
system or browser configuration, such as focus indication.</dd>
</dl>
</section>
<section>
<h3>Image Alts</h3>
<p>Short piece of text associated with
an image on a web page. It is intended to provide a description of the image
for users who cannot see it, such as those using screen readers or text-only
browsers.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Some computer vision image
identification is included in some browser extensions.</dd>
</dl>
</section>
<section>
<h3>Form Labels</h3>
<p>A label associated with each form
field accurately describing its purpose. The label should be consistent with
the logical structure of the form overall.</p>
<p>[2] Code with proper form labels.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type.</dd>
<dt>Benefit of being on the Edge:</dt>
<dd> Apparently, after twenty years
of consistent effort at changing how we train designers and developers of
forms, only a subset are doing it right today, but we still need the labels.
Having an overlay provide them escalates the need, hopefully attracts dev
attention and gets the resource allocated. Certainly, an overlay does not
prevent source from being fixed, when it can be fixed (e.g. there are some
legacy codebases where fixing in the edge is preferred).</dd>
</dl>
</section>
<section>
<h3>Dictionary</h3>
<p>Provide definitions of words or
phrases that may be unfamiliar to some users; provide pronunciation guidance;
provide synonyms which can help users with cognitive disabilities better
comprehend the content.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Browsers and operating systems
offer related features, generally on "right-click". </dd>
</dl>
</section>
<section>
<h3>Form Validation </h3>
<p>Ensure that screen reader users
and people with disabilities receive clear feedback on the status of the form
along with concise error messages. This includes the colors used, the proximity
to the form field, and the time-sensitive nature of the screen reader
announcement. </p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type.</dd>
</dl>
</section>
<section>
<h3>Interactive Elements </h3>
<p>Ensure there are concise
instructions and labels that are clear to sighted, low vision and non sighted
users, and that the elements can be controlled with keyboard navigation.
Provide such feedback on the status of the element and any changes that occur. </p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation unique
to overlays of this type.</dd>
</dl>
</section>
<section>
<h3>Autoplay Videos </h3>
<p>Provide ability to pause, mute
and/or stop the video; make these controls keyboard navigation accessible.</p>
<p>[2] Videos should be made
available with these capabilities, as they are built into HTML 5.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type. Some sites offer the option. </dd>
<dt>Benefit of being on the Edge:</dt>
<dd> Apparently, after years of
consistent effort at changing how we train designers and developers of websites
that host video, only a subset are doing it right today, and we still need
these controls. Having an overlay deliver these capabilities is not a problem
for end users, it is more service for users. The overlay may escalate the need,
hopefully attracting dev attention and encourage better source development in
the future. Certainly, an overlay does not prevent source from being fixed,
when it can be fixed (e.g. there are some legacy codebases where fixing in the
edge is preferred).</dd>
</dl>
</section>
<section>
<h3>External Link Targets</h3>
<p>Assure the link is announced
correctly as a link, and inform users if it opens in a new tab or window. In
addition, assess broken links: verify that the link resolves, and mark broken
links as broken. </p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type.</dd>
</dl>
</section>
<section>
<h3>Ambiguous Links</h3>
<p>Provide descriptive and meaningful
link text that accurately reflects the purpose or destination of the link,
particularly needed for link text such as "click here" or
"more." </p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type.</dd>
</dl>
</section>
<section>
<h3>Broken Links</h3>
<p>Assess if the link resolves, and
mark broken links as broken.</p>
<dl>
<dt>Trade-offs</dt>
<dd> Not redundant: an innovation
unique to overlays of this type. There are some browser extensions that perform
some of this functionality.</dd>
</dl>
</section>
<section>
<h3>Video Captioning</h3>
<p>Displaying in text along with
video, synchronized with the video, what is heard. </p>
</section>
<section>
<h3>Missing Titles </h3>
<p>Meaningful titles, for pages and/or
iFrames within pages, allow screen reader users to browse by means of titles. </p>
</section>
<section>
<h3>Element Focus </h3>
<p>Visible indication when an
interactive element on the page is selected. </p>
</section>
<section>
<h3>Site Language </h3>
<p>Specify the primary language of a
web page.</p>
</section>
<section>
<h3>PDF Remediation</h3>
<p>Assuring that a PDF is tagged and
marked up sufficiently so that it can be accessed and understood by people with
disabilities, including those who use assistive technology such as a screen
reader.</p>
</section>
<section>
<h3>Content Moderation</h3>
<p>Assuring that the content on a
site meets content policy. The default policy includes everyday phrases with
racist origins, and gendered or exclusive expressions and terms that are deemed
to exclude audiences.</p>
</section>
<section>
<h3>Text Align</h3>
<p>Text alignment enhances
readability. The inconsistent spacing between words created by justified text
can be problematic for people with cognitive concerns such as Dyslexia. Users
can determine the alignment best suited to their vision.</p>
</section>
<section>
<h3>Line Height</h3>
<p>Increase or decrease line height
to distinguish between lines of text.</p>
</section>
<section>
<h3>Accessible Pricing</h3>
<p>Strike-through pricing is a visual
representation of the original price of a product in a strike-through or crossed
out font, and then an associated new price next to it. Screen readers read the
struck-out price like any other number, so ARIA markup needs to be added to
indicate that the struck out price is the old, no longer valid price.</p>
</section>
<section>
<h3>Live Site Translations</h3>
<p>Offer a user-triggered method to
change the language of a web page in real time, by translating the current page
into a language selected by the user.</p>
</section>
<section>
<h3>Smart Contrast</h3>
<p>The colors of text and background
that does not meet minimum contrast requirements are adjusted in such a way
that the minimum change is made. The advantage of such minimal changes is that
the colors will resemble, or remain close to, the original brand design
intention.</p>
</section>
</section>
</body>
</html>