-
Notifications
You must be signed in to change notification settings - Fork 2
/
index.html
872 lines (867 loc) · 44.6 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
<!DOCTYPE html>
<html lang="en-US" xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Framework for Accessible Specification of Technologies (FAST)</title>
<script class="remove" src="respec-config.js"></script>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
</head>
<body>
<section id="abstract">
<p>Framework for Accessible Specification of Technologies (FAST) advises creators of technical specifications how to ensure that their technology meets the needs of users with disabilities. It primarily addresses web content technologies, and also relates to any technology that affects web content sent to users, including client-side APIs, transmission protocols, and interchange formats. Specifications that implement these guidelines make it possible for content authors and user agents to render the content in an accessible manner to people with a wide range of abilities.</p>
<p>This document is accompanied by a <a href="checklist.html">checklist</a> which is more complete and usable for groups evaluating technologies at this time.</p>
</section>
<section id="sotd">
</section>
<section>
<h2>Introduction</h2>
<section>
<h3>Checklist</h3>
<p>This document is accompanied by a <a href="checklist.html">checklist</a> which is more complete and usable for groups evaluating technologies at this time.</p>
</section>
<section>
<h3>Goals</h3>
<p>Numerous guidelines exist for creating and supporting content that is accessible to people with disabilities, on and off the Web. When these guidelines are supported in the entire web ecosystem, content creators can author accessible content, and expect the accessibility features to be made available by user agents, including assistive technologies when needed. Authoring tools support creation of accessible content, and accessibility features survive transmission to different systems or conversion of content to different formats.</p>
<p>Nearly all of these accessibility features depend on support in some form from the technology in which content is encoded, transmitted, and sometimes transformed. But there is not yet a set of well-documented guidance for such technologies. Instead, requirements are inferred from authoring and user agent guidelines. This makes it complicated for technology creators to ensure they have met the full set of needs. Review from accessibility specialists is limited by bandwidth and expertise, so does not fully address that problem. As a result, varying technologies provide various levels of support with varying levels of compatibility with other technologies. These issues at the core layers of Web technology impact the progress that can be made from support of higher-level guidelines.</p>
<p>Framework for Accessible Specification of Technologies aims to fill this gap. It is intended to be a single, well-considered set of guidelines addressing specifically the features technologies need to provide to support accessibility. These guidelines relate to the requirements of other guidelines but should not be confused with them. The goal of FAST is to provide a single source of guidelines for Web technology accessibility. They relate to other guidelines and documentation to provide additional information and rationale for the requirement, but are intended to be a self-sufficient set of guidelines that technology creators can follow.</p>
</section>
<section>
<h3>Audience</h3>
<p>The primary audience of FAST is creators of Web technologies. Most of the guidelines relate to content and presentation technologies like HTML, CSS, SVG, PDF, audio/video formats, etc. Some guidelines also address data formats, interchange formats, transmission protocols, etc., usually aimed at ensuring these technologies preserve the accessibility features of content impacted by these technologies. Because of this broad set of relevant technologies, all Web technology creators are considered part of the audience for FAST.</p>
<p>Secondary audience include creators of higher level accessibility guidelines and other advocates for web accessibility features. Because FAST has a strong grounding in user needs, researchers and advocates who identify the accessibility requirements of web users with disabilities are also an important audience.</p>
</section>
<section>
<h4>Scope</h4>
<p>Framework for Accessible Specification of Technologies is a product of the World Wide Web Consortium and as such targets only the accessibility requirements of web technologies. Many of the user needs are the same for web use and non-web use, so FAST will necessarily overlap and hopefully be compatible with similar guidelines addressing non-web space. Nonetheless, FAST is not designed to be used for non-web technologies and there could be key differences. Furthermore, there are user needs that exist outside the web that do not impact the web, and those needs are completely unaddressed by FAST.</p>
<p>In spite of these caveats about the scope of FAST, this scope will evolve as the Web does. More and more technologies are becoming part of the Web, and bringing user needs to the Web along with them. For instance, strictly hardware accessibility issues may be non-web requirements, but the Web of Things brings many of these issues closer to the Web than in the past. FAST will need to reflect this evolution, and future versions may be required to address user needs that are new to the Web.</p>
</section>
<section>
<h3>Approach</h3>
<p>The goal of FAST is to help ensure that web technologies meet the needs of users with disabilities. To do this, the work involves three stages:</p>
<ul>
<li>Inventory functional and user needs;</li>
<li>Identify ways to meet needs;</li>
<li>Develop technology guidelines.</li>
</ul>
<section>
<h4>Inventory functional and user needs</h4>
<p>The first step in the development of these guidelines is to inventory known functional and user needs. Many user needs affecting web content accessibility are well known and documented in multiple places. These needs are collected and related to each other in order to arrive at a single set of known needs. Sources examined in the development of these guidelines include:</p>
<ul>
<li><a href="http://www.jtc1access.org/documents/swga_339_DTR_29138-1_User_Needs_Summary.zip">JTC 1 User Needs</a>; </li>
<li><a href="https://www.iso.org/standard/70913.html">ISO/IEC 30071-1 Information technology — Development of user interface accessibility — Part 1: A code of practice for creating accessible ICT products and services</a></li>
<li><a href="https://www.w3.org/TR/WCAG20/">WCAG 2.0</a>;</li>
<li><a href="https://www.w3.org/TR/UAAG20/">UAAG 2.0</a>;</li>
<li><a href="https://www.w3.org/TR/ATAG20/">ATAG 2.0</a>;</li>
<li><a href="https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Main_Page">Mobile gap analysis</a>;</li>
<li><a href="https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page">Cognitive gap analyses</a>;</li>
<li><a href="https://www.w3.org/TR/media-accessibility-reqs/">Media Accessibility User Requirements</a>;</li>
<li> Sources from other advocacy organizations.</li>
</ul>
<p class="note">Note the goal of this exercise is not to supplant other good work in this field. The aim is to assemble disparate sources of knowledge about user needs in one place, to facilitate analysis. This work is likely to spin off from the core work of developing FAST. If another organization creates a sufficiently rich collection of documented user needs it will be possible to use that resource rather than reinvent the work in W3C.</p>
<p>In the course of exploring how to apply user needs to accessibility guidance, we have identified two intersecting categories of needs: [[[#functional-needs]]] and [[[#user-needs]]].</p>
</section>
<section>
<h5>Document functional needs</h5>
<p>A <dfn>functional need</dfn> is a statement that describes a specific gap in one’s [=ability=], or a specific mismatch between ability and the designed environment or context. An <dfn data-lt="intersectional need">intersectional functional need</dfn> results from an individual having more than one functional need simultaneously in a given context.</p>
<p>A <dfn data-lt="ability">functional ability</dfn> is a notional measure of a person’s abilities that may need technological support or augmentation to be able to complete a particular task.</p>
<p class="note">The intent is to express the need in a contextual model, as opposed to a lack of ability in a medical model. This is similar to the ICF (International Classification of Functioning – a biopsychosocial model), “outcomes of interactions between health conditions (diseases, disorders and injuries) and contextual factors”, focusing on the interactions. </p>
</section>
<section>
<h5>Document user needs</h5>
<p>A <dfn>user need</dfn> is a high level accessibility characteristic of content and/or a user interface that is necessary for users to complete an objective.</p>
<p>In this model, user needs are not accessibility specific. User needs are generic requirements of content for its features to be usable by humans. </p>
</section>
</section>
<section>
<h5>Develop matrix of functional and user needs</h5>
<p>In order for people to access content, for every [=user need=] inherent in the content, there must be a way to meet an individual’s [=functional needs=]. User needs and functional needs intersect into a matrix of potential affordances required for content. These requirements comprise the set of <dfn>expected outcomes</dfn> that should be addressed in this and other web accessibility guidance.</p>
<p class="ednote">Todo: put in snapshot of matrix or something.</p>
<section>
<h4>Identify ways to meet needs</h4>
<p>The second stage in development of the guidelines is to identify ways these needs can be met. There are three high-level ways user needs can be met:</p>
<ul>
<li>technology features;</li>
<li>author implementation;</li>
<li>user agent support.</li>
</ul>
<p>These are not mutually exclusive categories. A given user need could be met by more than one of these categories, but the ability of a given category to meet a user need implies the need for guidelines targeting that category. In policy setting and evaluation there may be a preference hierarchy for how best to meet needs, e.g., user agent support of standard features is preferred, but author technical override is needed if user agent support is lacking. </p>
<p>Some needs can be met with present technology only via one of these routes. Other needs can be met by more than one route, and for content to be accessible it is only required that one of the available routes be implemented. Many needs, however, require more than one route to be implemented together for the need to be met. The most common example is that a technology provides a feature, the author uses that feature in the content, and the user agent makes the result available to the user.</p>
<p>All of these ways of meeting user needs are identfied, along with their relationships to each other. Once these approaches are identified, the result is separate lists of requirements for content technologies, authors, and user agents. The relationship among the routes may play a role in prioritization of guidelines, since needs that can only be met by one route may be more important to meet by that route, than needs that could be met by other means as well.</p>
</section>
<section>
<h4>Develop technology guidelines</h4>
<p>From the above analyses, it should also be easy to see where content technology features are required to make it possible to meet user needs. For example: </p>
<ul>
<li> If the author must implement something, the technology must provide a feature for the author to implement. </li>
<li> If the user need is met by design, the technology must provide suitably rich design capabilities. </li>
<li> If the user need is met by user agents, the technology must provide a sufficiently rich definition of the object for user agents to implement. </li>
</ul>
<p>Not all technologies will address all ways of meeting user needs. For instance, CSS is primarily design-oriented, and HTML is somewhat semantics-oriented. The technology requirements may need conformance profiles or some other way of guiding technology developers seeking to follow them. It may not be easy to state in a general prescriptive way whether a given technology should, for instance, provide a richer design capability to meet a user need or should instead rely on better semantics for assistive technology-oriented content alternatives. A good structure of the technology requirements should help make it clear that <i>some</i> method of meeting a given user need is important. Horizontal review may continue to be important in guiding technology developers through the possibilities. </p>
<p>The set of approaches to meeting user needs that affects technology features becomes the base information for the Framework for Accessible Specification of Technologies. (The other two routes, while important to the analysis, are not directly relevant to FAST but may inform other work.) These approaches are prioritized, organized, and translated into guidelines-type language to become the Framework for Accessible Specification of Technologies.</p>
<p>With the above analyses done, it should be easy to see how current guidelines address which user needs. In turn it should be easy to see where current guidelines do not meet user needs, that in theory should be able to be met by activities within the remit of that set of guidelines. This should be important input into WAI 3.0 / WAI 2020 planning.</p>
</section>
</section>
<section>
<h3>Explanation of User Needs</h3>
<!--
<figure>
<img src="img/usability-accessibility.png" xmlns="https://www.w3.org/1999/xhtml"/>
<figcaption>Accessibility needs become mainstream needs over time</figcaption>
</figure>
-->
<p>Identify user needs that we plan to provide guidance on meeting. These should describe the needs of humans as they currently exist (i.e., without significant evolution or cyborgization from early 21st century norms), and therefore is as era-independent as possible with current knowledge. The focus is on the needs of people with disabilities, but because that is sometimes a relative / contextual condition, a significant proportion of mainstream needs will also be identified. </p>
<p>At least two levels of needs may be identified. The first is truly generic needs, requirements users have to access and use content such as perceive and understand it, and should be stable over time. The second layer is needs specific to technologies of the day, such as ability to understand and operate controls. This layer may be understood as an implementation of the generic needs, so may not be classed as user needs in the end. Regardless of its classification, it will be an important component of understanding the space. This level of needs evolves as technology and design patterns do, so needs to be maintainable separately from the generic needs. </p>
<section>
<h4>Evolution of user needs</h4>
<p>Where user needs are suspected but known, related work may expand the inventory through research when feasible. Therefore the set of documented user needs will evolve over time. A given set of guidelines including FAST, however, can only address needs that were known at the time of development of the guidelines.</p>
</section>
<section>
<h4>Assumptions </h4>
<ul>
<li> User is accessing Web content on hardware / OS / AT combination that supports their needs. This may not always be true for shared device / public kiosk situations, but that issue is out of scope. </li>
</ul>
</section>
<section>
<h4>Applicability of Needs </h4>
<ul>
<li> Content </li>
<li> Controls (buttons, fields, etc.) </li>
<li> Input indicators (mouse, keyboard cursors) </li>
<li> Signals (non-actionable state indicators) </li>
<li> Alerts (dialogs, alarms, etc.) </li>
</ul>
</section>
</section>
</section>
<section>
<h2>Functional Needs</h2>
<section>
<h3>Safety</h3>
<section>
<h4>Use without physical harm or risk (to self or others within a physical environment)</h4>
</section>
</section>
<section>
<h3>Sensory</h3>
<section>
<h4>Vision and Visual</h4>
<section>
<h5>Use without vision </h5>
<section>
<h6>Use as blind (born without vision)</h6>
</section>
<section>
<h6>Use with blindness (acquired blindness during lifetime)</h6>
</section>
</section>
<section>
<h5>Use with limited vision </h5>
<section>
<h6>Use with limited central vision</h6>
</section>
<section>
<h6>Use with limited peripheral vision</h6>
</section>
<section>
<h6>Use with limited interocular acuity or monocular input</h6>
</section>
</section>
<section>
<h5>Use without color perception</h5>
</section>
<section>
<h5>Use with limited color perception</h5>
</section>
<section>
<h5>Use with limited depth perception</h5>
</section>
<section>
<h5>Use with limited orientation or spatial tracking</h5>
</section>
<section>
<h5>Use with photosensitivity (too much or too little)</h5>
</section>
</section>
<section>
<h4>Hearing and Auditory</h4>
<section>
<h5>Use without hearing </h5>
<section>
<h6>Use as Deaf (born with congenital deafness and/or to a deaf family)</h6>
</section>
<section>
<h6>Use as deaf (acquired deafness during lifetime after a language was learned)</h6>
</section>
</section>
<section>
<h5>Use with limited hearing</h5>
</section>
<section>
<h5>Use with limited auditory processing (speech)</h5>
</section>
<section>
<h5>Use with sensorineural hearing loss (limited frequency range) related to age or Presbycusis (gradual loss over time)</h5>
</section>
</section>
<section>
<h4>Sensory Intersections</h4>
<section>
<h5>Use without vision and hearing </h5>
<section><h6>Use without vision from birth then without hearing as acquired</h6> </section>
<section><h6>Use without hearing from birth then without vision as acquired</h6> </section>
</section>
<section>
<h5>Use with vestibular issues</h5>
</section>
<section>
<h5>Use without spatial auditory awareness or perception (needs diegetic sound)</h5>
</section>
</section>
</section>
<section>
<h3>Physical</h3>
<section>
<h4>Mobility</h4>
<section>
<h5>Use without mobility</h5>
</section>
<section>
<h5>Use with limited mobility </h5>
<section>
<h6>Use with limited ambulation</h6>
</section>
<section>
<h6>Use with temporary or partial paralysis</h6>
</section>
</section>
<section>
<h5>Use with limited reach or range</h5>
</section>
</section>
<section>
<h4>Motor</h4>
<section>
<h5>Use without hands</h5>
</section>
<section>
<h5>Use without multiple touchpoint gesture</h5>
</section>
<section>
<h5>Use with limited strength</h5>
</section>
<section>
<h5>Use without fine point control</h5>
</section>
<section>
<h5>Use without physical tracking speed</h5>
</section>
<section>
<h5>Use with tremors</h5>
</section>
</section>
<section>
<h4>Physical and Sensory Intersections</h4>
<section>
<h5>Use with limited kinaesthetic perception (orientation, position, weight distribution, movement)</h5>
</section>
<section>
<h5>Use with limited tactile perception, sensory processing, or touch pressure sensitivity</h5>
</section>
<section>
<h5>Use with chronic pain impacting input or interaction modality, speed and/or frequency</h5>
</section>
<section>
<h5>Use without vision and a motor disability</h5>
</section>
<section>
<h5>Use without hearing and a motor disability</h5>
</section>
</section>
<section>
<h4>Speech</h4>
<section>
<h5>Use without vocalization</h5>
</section>
<section>
<h5>Use with limited vocalization or volume</h5>
</section>
</section>
</section>
<section>
<h3>Cognitive</h3>
<section>
<h4>Attention</h4>
<p class="ednote">Note that attention and working memory are also often called part of Executive
function
</p>
<section><h5>Use with limited ability to focus attention</h5> </section>
<section>
<h5>Use with limited ability to direct attention</h5>
<p>Focus on the users key task and page purpose</p>
</section>
<section><h5>Use with limited ability to shift attention</h5> </section>
<section>
<h5>Use with limited ability to sustain attention</h5>
</section>
<section>
<h5>Use with limited ability to restore context</h5>
<p>After focus is lost and return attention</p>
</section>
</section>
<section>
<h4>Language and Communication</h4>
<section><h5>Receptive communication</h5></section>
<section><h5>Expressive / productive communciation</h5></section>
<section><h5>Language</h5>
<p>(from different sources, such as auditory discriminatory, visual memory etc) </p>
<p>Speak, write, read, or understand speech , sign, symbols and/or other language. Includes: </p>
<ul>
<li>Language Development</li>
<li>Lexical Knowledge (VL)</li>
<li>Oral Production and Fluency (OP)</li>
<li>Grammatical Sensitivity (MY)</li>
<li>Morphology and sentences (syntax)</li>
<li>Foreign Language Aptitude (LA)</li>
<li>interocular transfer of visual memory (retrieval based on limited acuity in a single
eye)</li>
<li>phonological or phonemic awareness</li>
<li>Auditory discrimination </li>
</ul></section>
<section><h5>Literacy</h5></section>
<section><h5>Non language and sublinguistic communication</h5>
<p>Non-language communication (CM) can include: </p>
<ul>
<li>Implied communication, body language understanding metaphors and non literal
language</li>
<li> Listening Ability(LS)</li>
<li>Information about Culture (K2)</li>
<li>Range of stored general cultural knowledge (e.g., music, art)</li>
<li> </li>
<li>Understanding visual cues( symbols, spacing etc )</li>
<li>understanding appropriate behaviors </li>
</ul></section>
</section>
<section>
<h4>Learning</h4>
<section><h5>New skills</h5></section>
<section><h5>New information</h5></section>
<section><h5>New interface</h5></section>
<section><h5>New terms</h5></section>
<section><h5>New symbols </h5>
<p>(note that someone with early dementia may have </p>
<p>wonderful language, but not be able to learn any new terms etc)</p>
</section>
<section><h5>Understand new or complex information </h5></section>
</section>
<section>
<h4>Memory</h4>
<p class="ednote">Note that attention and working memory are also often called part of Executive
function
</p>
<section>
<h5>Use with limited short-term or working memory </h5>
</section>
<section>
<h5>Use with limited medium or long-term memory</h5>
</section>
<section>
<h5>Use with limited sensory memory </h5>
<section>
<h6>Visual</h6>
</section>
<section>
<h6>Visual-spatial</h6>
</section>
<section>
<h6>Auditory</h6>
</section>
</section>
<section><h5>Context-based memory</h5>
<section><h5><b>Episodic memory</b> (autobiographical – time, self)</h5></section>
<section><h5><b>Semantic</b> memory (factual)</h5></section>
<section><h5><b>Musical memory</b></h5></section>
<section><h5><b>Auditory memory:</b> Memory for sound patterns (UM)</h5></section>
<section><h5><b>Procedural memory:</b> Memory for performance of particular types of action such as
walking.</h5></section>
<section><h5><b>Prospective memory</b>: Much of what we have to remember in everyday life involves prospective memory —
remembering to do things in the future, such as keep appointments, return a book to the
library, or pay bills on time.
[http://www.ncbi.nlm.nih.gov/books/NBK3885/]</h5></section>
<h5><b>Emotional memories:</b> can be both declarative- and procedural-memory processes.</h5>
</section>
<section><h5>Awareness-based memory</h5>
<section><h6>Implicit memory</h6><p>(Can be called non-declarative memory) is built or used without conscious awareness.
In contrast with...</p></section>
<section><h6>Explicit memory</h6>: (Can be called declarative memory) the intentional use of memory such as remembering the time of an appointment or studying for an exam.</section>
</section>
<section><h5>Associative Memory</h5> (AM)</section><section><h5>Meaningful memory</h5></section><section><h5>Free-recall memory (M6)</h5></section>
</section>
<section>
<h4>Executive</h4>
<section>
<h5>Use with limited reasoning ability</h5>
</section>
<section>
<h5>Use with limited understanding ability</h5>
</section>
<section>
<h5>Use with limited decision-making ability</h5>
</section>
<section>
<h5>Use with limited self regulation</h5>
<p>tolerate interruptions, respond to and cope with changes to schedules, routines, people, surroundings, etc.</p>
</section>
<section><h5>function </h5></section>
<section><h5>Pacing and response time</h5></section>
<section><h5>Planning and changes/switching plans</h5></section>
<section>
<h5>Use with limited judgment</h5>
</section>
<section><h5>visual, language, or numerical thinking.</h5></section>
</section>
<section>
<h4>Mental Health</h4>
<section><h5>Emotional regulation (triggers and others) impulse control</h5></section>
<section><h5>Specific content needs such as relating to addictive issues or food,
triggers</h5></section>
<section><h5>Mood - depression, mania etc </h5></section>
<section><h5>Anxiety fears Stress and pressure </h5><ul>
<li> Social, paranoia , fear of how people will react to your
issues</li>
<li>fear of types of situations , lines/ crowded , fear of
travel </li>
</ul></section>
<section><h5>Disturbed thoughts Trouble with organized thoughts , concentration/ mind going blank,
indecisive, memory gaps</h5>
<ul><li>-Exaggerated or unhealthy responses, such as irritation, love, anger, guilt, self
hate </li>
<li>-Derealization, (detachment from reality) or depersonalization , </li></ul></section>
<section><h5>dissociative reactions, detachments</h5></section>
<section><h5>Persistent negative beliefs and false physical interpretation </h5></section>
<section><h5>Physical disability and symptoms (from somatic disorders and other physical symptoms,
nausea, fainting, short of breath) </h5></section>
<section><h5>Repetitive or obsessive behaviors </h5></section>
<section><h5>Identifying reality, such as Psychosis </h5></section>
<section><h5>Altered sensory and motor, psychomotor changes.</h5></section>
<section><h5>Fatigue / insomnia </h5></section>
</section>
<section>
<h5>Processing</h5>
<p>speed</p>
<p>fluency </p>
<p> Cognitive overload and fatigue </p>
</section>
<section>
<h5>Knowledge</h5>
<section><h5>knowledge of culture</h5></section>
<section><h5>base </h5></section>
<section><h5>Language knowledge, including:</h5></section>
<section><h5>lexical (UL)</h5></section>
<section><h5>jargon (subject matter)</h5></section>
<section><h5>Background and subject matter - including jargon and technology</h5></section>
<section><h5>Web and technology usages and risks</h5></section>
<section><h5>metaphors and idioms</h5></section>
<section><h5>icons and symbols</h5></section>
<section><h5>mathematical knowledge</h5></section>
<section><h5>mechanical Knowledge (MK)</h5></section>
<section><h5>knowledge of behaviors</h5></section>
<section><h5>Design metaphor – look</h5></section>
<section><h5>Design functions</h5></section>
<section><h5>Who to trust and credibility </h5></section>
</section>
<section><h5>Sensory processing</h5>Overloads</section>
<section>
<h5>Orientation</h5>
<section><h5>Where you are in physical space, </h5></section>
<section><h5>Where you are in a process</h5></section>
<section><h5>Where you are in a site</h5></section>
<section><h5>Where you are in a page</h5></section>
<section><h5>Where you are in time</h5></section>
</section>
<section>
<h5>Mathematical</h5>
<section><h5>Understanding of math abstractions and numeric concepts</h5></section>
<section><h5>Computational skill</h5></section>
</section>
<section>
<h5>Psychomotor and coordination</h5>
<section><h5>Coordination skill (motoric skills, visual-spatial organizational memory, and
social)</h5></section>
<section><h5>Compositional skill such as:</h5><ul>
<li>Simultaneous thinking and input </li>
<li>Communication that requires multiple cognitive functions such as talking and/or
signing while thinking </li>
<li> Divided attention </li>
</ul></section>
</section>
</section>
<section>
<h3>Independence</h3>
<section>
<h4>Independence</h4>
<section>
<h5>Use without autonomy or agency</h5>
</section>
<section>
<h5>Use without privacy</h5>
</section>
<p class="note">The purpose of identifying independence as a functional need is for individuals where independence cannot be achieved. Example: a person who has suffered a stroke, is conscious and aware but otherwise incapable of interacting with technology may need to log into a system or record a decision or authorize an agent to record a decision in their presence. In this case, they lack autonomy and privacy, but a method could be provided to verify the individual consent and the agent authority.</p>
</section>
</section>
</section>
<section>
<h2>User Needs</h2>
<section>
<h3>Perceivable</h3>
<section>
<h4>Provide consistent content </h4>
<p>(static / fixed)</p>
<section>
<h5>Users can perceive content</h5>
</section>
<section>
<h5>Users can perceive controls (roles, states and properties)</h5>
</section>
<section>
<h5>Users can perceive structure</h5>
</section>
<section>
<h5>Users can perceive purpose</h5>
</section>
<section>
<h5>Users can perceive input values</h5>
</section>
</section>
<section>
<h4>Reveal changed content</h4>
<section>
<h5>Users can perceive changes to content</h5>
</section>
<section>
<h5>Users can perceive changes to controls (roles, states and properties)</h5>
</section>
<section>
<h5>Users can perceive changes to purpose</h5>
</section>
<section>
<h5>Users can perceive changes to input values</h5>
</section>
</section>
</section>
<section>
<h3>Operable</h3>
<section>
<h4>Provide consistent interactions</h4>
<section>
<h5>Users can operate content</h5>
</section>
<section>
<h5>Users can operate controls (roles, states and properties)</h5>
</section>
<section>
<h5>Users can operate navigation</h5>
</section>
<section>
<h5>Users can navigate structure (document and application)</h5>
</section>
</section>
<section>
<h4>Allow adjustable content</h4>
<section>
<h5>Users can adjust duration requirements</h5>
</section>
<section>
<h5>Users can adjust content orientation</h5>
</section>
<section>
<h5>Users can adjust orientation in space</h5>
</section>
</section>
</section>
<section>
<h3>Understandable</h3>
<section>
<h4>Make appearance understandable</h4>
<section>
<h5>Users can understand content</h5>
</section>
<section>
<h5>Users can understand controls</h5>
</section>
<section>
<h5>Users can understand structure</h5>
</section>
<section>
<h5>Users can understand navigation</h5>
</section>
<section>
<h5>Users can understand changed content</h5>
</section>
<section>
<h5>Users can understand purpose</h5>
</section>
<section>
<h5>Users can understand relationships</h5>
</section>
</section>
<section>
<h4>Provide help and instructions</h4>
<section>
<h5>Users get instructions for content</h5>
</section>
<section>
<h5>Users get instructions for interaction</h5>
</section>
<section>
<h5>Users get instructions for support for modalities</h5>
</section>
<section>
<h5>Users get instructions for personalization options</h5>
</section>
<section>
<h5>Users get instructions for processes</h5>
</section>
<section>
<h5>Users get help through moderated (form) input</h5>
</section>
<section>
<h5>Users get help through alert awareness</h5>
</section>
</section>
<section>
<h4>Make position and orientation clear</h4>
<section>
<h5>Users can identify their position in content</h5>
</section>
<section>
<h5>Users can identify their position in context</h5>
</section>
<section>
<h5>Users can identify their position in a process</h5>
</section>
<section>
<h5>Users can identify their position in a space</h5>
</section>
<section>
<h5>Users can orientate themselves in immersive environments</h5>
</section>
<section>
<h5>Users can orientate themselves in augmented environments</h5>
</section>
</section>
<section>
<h4>Make discoverable</h4>
<section>
<h5>Users can discover content</h5>
</section>
<section>
<h5>Users can discover context</h5>
</section>
<section>
<h5>Users can discover customization options</h5>
</section>
</section>
</section>
<section>
<h3>Personalization</h3>
<section>
<h4>Customization</h4>
<section>
<h5>Users can customize or request content</h5>
</section>
<section>
<h5>Users can customize or request context</h5>
</section>
<section>
<h5>Users can customize or request functionality / settings</h5>
</section>
<section>
<h5>Users get customized (via platform) content</h5>
</section>
<section>
<h5>Users get customized (via platform) context</h5>
</section>
<section>
<h5>Users get customized (via platform) functionality</h5>
</section>
<section>
<h5>Users can control time-sensitive content</h5>
</section>
<section>
<h5>Users can control time-sensitive tasks</h5>
</section>
<section>
<h5>Users can control time-based media (including dynamic values, EQ, volume)</h5>
</section>
</section>
<section>
<h4>Preferences</h4>
<section>
<h5>Users personalization preferences are allowed</h5>
</section>
<section>
<h5>Users personalization preferences are honored by content authors</h5>
</section>
<section>
<h5>Users personalization preferences are not compromised by security</h5>
</section>
<section>
<h5>Users personalization preferences do not compromise privacy</h5>
</section>
<section>
<h5>Users can, device independently interact</h5>
</section>
<section>
<h5>Users can, device independently input data</h5>
</section>
<section>
<h5>Users can, device independently route and control output</h5>
</section>
</section>
</section>
<section>
<h3>Deceptive Patterns</h3>
<section>
<h4>Distractions and Interruptions</h4>
<section>
<h5>Users attention can be focussed</h5>
</section>
<section>
<h5>Users attention can be directed</h5>
</section>
<section>
<h5>Users attention can be shifted</h5>
</section>
</section>
<section>
<h4>No Harm</h4>
<section>
<h5>Users are not harmed neurologically</h5>
</section>
<section>
<h5>Users are not harmed emotionally</h5>
</section>
</section>
</section>
</section>
<section>
<h2>Meeting User Needs</h2>
<p class="note">This is a preliminary draft to document how user needs are met in various ways. </p>
<p>For each [=expected outcome=], ways to meet it are proposed for: </p>
<ul>
<li> Technologies </li>
<li> Content Authors </li>
<li> User Agents </li>
</ul>
<p>Other categories may be included later. Many user needs can be met in more than one way. The mechanism to meet user needs in one of the above areas may require support from one or more of the other areas. </p>
<section>
<h3>Ways to Meet User Needs</h3>
<p>User needs need to be analyzed for how they can be met. The following ways of meeting needs are currently understood: </p>
<ul>
<li> Author design </li>
<li> Author technical implementation </li>
<li> User agent accessibility support of standard features </li>
<li> User agent support of author-implemented accessibility features </li>
<li> Assistive technology support (including accessibility API mediation) </li>
</ul>
<section>
<h4>Author Implementation</h4>
</section>
<section>
<h4>User Agent Features</h4>
<section>
<h5>Accessibility Support in Mainstream User Agents</h5>
</section>
<section>
<h5>Assistive Technology</h5>
</section>
<section>
<h5>Accessibility APIs</h5>
</section>
</section>
</section>
<section>
<h3>Meeting User Needs Table</h3>
<p class="note">This version of the resource is primarily to show the structure, not yet a comprehensive documentation of how user needs can be met. </p>
<p>The table below shows how two of the user needs identified above might be met by technology features, author implementation, and user agent support. Each row of the table shows a related set of approaches, in which the approach in each column depends on successful implementation of the approaches in the other columns for that row. For instance, many author features depend on support from the technology as well as exposure from the user agents. Some approaches to meeting user needs do not require support from others, which is reflected by rows with blank columns. For instance, it is possible for a user agent to meet certain needs with no particular support provided by the technology or author. This layout is preliminary and a more expressive layout is sought.</p>
<table class="simple">
<thead>
<tr>
<th> User Need </th>
<th> Technology </th>
<th> Content Author </th>
<th> User Agent </th>
</tr>
</thead>
<tbody>
<tr>
<th rowspan="2" scope="rowgroup"> Text Alternatives </th>
<td>Provide a mechanism for author to create text alternatives and associate with content </td>
<td>Create text alternative content and associate with primary content using features of the content technology</td>
<td>Expose text alternatives provided by the author </td>
</tr>
<tr>
<td>Define parseable and semantically rich content encoding that supports automated creation of text alternatives</td>
<td>Encode content using a content technology that is sufficiently rich that machines can create useful automated text alternatives</td>
<td>Create automated text alternative content based on the semantics of the primary content</td>
</tr>
<tr>
<th rowspan="6" scope="rowgroup"> Color Contrast </th>
<td>Provide color definition features that allow authors to set colors to meet requirements </td>
<td>Use only colors that meet luminosity contrast guidelines </td>
<td> </td>
</tr>
<tr>
<td>Provide color definition features that allow users to override author-set colors </td>
<td> </td>
<td>Provide a feature for users to override author colors </td>
</tr>
<tr>
<td>Provide color definition semantics that allow colors of common object types to be globally remapped easily </td>
<td>Use semantically defined color mappings to allow user global preferences to be easily applied </td>
<td>Support semantically defined color mappings to allow users to define global preferences that are easily applied across a range of content </td>
</tr>
<tr>
<td></td>
<td>Provide a feature to allow users to define their own color preferences </td>
<td> </td>
</tr>
<tr>
<td></td>
<td>Provide a feature to allow users to request "high contrast" mode </td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td>Provide a "high contrast" mode that overrides author colors</td>
</tr>
</tbody>
</table>
</section>
</section>
<section>
<h2>Framework for Accessible Specification of Technologies</h2>
<p class="note">The content below is initial draft content intended to show how guidelines aimed at web technology developers might look. It has not yet been related to the user needs and ways of meeting them outlined above. It serves as initial brainstorming to help demonstrate viability of this set of guidelines.</p>
<p class="ednote">This section needs to be updated to reflect the functional and user needs matrix.</p>
</section>
<section class='appendix'>
<h2>Acknowledgments</h2>
<p>The following people contributed to the development of this document.</p>
<section id="ack_group">
<h4>Participants active in the development of this document</h4>
<ol>
<li>Jake Abma (Invited Expert) </li>
<li>Joshue O Connor (Invited Expert)</li>
<li>Michael Cooper (W3C/MIT)</li>
<li>Charles Hall (Invited Expert)</li>
<li>Todd Libby (Invited Expert)</li>
</ol>
</section>
<section>
<h2>Enabling funders</h2>
<p>This publication has been funded in part with U.S. Federal funds from the Health and Human Services, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR), initially under contract number ED-OSE-10-C-0067, then under contract number HHSP23301500054C, and now under HHS75P00120P00168. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Health and Human Services or the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.</p>
<p>This work is supported by the EC-funded <a href="https://www.w3.org/WAI/about/projects/wai-guide/">WAI-Guide Project</a>.</p>
</section>
</section>
</body>
</html>