forked from ASSETS-Conference/assets2022
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathguidelines-policies.html
221 lines (193 loc) · 15.2 KB
/
guidelines-policies.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
<!doctype html>
<html lang="en">
<head>
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-59JZV5ZYEB"></script>
<script src="./assets/js/analytics.js"></script>
<!-- Meta data -->
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="ASSETS 2023 official website | Guidelines & Policies">
<meta name="keywords" content="ASSETS 2023, ASSETS'23, SIGACCESS, Guidelines, policies">
<meta name="author" content="">
<meta name="generator" content="">
<!-- Metadata tags for link preview -->
<meta property="og:type" content="website" />
<meta name="title" property="og:title" content="ASSETS 2023 | Guidelines & Policies" />
<meta name="image" property="og:image" content="https://assets22.sigaccess.org/assets/img/large/ASSETS2023_Logo.png" />
<meta name="og:title" content="ASSETS 2023 | The 24th International ACM SIGACCESS Conference on Computers and Accessibility" />
<meta name="og:image" content="https://assets22.sigaccess.org/assets/img/large/ASSETS2023_Logo.png" />
<title>ASSETS 2023 | Guidelines & Policies</title>
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
<link rel="manifest" href="/site.webmanifest">
<link rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="theme-color" content="#ffffff">
<!-- Bootstrap core CSS -->
<link href="./assets/dist/css/bootstrap.min.css" rel="stylesheet">
<!-- Custom styles for this template -->
<link href="./assets/css/style.css" rel="stylesheet">
<link href="./assets/css/navbar.css" rel="stylesheet">
<link href="./assets/css/committees.css" rel="stylesheet">
<!-- Javascript -->
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js"></script>
<script src="./assets/dist/js/bootstrap.bundle.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.0/jquery.min.js" integrity="sha512-894YE6QWD5I59HgZOGReFYm4dnWc1Qt5NtvYSaNcOP+u1T9qYdvdihz0PPSiiqn/+/3e7Jo4EaG7TubfWGUrMQ==" crossorigin="anonymous" referrerpolicy="no-referrer"></script>
</head>
<body>
<main>
<!--Navigation bar-->
<div id="navbar"></div>
<script>
$(function(){
$("#navbar").load("navbar.html");
});
</script>
<!--Navigation bar-->
<div id="content">
<!-- Jumbotron -->
<div id="top-jumbotron-cfp" class="jumbotron jumbotron-fluid text-light bg-overlay image-wrapper">
<div class="container px-4 py-5 text-center content">
<span class="d-flex justify-content-center align-items-center mt-5">
<div>
<h1 class="display-6 confTitle mt-4 mb-0">Guidelines & Policies</h1>
</div>
</span>
</div>
</div>
<!-- Jumbotron -->
<!-- Content -->
<!-- Creating Accessible PDFs -->
<section class="callout_section_0 p-3" id="a11y-pdfs">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center">Creating Accessible PDFs</h2>
<p>ACM publications are read (and reviewed) by many people. Making your paper accessible will help to promote the equal participation of people with disabilities in science and engineering. This note describes how to check if your PDF is accessible, and how to fix the most common accessibility problems. For more information please refer to <a href="http://www.adobe.com/accessibility/resources.html" target="_blank">Adobe's accessibility resource center</a>.</p>
</div>
</div>
</div>
</section>
<section class="callout_section_1 p-3">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center">How do I test if my PDF is accessible?</h3>
<ul>
<li><b>The document should be tagged.</b> In Adobe Acrobat Pro: Go to the 'File' menu. 'Document properties'. 'Description' tab. Look for 'Tagged PDF: Yes' among the set of advanced properties. If you do not have access to Adobe Acrobat, try selecting some text in the PDF and pasting it into a text editor. If you can't do this, or the text looks wrong, chances are your document is not readable with a screen reader.</li>
<li><b>Check the accessibility.</b> In Adobe Acrobat Pro: Go to the 'Advanced' menu. 'Accessibility'. 'Full Check'. The checker will report accessibility problems.</li>
<li><b>Fonts should be embedded</b>, or your PDF will need to be regenerated, and you may lose accessibility that you have added. In Adobe Acrobat Pro: Go to the 'File' menu. 'Document properties'. 'Fonts 'tab. All of the fonts should have the word 'embedded' in parentheses after the font name (unless they are not visible in the final document).</li>
</ul>
</div>
</div>
</div>
</section>
<section class="callout_section_0 p-3">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center">How do I fix accessibility problems?</h3>
<p>Word users should correct as many problems as possible in the Word source file rather than the pdf, as described in the next section. On a PC, the Adobe plugin for Word can export accessibility features from the Word document into the pdf.</p>
<p>On a Mac, this is not the case. Those using Word on a Mac, and all LaTeX users will need to edit the PDF directly using Adobe Acrobat. A better basic PDF may be produced by using latex2pdf as opposed to ps2pdf. See also the <a href="http://webaim.org/techniques/acrobat/converting" target="_blank">WebAim PDF Accessibility primer</a> which provides information for OpenOffice users.</p>
<p>The accessibility checker in Adobe Acrobat Pro provides help with fixing many accessibility problems. The following steps are for Adobe Acrobat Pro 9. <a href="http://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-pdf-author-guide/" target="_blank">More detailed instructions for Adobe Acrobat Pro XI</a>, and a <a href="https://www.youtube.com/watch?v=fO4udYorD6g" target="_blank">video</a>, are also available. Please see <a href="http://www.adobe.com/accessibility/resources.html" target="_blank">Adobe's best practices</a> for instructions covering more versions of Adobe Acrobat.</p>
<ul>
<li><b>Add tags.</b> Go to the 'Advanced' menu. Select 'Accessibility', then 'Add tags to document'.</li>
<li><b>Add alternative text for figures.</b> Context-click the Figure, select 'Properties', and fill in 'Alternate Text'. If no 'Properties' option appears, go to the 'Advanced' menu, select 'Touch Up Reading Order', and then try context-clicking on the figures again, looking for an 'Edit alternate text' option.</li>
<li><b>Specify the document language.</b> Go to the 'File' menu. Select 'Properties', then the 'Advanced' tab, 'Language' field. In some versions of Acrobat, the 'Properties' option is called 'Document Properties'. In some versions the 'Language' field is in a 'Reading Options' tab.</li>
<li><b>Define tab order.</b>
<ul>
<li>Go to the 'View' menu. Select 'Navigation tabs', then 'Pages'.</li>
<li>Click on any page, then type Ctrl-A (or Command-A on a Mac) to select all the pages.</li>
<li>Go to the 'Options' menu in the top right of the dialog box (icon showing two cogs), and select 'Page Properties'.</li>
<li>In the 'Tab Order' tab, select 'Use document structure'.</li>
</ul></li>
<li><b>Make sure tables have headings.</b>
<ul>
<li>Go to the 'View' menu. Select 'Navigation tabs', then 'Tags'.</li>
<li>Select the 'Tags' tab. This panel shows the document structure as a tree.</li>
<li>Navigate to the table cells that should be headers.</li>
<li>Check they have the type <TH>. If not, then right click on the header cell, select 'properties', select the 'Tag' tab, and change the value for 'Type' to 'Table Header Cell'.</li>
</ul></li>
</ul>
</div>
</div>
</div>
</section>
<section class="callout_section_1 p-3">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center">Creating an accessible PDF directly from Word</h3>
<p>The following link provides step-by-step instructions for adding basic accessibility information to a Word document on a PC, then exporting it to a PDF document intended for ACM: <a href="http://www.sigaccess.org/welcome-to-sigaccess/resources/acm-submission-with-ms-word/" target="_blank">Create an accessible ACM submission using Microsoft Word</a>.</p>
</div>
</div>
</div>
</section>
<section class="callout_section_0 p-3">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center">Making Accessible Figures and Tables</h3>
<ul>
<li><b>Do not add your figures as a pdf.</b> The tagging of figures that are in pdf can sometimes lead to undesired effects on the visual presentation. Instead, insert the image, for example, as png or svg.</li>
<li><b>Do not add your tables as images.</b></li>
<li><b>Give your tables lines/borders.</b>This can facilitate the tagging of the document.</li>
</ul>
</div>
</div>
</div>
</section>
<!-- Creating Accessible Video Figures -->
<section class="callout_section_1 p-3" id="a11y-videos">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center">Creating Accessible Video Figures and Video Presentations</h2>
<p>Video figures and video presentations, like papers, must be accessible. For videos to be accessible, include both audio narration (so that the contents of the video can be understood by someone with a visual impairment) as well as text captions (so that the video can be understood by someone who is deaf or hard of hearing). Please do <b>NOT</b> burn text captions directly into your <b>video presentations</b>. Instead, you will upload a separate closed-captioning files with your video presentation.</p>
<p>You can create closed-captioning files manually with a text editor, or use an online tool like <a href="https://flixier.com/tools/online-subtitle-editor">Flixier</a> or <a href="https://www.rev.com/blog/resources/what-is-an-srt-file-format-create-use-srt-files">Rev</a>. If you have access to <a href="https://helpx.adobe.com/premiere-pro/using/working-with-captions.html">Adobe Premiere</a>, it can auto-add captions based on speech-to-text, which you can then modify and export as .srt or .vtt. You can also download auto-generated captions from <a href="https://support.zoom.us/hc/en-us/articles/207279736-Managing-closed-captioning-and-live-transcription">Zoom</a> or <a href="https://support.google.com/youtube/answer/6373554?hl=en">YouTube</a> and then manually modify the content, or <a href="https://support.google.com/youtube/answer/2734796#zippy=%2Cauto-sync">auto-sync</a> your script with YouTube and then download the .srt or .vtt file.</p>
<p><a href="https://dcmp.org/learn/captioningkey/600">This guide on language mechanics for captioning</a> from the <a href="https://dcmp.org/">Described and Captioned Media Program</a> can also be a helpful resource.</p>
</div>
</div>
</div>
</section>
<!-- Making Accessible Presentations -->
<section class="callout_section_0 p-3">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center">Making Accessible Presentations</h2>
<p>Presenters are responsible for making their presentations accessible to the diverse attendees at the conference. For instance, there will be ASL interpreters during the conference for people who use sign language, and there will be attendees in the audience who are blind or who have low vision.</p>
<p>As a resource to our community, <a href="http://homepage.cs.uiowa.edu/~krector/">Kyle Rector</a> has prepared a wonderful and concise guide about how to make your presentation accessible, along with a video: <a href="http://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-presentation-guide/">Accessible Presentation Guide</a>. Please ensure that your presentation incorporates the recommendations from this guide.</p>
</div>
</div>
</div>
</section>
<!-- Other Useful Links -->
<section class="callout_section_1 p-3" id="external-links">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center">Other Useful Links</h2>
<ul>
<li><a target="_blank" href="http://interactions.acm.org/archive/view/november-december-2015/writing-about-accessibility" role="menuitem">Writing Guidelines <i class="fas fa-external-link-alt"></i></a></li>
<li><a target="_blank" href="https://www.acm.org/publications/policies" role="menuitem">ACM Policies <i class="fas fa-external-link-alt"></i></a></li>
<li><a target="_blank" href="https://www.sigaccess.org/welcome-to-sigaccess/resources/conflict-of-interest/" role="menuitem">Conflict of Interest <i class="fas fa-external-link-alt"></i></a></li>
</ul>
</div>
</div>
</div>
</section>
<div id="footer"></div>
<script>
$(function(){
$("#footer").load("footer.html");
});
</script>
</div>
<!-- Content -->
</main>
<script src="./assets/dist/js/bootstrap.bundle.min.js"></script>
</body>
</html>