-
Notifications
You must be signed in to change notification settings - Fork 0
/
index-original.html
944 lines (803 loc) · 59.7 KB
/
index-original.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
<!DOCTYPE html>
<html class="no-js" lang="pt-PT">
<head>
<!--
source: https://github.com/w3c/wai-statements/edit/master/generator.html
project: WAI-Tools
I changed the source code accordingly to make this standalone page. I did:
HTML: planning/statements/generator/index.html -> index.html
CSS: content-images/wai-statements/generator.css -> css/generator.css
JS: content-images/wai-statements/generator.js -> js/generator.js note: is near the bottom of the body
WAI Theme Assets: assets/css/style.css -> assets-wai/style.css
assets/scripts/main.js -> assets-wai/main.js note: this file is referenced in the script below
delete all <head> elements related w/ WAI Theme
TODO: at the end I think I can delete also the directory /assets-wai and all the references to them. Carefully, check before the tasks of main.js and style.css
-->
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title> Gerar uma Declaração de Acessibilidade | Web Accessibility Initiative (WAI) | W3C</title>
<link rel="stylesheet" href="css/generator.css">
<link rel="stylesheet" href="assets-wai/style.css">
<!-- contains the 'assets-wai/main.js' -->
<script>
document.documentElement.className = document.documentElement.className.replace('no-js', 'has-js');
function downloadJSAtOnload() {
var element = document.createElement("script");
element.src = "assets-wai/main.js";
document.body.appendChild(element);
}
window.addEventListener("load", downloadJSAtOnload, false);
</script>
</head>
<body id="top" class="page-generate-an-accessibility-statement">
<main id="main">
<h1>Gerador da Declaração de Acessibilidade</h1>
<div id="accstatement">
<section class="page create" hidden="hidden">
<div class="container">
<aside class="box">
<header class="box-h "> How to use this generator tool</header><div class="box-i">
<p>The information that you provide below will generate an accessibility statement that you can download and further refine. None of the fields are required. None of the information you enter is stored outside your web browser.</p>
</div>
</aside>
<nav class="box box-simple box-full" aria-labelledby="tocheading" id="toc">
<header id="tocheading" class="box-h box-h-simple box-h-full"> Page Contents</header>
<div class="box-i">
<ul>
<li>
<a href="#create-basic">Basic information</a>
</li>
<li>
<a href="#create-efforts">Your efforts</a>
</li>
<li>
<a href="#create-technical">Technical information</a>
</li>
<li>
<a href="#create-approval">Approval and complaints process</a>
</li>
</ul>
</div>
</nav>
<div style="display: flex; align-items: center;">
<div class="excol-all"></div>
<div style="text-align: right; flex:1">
<button type="button" class="showhidebutton button-small" aria-expanded="false" data-target=".information" data-showtext="Show all additional Information" data-hidetext="Hide all additional Infomation">Show all additional Information</button>
</div>
</div>
<form name="create_accessibility_statement_form">
<details open><summary markdown="block">
<h2 id="create-basic">Basic information</h2>
<p class="intro">In this section you can provide the minimal set of information recommended for your accessibility statement. This includes information about your organization, the accessibility standards you applied, and your contact information for feedback.</p>
</summary>
<div markdown="block">
<div class="group">
<h3 class="label">About your statement
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_about" data-target="#info_about" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_about" hidden="hidden">
<p>Here you can enter the name of your organization, and the web address and name of your website or mobile application. For mobile applications, include version information and the release date, to identify a specific version.</p>
</div>
<div class="field">
<label for="accstmt_org">Name of your organization</label>
<em>(Example: “Example Inc.”)</em>
<input type="text" id="accstmt_org"/>
</div>
<div class="field">
<label for="accstmt_url">Address of your website or mobile application</label>
<em>(Example: “https://example.org”)</em>
<input type="text" id="accstmt_url"/>
</div>
<div class="field">
<label for="accstmt_namesite">Name of your website or mobile application</label>
<em>(Example: “Example Store” or “Example App 1.2.3”)</em>
<input type="text" id="accstmt_namesite"/>
</div>
</div>
<div class="group">
<h3 class="label">Accessibility standards applied
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_standards" data-target="#info_standards" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_standards" hidden="hidden">
<p>Which accessibility standard have you been following? The
<a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG)</a>
is internationally recognized. The latest version is WCAG 2.1.</p>
</div>
<fieldset class="field" id="standard-applied">
<legend class="label">Accessibility standard followed:</legend>
<div class="radio-field">
<input type="radio" name="accstmnt_standard" id="accstmnt_standard_wcag21aa" checked="checked" value="WCAG 2.1 level AA"/>
<label for="accstmnt_standard_wcag21aa">WCAG 2.1 level AA</label>
</div>
<div class="radio-field">
<input type="radio" name="accstmnt_standard" id="accstmnt_standard_wcag20aa" value="WCAG 2.0 level AA"/>
<label for="accstmnt_standard_wcag20aa">WCAG 2.0 level AA</label>
</div>
<div class="radio-field">
<input type="radio" name="accstmnt_standard" id="accstmnt_standard_other" value="another standard"/>
<label for="accstmnt_standard_other">Other</label>
<input aria-label="Other standard name" type="text" id="accstmnt_standard_other_name">
</div>
</fieldset>
</div>
<div class="group">
<h3 class="label">Conformance status
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_conformance" data-target="#info_conformance" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_conformance" hidden="hidden">
<p>To what degree do you conform to the accessibility standard stated in the previous section? Sometimes there are justifiable reasons to not fully conform. You can indicate parts that do not yet fully conform, including guidance on how users can find help, in later sections of this form.</p>
</div>
<fieldset class="field" id="conformance-status">
<legend class="visuallyhidden">Conformance status</legend>
<div class="radio-field">
<input type="radio" name="accstmnt_conformance" id="accstmnt_conformance_full" value="Fully conformant"/>
<label for="accstmnt_conformance_full">
<span class="status">Fully conformant</span>:
<span class="meaning">the content fully conforms to the accessibility standard without any exceptions</span>
</label>
</div>
<div class="radio-field">
<input type="radio" name="accstmnt_conformance" id="accstmnt_conformance_partial" value="Partially conformant" checked="checked"/>
<label for="accstmnt_conformance_partial">
<span class="status">Partially conformant</span>:
<span class="meaning">some parts of the content do not fully conform to the accessibility standard</span>
<span>(you can indicate these parts in later sections of this form)</span>
</label>
</div>
<div class="radio-field">
<input type="radio" name="accstmnt_conformance" id="accstmnt_conformance_nonconformant" value="Non conformant"/>
<label for="accstmnt_conformance_nonconformant">
<span class="status">Non conformant</span>:
<span class="meaning">the content does not conform the accessibility standard</span>
</label>
</div>
<div class="radio-field">
<input type="radio" name="accstmnt_conformance" id="accstmnt_conformance_unknown" value="Not assessed"/>
<label for="accstmnt_conformance_unknown">
<span class="status">Not assessed</span>:
<span class="meaning">the content has not been evaluated or the evaluation results are not available</span>
</label>
</div>
<div class="radio-field">
<input type="radio" name="accstmnt_conformance" id="accstmnt_conformance_inapplicable" value=""/>
<label for="accstmnt_conformance_inapplicable">None</label>
</div>
<input id="accstmnt_conformance_meaning" type="hidden" value="">
</fieldset>
</div>
<div class="group">
<h3 class="label">Additional accessibility considerations
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_additional" data-target="#info_additional" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_additional" hidden="hidden">
<p>Sometimes you may be applying more accessibility requirements than those specified in the accessibility standard stated above. For example, you may be providing sign language videos or real-time captioning for live media. Here you can list these additional accessibility requirements.</p>
<p>
<strong>Example:</strong>
“Although our goal is WCAG 2.1 Level AA conformance, we have also applied some Level AAA Success Criteria: Images of text are only used for decorative purposes. Re-authentication after a session expires does not cause loss of data. Some videos have sign language interpretation.”</p>
</div>
<div class="field">
<label for="accstmt_additions">Additional accessibility requirements applied</label>
<textarea id="accstmt_additions" rows="3"></textarea>
</div>
</div>
<div class="group">
<h3 class="label">Feedback options
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_feedback" data-target="#info_feedback" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_feedback" hidden="hidden">
<p>In which ways can users can get in touch with your organization when they encounter an accessibility barrier? Ideally you should provide more than one option. Also indicate the duration after which users can expect a response from your organization.</p>
</div>
<fieldset class="group" id="form-feedback">
<legend class="visuallyhidden">Feedback options</legend>
<div class="field">
<label for="accstmnt_contact_phone">Phone</label>
<em>(Example: “+12 34 567 89 00”)</em>
<input type="tel" id="accstmnt_contact_phone"/>
</div>
<div class="field">
<label for="accstmnt_contact_email">E-mail</label>
<em>(Example: “[email protected]”)</em>
<input type="email" id="accstmnt_contact_email"/>
</div>
<div class="field">
<label for="accstmnt_contact_visit">Visitor Address</label>
<em>(Example: “Main Street 1, 234 Example Ville”)</em>
<input type="text" id="accstmnt_contact_visit"/>
</div>
<div class="field">
<label for="accstmnt_contact_write">Postal address</label>
<em>(Example: “PO Box 1, 234 Example Ville”)</em>
<input type="text" id="accstmnt_contact_write"/>
</div>
<div class="field">
<label for="accstmnt_contact_other">Other contact options</label>
<em>(Example: on social media; Twitter: @ExampleUser)</em>
<textarea id="accstmnt_contact_other"></textarea>
</div>
<div class="field">
<label for="accstmnt_contact_responsetime">Typical duration for response</label>
<em>(Example: “2 business days”)</em>
<input type="text" id="accstmnt_contact_responsetime"/>
</div>
</fieldset>
</div>
<div class="group">
<h3 class="label">Date of publication
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_date" data-target="#info_date" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_date" hidden="hidden">
<p>Providing a date helps users to understand if the accessibility statement is being actively maintained or outdated. Ideally the date of an accessibility statement should not exceed one year, or it may be considered unmaintained. Writing out the month makes the date clearer internationally (eg. "1 February 2019" rather than "01/02/2019", which is ambiguous).</p>
</div>
<div class="field">
<label for="accstmt_date">Publication date of this accessibility statement</label>
<input type="text" id="accstmt_date" class="today"/>
</div>
</div>
</div>
</details>
<details ><summary markdown="block">
<h2 id="create-efforts">Your efforts</h2>
<p class="intro">In this section you can describe the efforts your organization takes to ensure accessibility. This helps users to understand your sincerity and the validity of the claims you make in your accessibility statement.</p>
</summary>
<div markdown="block">
<h3 class="label">Organizational measures
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_measures" data-target="#info_measures" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_measures" hidden="hidden">
<p>List the measures that your organization undertakes to achieve sustainable accessibility. This includes measures such as procurement actions, training, raising awareness, and quality assurance. Some of these measures are pre-defined for your convenience but you can add more as needed.</p>
</div>
<fieldset class="group">
<legend class="visuallyhidden">Organizational measures</legend>
<ul class="nolist field" id="effort-list">
<li class="radio-field">
<input id="accstmnt_orginfo_measures_1" name="accstmnt_orginfo_measures" type="checkbox" value="Include accessibility as part of our mission statement."/>
<label for="accstmnt_orginfo_measures_1">Include accessibility as part of our mission statement.</label>
</li>
<li class="radio-field">
<input id="accstmnt_orginfo_measures_2" name="accstmnt_orginfo_measures" type="checkbox" value="Include accessibility throughout our internal policies."/>
<label for="accstmnt_orginfo_measures_2">Include accessibility throughout our internal policies.</label>
</li>
<li class="radio-field">
<input id="accstmnt_orginfo_measures_3" name="accstmnt_orginfo_measures" type="checkbox" value="Integrate accessibility into our procurement practices."/>
<label for="accstmnt_orginfo_measures_3">Integrate accessibility into our procurement practices.</label>
</li>
<li class="radio-field">
<input id="accstmnt_orginfo_measures_4" name="accstmnt_orginfo_measures" type="checkbox" value="Appoint an accessibility officer and/or ombudsperson."/>
<label for="accstmnt_orginfo_measures_4">Appoint an accessibility officer and/or ombudsperson.</label>
</li>
<li class="radio-field">
<input id="accstmnt_orginfo_measures_5" name="accstmnt_orginfo_measures" type="checkbox" value="Provide continual accessibility training for our staff."/>
<label for="accstmnt_orginfo_measures_5">Provide continual accessibility training for our staff.</label>
</li>
<li class="radio-field">
<input id="accstmnt_orginfo_measures_6" name="accstmnt_orginfo_measures" type="checkbox" value="Assign clear accessibility targets and responsibilities."/>
<label for="accstmnt_orginfo_measures_6">Assign clear accessibility targets and responsibilities.</label>
</li>
<li class="radio-field">
<input id="accstmnt_orginfo_measures_7" name="accstmnt_orginfo_measures" type="checkbox" value="Employ formal accessibility quality assurance methods."/>
<label for="accstmnt_orginfo_measures_7">Employ formal accessibility quality assurance methods.</label>
</li>
</ul>
<div id="accstmnt_orginfo_othermeasures" class="group">
<div class="field line">
<label for="accstmnt_orginfo_othermeasures_1">Other measure 1</label>
<em>(Example: “Include people with disabilities in our design personas”)</em>
<input type="text" id="accstmnt_orginfo_othermeasures_1" name="accstmnt_orginfo_measures"/>
</div>
<div class="field proto">
<label for="accstmnt_orginfo_othermeasures_[n]">Other measure [n]</label>
<input type="text" id="accstmnt_orginfo_othermeasures_[n]" name="accstmnt_orginfo_measures"/>
</div>
</div>
<button type="button" class="add-line">
Add another measure
</button>
</fieldset>
</div>
</details>
<details ><summary markdown="block">
<h2 id="create-technical">Technical information</h2>
<p class="intro">In this section you can provide more technical details to help users understand any issues they may be observing. This includes information about compatibility with web browsers and assistive technologies.</p>
</summary>
<div markdown="block">
<h3 class="label">Accessibility limitations
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_limitations" data-target="#info_limitations" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_limitations" hidden="hidden">
<p>There are many situations in which limitations to accessibility can occur. For example, you may not be able ensure instant accessibility of user-generated content. Providing transparency on such situations helps users to understand any issue they may be observing, and to find alternatives where applicable. Under the EU Web Accessibility Directive, public bodies are required to provide information on the parts of the content that do not conform, the reason for not conforming, and, if applicable, where to find accessible alternatives.</p>
</div>
<fieldset class="group">
<legend class="visuallyhidden">Accessibility limitations</legend>
<p class="expl">List the
<em>content parts</em>
that have accessibility limitations, a
<em>description of the issue</em>
that may be observed by users, a brief explanation of
<em>why the issue occurs</em>, and
<em>what to do in the mean time</em>, such as who to contact or where to find accessibility alternatives where appropriate.</p>
<div id="accstmnt_issues">
<fieldset id="accstmnt_limitation_1" class="group line">
<legend>Accessibility limitation 1</legend>
<div class="field">
<label for="accstmnt_limitation_1_element">Content part</label>
<em>(Example: “Comments from users”)</em>
<input type="text" id="accstmnt_limitation_1_element" name="element"/>
</div>
<div class="field">
<label for="accstmnt_limitation_1_description">Description of the issue</label>
<em>(Example: “Uploaded images may not have text alternatives”)</em>
<input type="text" id="accstmnt_limitation_1_description" name="description"/>
</div>
<div class="field">
<label for="accstmnt_limitation_1_reason">Why the issue occurs</label>
<em>(Example: “We cannot ensure the quality of contributions”)</em>
<input type="text" id="accstmnt_limitation_1_reason" name="reason"/>
</div>
<div class="field">
<label for="accstmnt_limitation_1_us">What we are doing about it</label>
<em>(Example: “We monitor user comments and typically repair issues within 2 business days”)</em>
<input type="text" id="accstmnt_limitation_1_us" name="us"/>
</div>
<div class="field">
<label for="accstmnt_limitation_1_you">What to do in the meantime</label>
<em>(Example: “Please use the ‘report issue’ button if you encounter an issue”)</em>
<input type="text" id="accstmnt_limitation_1_you" name="you"/>
</div>
</fieldset>
<fieldset id="accstmnt_limitation_[n]" class="group proto">
<legend>Accessibility limitation [n]</legend>
<div class="field">
<label for="accstmnt_limitation_[n]_element">Content part</label>
<input type="text" id="accstmnt_limitation_[n]_element" name="element"/>
</div>
<div class="field">
<label for="accstmnt_limitation_[n]_description">Description of the issue</label>
<input type="text" id="accstmnt_limitation_[n]_description" name="description"/>
</div>
<div class="field">
<label for="accstmnt_limitation_[n]_reason">Why the issue occurs</label>
<input type="text" id="accstmnt_limitation_[n]_reason" name="reason"/>
</div>
<div class="field">
<label for="accstmnt_limitation_[n]_us">What we are doing about it</label>
<input type="text" id="accstmnt_limitation_[n]_us" name="us"/>
</div>
<div class="field">
<label for="accstmnt_limitation_[n]_you">What to do in the meantime</label>
<input type="text" id="accstmnt_limitation_[n]_you" name="you"/>
</div>
</fieldset>
<button type="button" class="add-line">
Add another limitation
</button>
</div>
</fieldset>
<h3 class="label">Compatibility with user environment
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="support_asstech" data-target="#support_asstech" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="support_asstech" hidden="hidden">
<p>Despite best efforts, accessibility may not work well in every combination of operating system, web browser, and assistive technology. Developers typically test their websites and mobile applications with common user environments, to determine compatibility. WCAG defines requirements for accessibility features provided by content authors to be
<a href="https://www.w3.org/TR/WCAG21/#dfn-accessibility-supported">accessibility supported</a>. Communicating this compatibility expectation helps user to determine if that is the cause for any issues they may be observing.</p>
</div>
<fieldset class="group" id="compatible_tech">
<legend class="visuallyhidden">Compatibility with user environment</legend>
<p class="expl">Describe the environments (combinations of web browsers, assistive technologies, and operating systems) that the content is expected to work with. These should be in-line with the WCAG definition of
<a href="https://www.w3.org/TR/WCAG21/#dfn-accessibility-supported">accessibility supported</a>
use of technologies.</p>
<div class="field line">
<label for="accstmnt_asstech_compatible_1">Environment 1</label>
<em>(Example: “browser X with assistive technology Y on operating system Z”)</em>
<input type="text" id="accstmnt_asstech_compatible_1" name="accstmnt_asstech_compatible"/>
</div>
<div class="field proto">
<label for="accstmnt_asstech_compatible_[n]">Environment [n]</label>
<input type="text" id="accstmnt_asstech_compatible_[n]" name="accstmnt_asstech_compatible"/>
</div>
<button class="add-line" type="button">Add another compatible environment</button>
</fieldset>
<h3 class="label">Known incompatibility
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="support_incompatible" data-target="#support_incompatible" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="support_incompatible" hidden="hidden">
<p>Help users understand what versions of operating systems, web browsers, and assistive technologies are not (or no longer) supported. This helps user to determine if they can use your website or mobile application with their current environments.</p>
</div>
<fieldset class="group" id="incompatible_tech">
<legend class="visuallyhidden">Known incompatibility</legend>
<p class="expl">Describe the environments (combinations of web browsers, assistive technologies, and operating systems) that the content is not expected to work with.</p>
<div class="field line">
<label for="accstmnt_asstech_incompatible_1">Environment 1</label>
<em>(Example: “browsers older than 3 major versions” or “Mobile operating systems older than 5 years”)</em>
<input type="text" id="accstmnt_asstech_incompatible_1" name="accstmnt_asstech_incompatible"/>
</div>
<div class="field proto">
<label for="accstmnt_asstech_incompatible_[n]">Environment [n]</label>
<input type="text" id="accstmnt_asstech_incompatible_[n]" name="accstmnt_asstech_incompatible"/>
</div>
<button type="button" class="add-line">
Add another incompatible environment
</button>
</fieldset>
<h3 class="label">Technologies used
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="support_tech" data-target="#support_tech" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="support_tech" hidden="hidden">
<p>You may be relying on specific web technologies, such as JavaScript, WAI-ARIA, or SVG to ensure accessibility of your content. Communicating this expectation in the accessibility statement can help users to understand the reason for issues they may be observing. For example, the accessibility features may not work because the user disabled JavaScript. The
<a href="https://www.w3.org/TR/WCAG21/#cc4">WCAG 2 conformance requirement 4</a>
on "<em>accessibility supported was of using technologies relied upon</em>" provides more background.</p>
</div>
<p class="expl">Describe the technologies that are relied upon for conformance. The content would not conform if that technology is turned off or is not supported.</p>
<fieldset class="field">
<legend class="label">Technologies:</legend>
<ul id="tech_relied" class="nolist">
<li class="radio-field">
<input type="checkbox" id="accstmnt_tech_html" name="accstmnt_tech" value="HTML"/>
<label for="accstmnt_tech_html">HTML</label>
</li>
<li class="radio-field">
<input type="checkbox" id="accstmnt_tech_aria" name="accstmnt_tech" value="WAI-ARIA"/>
<label for="accstmnt_tech_aria">WAI-ARIA</label>
</li>
<li class="radio-field">
<input type="checkbox" id="accstmnt_tech_css" name="accstmnt_tech" value="CSS"/>
<label for="accstmnt_tech_css">CSS</label>
</li>
<li class="radio-field">
<input type="checkbox" id="accstmnt_tech_js" name="accstmnt_tech" value="JavaScript"/>
<label for="accstmnt_tech_js">JavaScript</label>
</li>
<li class="radio-field">
<input type="checkbox" id="accstmnt_tech_smil" name="accstmnt_tech" value="SMIL"/>
<label for="accstmnt_tech_smil">SMIL</label>
</li>
<li class="radio-field proto">
<input type="checkbox" id="accstmnt_tech_other_[n]" value="other" checked="checked"/>
<span id="accstmnt_tech_other_label_[n]">
<label for="accstmnt_tech_other_[n]">Other [n]</label>
<span class="visuallyhidden">
name</span></span>
<input id="accstmnt_tech_other_[n]_value" type="text" aria-describedby="accstmnt_tech_other_label_[n]" name="accstmnt_tech"/>
</li>
</ul>
<button class="add-line" type="button">Add another technology</button>
</fieldset>
<h3 class="label">Assessment approach
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_accstmnt_approach" data-target="#info_accstmnt_approach" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_accstmnt_approach" hidden="hidden">
<p>How did you assess your website or mobile application, to determine the information provided in the previous sections? This helps users understand your quality assurance process and the background for the claims you make in your accessibility statement.</p>
</div>
<fieldset id="accstmnt_assessment" class="group">
<legend class="visuallyhidden">Assessment approach</legend>
<ul class="nolist">
<li class="radio-field">
<input id="accstmnt_approach_1" name="accstmnt_approach" type="checkbox" value="Self-evaluation"/>
<label for="accstmnt_approach_1">Self-evaluation: the content was evaluated by your own organization or the developer of the content</label>
</li>
<li class="radio-field">
<input id="accstmnt_approach_2" name="accstmnt_approach" type="checkbox" value="External evaluation"/>
<label for="accstmnt_approach_2">External evaluation: the content was evaluated by an external entity not involved in the design and development process</label>
</li>
</ul>
<div class="group">
<div class="field line">
<label for="accstmnt_approach_other_1">Other approach 1</label>
<em>(Example: a formal quality assurance process throughout the design and development process)</em>
<input type="text" id="accstmnt_approach_other_1" name="accstmnt_approach"/>
</div>
<div class="field proto">
<label for="accstmnt_approach_other_[n]">Other approach [n]</label>
<input type="text" id="accstmnt_approach_other_[n]" name="accstmnt_approach"/>
</div>
<button type="button" class="add-line">Add another approach</button>
</div>
</fieldset>
<h3 class="label">Related evidence
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="support_related" data-target="#support_related" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="support_related" hidden="hidden">
<p>Provide links to related background and evidence to support the claims you make in this accessibility, and to provide more transparency and credibility. This can include an evaluation report, an evaluation statement, or a certification.</p>
</div>
<div class="group">
<div class="field">
<label for="accstmnt_audit_url">Link to recent evaluation report
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_audit_url" data-target="#info_audit_url" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</label>
<em>(Example: “https://example.org/accessibility-evaulation-report”)</em>
<div class="information" id="info_audit_url" hidden="hidden">
<p>An evaluation report provides details on which accessibility requirements are met, and which are not. While this is usually more technical of nature than the average user, it can help some users to understand issues they have been observing. You can use the
<a href="https://www.w3.org/WAI/eval/report-tool/">WCAG-EM Evaluation Report Tool</a>
to create an evaluation report. Place the link to the report here.</p>
</div>
<input type="url" id="accstmnt_audit_url"/>
</div>
<div class="field">
<label for="accstmnt_audit_wcagem">Link to evaluation statement
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_audit_statement" data-target="#info_audit_statement" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</label>
<em>(Example: “https://example.org/accessibility-evaulation-statement”)</em>
<div class="information" id="info_audit_statement" hidden="hidden">
<p>An evaluation statement summarizes the essential outcomes of an evaluation report. The
<a href="https://www.w3.org/TR/WCAG-EM/">Website Accessibility Conformance Evaluation Methodology (WCAG-EM)</a>
defines requirements for evaluation statements in
<a href="https://www.w3.org/TR/WCAG-EM/#step5c">Step 5.c</a>
of the document. This can be provided instead of or in addition to an evaluation report provided above.</p>
</div>
<input type="url" id="accstmnt_audit_wcagem"/>
</div>
<div class="field line">
<label for="accstmnt_audit_other_1">Other evidence 1</label>
<em>(Example: “https://example.org/accessibility-evaulation-certificate”)</em>
<input type="text" id="accstmnt_audit_other_1" name="accstmnt_audit_other"/>
</div>
<div class="field proto">
<label for="accstmnt_audit_other_[n]">Other evidence [n]</label>
<input type="text" id="accstmnt_audit_other_[n]" name="accstmnt_audit_other"/>
</div>
<button type="button" class="add-line">
Add another related evidence
</button>
</div>
</div>
</details>
<details ><summary markdown="block">
<h2 id="create-approval">Approval and complaints process</h2>
<p class="intro">In this section you can add information about the formal approval of this accessibility statement and, if applicable, any complaints escalation procedure.</p>
</summary>
<div markdown="block">
<h3 class="label">Formal approval
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="org_approved" data-target="#org_approved" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="org_approved" hidden="hidden">
<p>Your organization may want to formally approve this accessibility statement, for example for internal purposes or to show users that this is part of the corporate policy.</p>
</div>
<fieldset class="group">
<legend class="visuallyhidden">Approval</legend>
<div class="field">
<label for="accstmnt_orginfo_approved_name">Name of person or department</label>
<em>(Example: “Communication Department”)</em>
<input type="text" id="accstmnt_orginfo_approved_name"/>
</div>
<div class="field">
<label for="accstmnt_orginfo_approved_function">Function</label>
<em>(Example: “Director of Communication”)</em>
<input type="text" id="accstmnt_orginfo_approved_function"/>
</div>
</fieldset>
<h3 class="label">Formal complaints
<button type="button" class="showhidebutton button-small" aria-expanded="false" aria-controls="info_complaints" data-target="#info_complaints" data-showtext="Show Info" data-hidetext="Hide Info">Show Info</button>
</h3>
<div class="information" id="info_complaints" hidden="hidden">
<p>In some situations you may want to or may be required to provide information about a formal complaints procedures. For example, a quality management process within your organization may require you to establish a formal complaints procedure with clear escalation paths. The
<a href="https://eur-lex.europa.eu/eli/dir/2016/2102/oj">EU Web Accessibility Directive
<svg aria-label="External Site" class="icon-external-link "><use xlink:href="/wai-statements/assets/images/icons.svg#icon-external-link"></use></svg></a>
foresees EU countries to have legal “enforcement procedures” when users are not satisfied with the responses from public bodies. Inform users about any such formal complaints procedures. This may also motivate them to provide you with valuable feedback about the accessibility of your content.</p>
<p>
<strong>Example:</strong>
“We aim to respond to accessibility feedback within 2 business days, and to propose a solution within 10 business days. You are entitled to escalate a complaint to [organizational or legal entity], should you be dissatisfied with our response to you.”</p>
</div>
<div class="field">
<label for="accstmt_complaints">Describe any formal complaints procedures</label>
<textarea id="accstmt_complaints" rows="3"></textarea>
</div>
</div>
</details>
<aside class="box"><div class="box-i">
<div class="statement-actions">
<a class="button" href="#preview" data-action="statement_preview">
Preview your accessibility statement
</a>
</div>
</div>
</aside>
</form>
</div>
</section>
<section class="page preview" hidden="hidden">
<aside class="box box-example"><header class="box-h box-h-example"> Preview your accessibility statement</header><div class="box-i">
<div id="statement_generated">
<div id="statement_header">
<h2>Accessibility Statement for <span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME"></span></h2>
<p>
<span class="basic-information organization-name" data-print="accstmt_org" data-printdefault="ORGANIZATION"></span>
is committed to ensuring digital accessibility for people with disabilities.
We are continually improving the user experience for everyone, and applying the relevant accessibility standards.
</p>
</div>
<div id="statement-measures-block" data-if="accstmnt_orginfo_measures">
<h3>Measures to support accessibility</h3>
<p>
<span class="basic-information organization-name" data-print="accstmt_org" data-printdefault="ORGANIZATION"></span>
takes the following measures to ensure accessibility of
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME"></span>:
</p>
<ul id="statement-measures" class="organizational-effort accessibility-measures" data-print="accstmnt_orginfo_measures" data-printfilter="capitalize"></ul>
</div>
<div id="statement-conformance" data-if="accstmnt_conformance">
<h3>Conformance status</h3>
<p>
The <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG)</a> defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME">WEBSITE_NAME</span>
is
<span class="basic-information conformance-status" data-print="accstmnt_conformance" data-printfilter="lowercase"></span>
with
<span class="basic-information conformance-standard"><span data-print="accstmnt_standard" data-if="accstmnt_standard_other_name" data-negate></span><span data-print="accstmnt_standard_other_name" data-if="accstmnt_standard_other_name"></span>.</span>
<span data-if="accstmnt_conformance_meaning">
<span class="basic-information conformance-status" data-print="accstmnt_conformance"></span>
means that
<span class="basic-information conformance-meaning" data-print="accstmnt_conformance_meaning" data-printdefault="CONFORMANCE_MEANING"></span>.
</span>
</p>
</div>
<div id="statement-additions" data-if="accstmt_additions">
<h4>Additional accessibility considerations</h4>
<p class="basic-information conformance-additions" data-print="accstmt_additions" data-printfilter="capitalize"></p>
</div>
<div data-if="accstmnt_contact_phone, accstmnt_contact_email, accstmnt_contact_visit, accstmnt_contact_write, accstmnt_contact_other">
<h3>Feedback</h3>
<p>
We welcome your feedback on the accessibility of
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME"></span>.
Please let us know if you encounter accessibility barriers on
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME"></span>:
</p>
<ul class="basic-information feedback h-card">
<li data-if="accstmnt_contact_phone">
Phone:
<span class="phone-number p-tel" data-print="accstmnt_contact_phone"></span>
</li>
<li data-if="accstmnt_contact_email">
E-mail:
<a class="email u-email" href="mailto:" data-print="accstmnt_contact_email"></a>
</li>
<li data-if="accstmnt_contact_visit">
Visitor address:
<span class="visitor-address p-extended-address" data-print="accstmnt_contact_visit"></span>
</li>
<li data-if="accstmnt_contact_write">
Postal address:
<span class="postal-address p-adr" data-print="accstmnt_contact_write"></span>
</li>
<li class="contact-other p-note" data-if="accstmnt_contact_other" data-print="accstmnt_contact_other"></li>
</ul>
<p data-if="accstmnt_contact_responsetime">
We try to respond to feedback within <span class="feedback responsetime" data-print="accstmnt_contact_responsetime"></span>.
</p>
</div>
<div id="statement-asstech" data-if="accstmnt_asstech_compatible, accstmnt_asstech_incompatible">
<h3>Compatibility with browsers and assistive technology</h3>
<div id="statement-asstech-compatible-block">
<p>
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME"></span>
is designed to be compatible with the following assistive technologies:
</p>
<ul id="statement-asstech-compatible" class="technical-information compatible-environments" data-print="accstmnt_asstech_compatible" data-printdefault="COMPATIBLE_LIST"></ul>
</div>
<div id="statement-asstech-incompatible-block" data-if="accstmnt_asstech_incompatible">
<p>
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME"></span>
is not compatible with:
</p>
<ul id="statement-asstech-incompatible" class="technical-information incompatible-environments" data-print="accstmnt_asstech_incompatible"></ul>
</div>
</div>
<div id="statement-conftech" data-if="accstmnt_tech">
<h3>Technical specifications</h3>
<p>
Accessibility of
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME"></span>
relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
</p>
<ul id="statement-tech" class="technical-information technologies-used" data-print="accstmnt_tech"></ul>
<p>These technologies are relied upon for conformance with the accessibility standards used.</p>
</div>
<div id="statement-limitations-block">
<h3>Limitations and alternatives</h3>
<p>
Despite our best efforts to ensure accessibility of
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME">WEBSITE_NAME</span>, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.
</p>
<p>
Known limitations for
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME">WEBSITE_NAME</span>:
</p>
<ol id="statement-limitations" class="technical-information accessibility-limitations"></ol>
</div>
<div id="statement-assessment-block" data-if="accstmnt_approach">
<h3>Assessment approach</h3>
<p>
<span class="basic-information organization-name" data-print="accstmt_org" data-printdefault="ORGANIZATION">ORGANIZATION</span>
assessed the accessibility of
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME">WEBSITE_NAME</span>
by the following approaches:
</p>
<ul id="statement-assessments" class="technical-information assessment-approaches" data-print="accstmnt_approach"></ul>
</div>
<div data-if="accstmnt_audit_url">
<h3>Evaluation report</h3>
<p>
An evaluation report for
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME">WEBSITE_NAME</span>
is available at:
<a class="technical-information related-evidence" href="" data-print="accstmnt_audit_url"></a>.
</p>
</div>
<div data-if="accstmnt_audit_wcagem">
<h3>Evaluation statement</h3>
<p>
An evaluation statement for
<span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME">WEBSITE_NAME</span>
is available at:
<a class="technical-information related-evidence" href="" data-print="accstmnt_audit_wcagem"></a>.
</p>
</div>
<div data-if="accstmnt_audit_other">
<h3>Other evidence</h3>
<p>Other related evidence for <span class="basic-information website-name" data-print="accstmt_namesite" data-printdefault="WEBSITE_NAME"></span> is available at:</p>
<ul data-print="accstmnt_audit_other" class="technical-information related-evidence-other"></ul>
</div>
<div id="statement-approval-block" data-if="accstmnt_orginfo_approved_name, accstmnt_orginfo_approved_function">
<h3>Formal approval of this accessibility statement</h3>
<p>This Accessibility Statement is approved by:</p>
<p class="approval">
<span class="basic-information organization-name" data-print="accstmt_org" data-printdefault="ORGANIZATION"></span><br/>
<span class="approved-by" data-print="accstmnt_orginfo_approved_name" data-printdefault="APPROVED_BY"></span><br/>
<span class="approved-by-jobtitle" data-print="accstmnt_orginfo_approved_function" data-if="accstmnt_orginfo_approved_function"></span>
</p>
</div>
<div data-if="accstmt_complaints">
<h3>Formal complaints</h3>
<p class="complaints" data-print="accstmt_complaints"></p>
</div>
<hr noshade="noshade"/>
<p>
This statement was created on
<span class="basic-information statement-created-date" data-print="accstmt_date" data-printdefault="DATE"></span>
using the <a href="http://localhost:4000/wai-statements/planning/statements/">W3C Accessibility Statement Generator Tool</a>.
</p>
</div>
</div>
</aside>
<div class="button-group statement-actions">
<a class="button" href="#create">Back to generator tool</a>
<button type="button" data-action="preview_save_as_html">Download as HTML page</button>
</div>
</section>
</div>
<!-- generator standalone js -->
<script src="js/generator.js"></script>
<a class="button button-backtotop" href="#top"><span><svg aria-hidden="true" class="icon-arrow-up "><use xlink:href="/wai-statements/assets/images/icons.svg#icon-arrow-up"></use></svg> Voltar ao Topo</span></a>
</main>
<!-- Footer -->
<footer class="page-footer default-grid" aria-label="Página">
<div class="inner">
<p><strong>Última atualização:</strong> 11 de fevereiro 2019.</p>
<p><strong>Nota:</strong> O presente Gerador em português da Declaração de Acessibilidade é uma adaptação da <a href="https://www.w3.org/WAI/planning/statements/" title="Projeto WAI-Tools">Declaração de Acessibilidade</a> desenvolvida pelo <a href="https://www.w3.org/WAI/EO/" lang="en">Education and Outreach Working Group (EOWG)</a> como parte do <a href="https://www.w3.org/WAI/Tools/">projeto <span lang="en">WAI-Tools</span></a>, co-financiado pela Comissão Europeia, ao abrigo do Programa Horizon 2020 (780057). <a href="../acknowledgements/">Agradecimentos</a>.</p>
</div>
</footer>
<!-- Details4Everybody -->
<script src="/wai-statements/assets/scripts/details4everybody.js?1549738288064434000"></script>
<!-- SVG4Everybody -->
<script src="/wai-statements/assets/scripts/svg4everybody.js?1549738288064434000"></script>
<script>
svg4everybody();
</script>
<!-- Matomo -->
<script>
var _paq = _paq || [];
/* tracker methods like "setCustomDimension" should be called before "trackPageView" */
_paq.push(["setDoNotTrack", true]);
_paq.push(['trackPageView']);
_paq.push(['enableLinkTracking']);
(function() {
var u="//www.w3.org/analytics/piwik/";
_paq.push(['setTrackerUrl', u+'piwik.php']);
_paq.push(['setSiteId', '328']);
var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'piwik.js'; s.parentNode.insertBefore(g,s);
})();
</script>
<noscript><p><img src="//www.w3.org/analytics/piwik/piwik.php?idsite=328&rec=1" style="border:0;" alt="" /></p></noscript>
<!-- End Matomo Code -->
</body>
</html>