-
Notifications
You must be signed in to change notification settings - Fork 1
/
workshops.html
356 lines (327 loc) · 24.2 KB
/
workshops.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
<!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 2022 official website | Workshops">
<meta name="keywords" content="ASSETS 2022, ASSETS'22, SIGACCESS, Workshops, workshop">
<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 2022 | Call for Workshop Proposals" />
<meta name="image" property="og:image"
content="https://assets22.sigaccess.org/assets/img/large/ASSETS2022_Logo.png" />
<meta name="og:title"
content="ASSETS 2022 | The 24th International ACM SIGACCESS Conference on Computers and Accessibility" />
<meta name="og:image" content="https://assets22.sigaccess.org/assets/img/large/ASSETS2022_Logo.png" />
<title>ASSETS 2022 | Call for Workshop Proposals</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">
<img class="d-block my-0 mx-4" src="./assets/img/large/logo-large.png" alt="ASSETS'22 logo"
width="125">
<div>
<h1 class="display-6 confTitle mt-4 mb-0">Call For Workshop Proposals</h1>
<h5 class="confTitle">October 23-26, 2022</h5>
</div>
</span>
</div>
</div>
<!-- Jumbotron -->
<!-- Content -->
<section class="callout_section_2 p-3">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<p>We invite you to submit a proposal for workshops at ASSETS 2022. Workshops will bring
together attendees with shared interests to meet in the context of a focused and
interactive discussion. ASSETS workshops should include topics relevant to the ASSETS
community, including design, systems, tools, scientific understanding, methodology, or
social issues relevant to and including people with disabilities or older adults. It may
also focus on enabling technologies, technology use by people with disabilities,
disability justice, legal and policy issues, or accessibility in computing education.
Each workshop should generate ideas that will suggest promising directions for future
work for the ASSETS community. If you are working in an emerging area in accessibility,
please consider organizing a workshop.</p>
</div>
</div>
</div>
</section>
<section id="dates" 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" tabindex="0">Important Dates</h3>
<p><b>All deadlines are 5 P.M. Pacific Time (GMT -8:00).</b></p>
<ul>
<li><strike><b>Thursday, June 23, 2022</b> – Submission deadline</strike></li>
<li><strike><b>June 24 - July 8, 2022</b> – Open discussion (via PCS)</strike></li>
<li><strike><b>Friday, July 15, 2022</b> – Notification of acceptance</strike></li>
<li><strike><b>Friday, July 29, 2022</b> – Workshop website online</strike></li>
<li><strike><b>Friday, July 29, 2022 </b> – Camera-ready deadline</strike> </li>
<li><b>Week of Oct 17th</b> – ASSETS'22 Workshops (see <a href="accepted-workshops.html">Accepted Workshops page</a>) </li>
</ul>
Following the camera-ready deadline, workshop organizers will receive instructions for completing their
eRights forms, validating and submitting their final workshop proposal to TAPS, and
submitting their final accessible pdf.</li>
</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" tabindex="0">Workshop Format</h3>
<p>Workshops will be an online only event and take place the <b>week of Oct 17th</b> or on <b>October 23</b>. Please note
that workshops <u>will not</u> have a physical space at the conference.</p>
<p>Please see the <a href="workshops.html#suggestions">Suggestions</a> sections for more
details on how you might plan your workshop.</p>
<!-- <p>To help reduce videoconferencing exhaustion and to broaden participation, we encourage organizers to think creatively and inclusively to make the workshops interactive. Workshop organizers may consider supporting offline activities ahead of / during the workshop (such as sending design kits to participants). Organizers may also want to consider tasks and activity design where attendees might be co-located (<i>e.g.,</i> a workshop that connects multiple research groups) and could physically work together prior to joining the online workshop event.</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" tabindex="0">Preparing and Submitting your Workshop Proposal</h3>
<p>A workshop proposal must be prepared according to the <a
href="submission-templates.html">ACM Master Article Submission Templates (single
column)</a>. It must be submitted via the PCS Submission System as a single PDF
file. The proposal must be no more than 6,000 words (excluding references) and have the
following structure:</p>
<ul>
<li><b>Background:</b> Provide a strong rationale for the workshop, describe the issues
to be addressed, and state concrete goals for the workshop.</li>
<li><b>Workshop Plans:</b> Explain in detail the workshop structure, including
activities, timing, resources, and any follow-up activities or tangible outcomes.
Please note that there is no on-site space provided. Please provide details
regarding what specific technical capacity will be necessary to support the online
workshop day.</li>
<li><b>Diversity and inclusion considerations:</b> Please elaborate on how you plan to
promote diversity and how you would create an inclusive environment at the workshop.
</li>
<li><b>Organizers:</b> Present the organizers’ backgrounds, including the main contact
person.</li>
<li><b>Website:</b> Provide details of the planned website, including the URL. (This may
be TBD until after acceptance).</li>
<li><b>Pre-Workshop Plans:</b> Please provide plans for how participants will be made
aware of the workshop and how you will encourage community-building (<i>e.g.,</i>
through a website or other communication with participants).</li>
<li><b>Call for Participation:</b> Provide a 250-word Call for Participation that will
be posted on the conference site to recruit participants for your workshop. This
should appear at the end of your workshop proposal, and should include the
following:
<ul>
<li>The goals of the workshop</li>
<li>The participant selection criteria</li>
<li>Requirements for position papers (<i>e.g.,</i> topics to address, page
length, format) or workshop artifact </li>
<li>Where these position papers or workshop artifacts should be submitted</li>
<li>The requirement that at least one author of each accepted position paper or
workshop artifact must attend the workshop and that all participants must
register for workshop</li>
<li>A link to the workshop website. (This may be TBD until after acceptance)
</li>
</ul>
</li>
<li><b>References:</b> References are not included within the word limit.</li>
</ul>
<p>This proposal is the only document from the workshop which will be included in the ASSETS
Extended Abstracts proceedings. Any position paper or other material submitted by
workshop participants are not included but may be distributed through avenues like the
workshop website. The workshop organizers may also consider submitting an actionable
summary or lessons learned-type of report after the workshop to <a
href="https://www.sigaccess.org/category/news/newsletter/" target="_blank">SIGACCESS
newsletter</a>.</p>
</div>
</div>
</div>
</section>
<section class="callout_section_2 p-3" id="suggestions">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center" tabindex="0">Suggestions for planning your inclusive online workshop
</h3>
<p>To help reduce videoconferencing exhaustion and to broaden participation, we encourage
organizers to think creatively and inclusively to make the workshops interactive.
Workshop organizers may consider supporting offline activities ahead of / during the
workshop (such as sending design kits to participants). Organizers may also want to
consider tasks and activity design where attendees might be co-located (<i>e.g.,</i> a
workshop that connects multiple research groups) and could physically work together
prior to joining the online workshop event.</p>
<p>While traditionally at in-person workshops we would often work for upto 8 hours at a
time, in online workshops we recommend that you reduce the length of time that your
participants will be on the video call and opt for shorter, more interactive activities.
</p>
<p>We expect to have participants from all around the world, as such it is vital that you
plan your workshop to accommodate participants joining from a number of timezones. You
might consider more break out asynchronous activities that participants can do on their
own, complemented with shorter synchronous interactions where participants get together
and discuss.</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" tabindex="0">Workshop Selection Process</h3>
<p>We would like the ASSETS community to guide and shape the workshops that will be included
in the conference. As such, ASSETS Workshop track will follow an open review and then a
Juried review process.</p>
<p>During the period between submissions and notifications researchers and practitioners who
work in the areas of accessibility, disability and computing will be invited to comment
and discuss the workshop proposal submissions within a reviewer forum via PCS in a
non-anonymous format <sup style="color: #e84949;">*</sup>. Authors will also be
encouraged to invite relevant members (such as potential attendees) to review the
proposal and provide feedback. Such discussion and feedback we hope will give the
authors an opportunity to refine and adapt their workshop plans (if they choose) to
ultimately create a successful workshop.</p>
<p>After the discussion period, the final selection will be curated by the workshops chairs
based on the following assessment criteria:</p>
<ul>
<li>Does the workshop foster community-building and look to broaden diversity in the
ASSETS community?</li>
<li>Alignment of the workshop topic with the interests of the ASSETS community.</li>
<li>Workshops potential to generate discussion on new directions of future work by the
ASSETS community.</li>
<li>Level of engagement and proposed interactivity in the workshop. For workshop
proposals of comparable quality, preference will be given to workshops containing
discussion, interactive sessions and a diverse organization team. </li>
</ul>
<p style="color: #e84949;">* all reviewers will be required to consent to a review agreement
prior to participating in the selection process. </p>
</div>
</div>
</div>
</section>
<section class="callout_section_2 p-3">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center" tabindex="0">Reviewing for Workshops</h3>
<ol>
<li>Interested reviewers must volunteer to review for the ASSETS 2022 Workshops Track
via PCS. Visit the <a href="https://new.precisionconference.com/review_volunteering"
target="_blank">PCS volunteer page</a>.</li>
<li>You will then have access to the bidding page and see a list of all available titles
and abstracts. For any you wish to review, please select “want” or “willing”. You
can bid on more workshop proposals at any time during the review period, and can
deselect reviews if you change your mind.</li>
<li>You will have access to the submissions, discussions and reviews through your <a
href="https://new.precisionconference.com/reviews" target="_blank">reviewing
page</a>.</li>
<li>Reviewers and authors are encouraged to actively engage in discussions about their
workshop proposals throughout the reviewing process.</li>
</ol>
</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" tabindex="0">Responsibility of Workshop Organizers: Upon Acceptance
of Workshop Proposals and Before the Workshop Day</h3>
<p>Workshop organizers upon receiving notification of acceptance, must prepare to fulfill
the following responsibilities prior to the workshop day:</p>
<ul>
<li><b>Set up a website:</b> Organizers of an accepted workshop must set up and maintain
a website with information about their workshop (deadlines, CfP, programme,
templates, accepted papers/participants, organizers,<i>etc.</i>). We will include
the link to the workshop’s page on the official ASSETS workshop site.</li>
<li><b>Advertise your workshop:</b> Share your call for participants within your
professional network. Accepted workshops will also be listed on the ASSETS’22 web
page.</li>
<li><b>Collect position papers or workshop artifacts:</b> From potential participants
(depending on how the organizers run the workshop). A position paper can be a 2-4
pages document. An artifact can be a video or images of physical objects that
outlines the submitter’s view on the workshop theme and the reasons for the
submitter’s interest in the topic.</li>
<li><b>Set up a review process:</b> Select participants accordingly. We expect workshops
to target a minimum number of 10 participants.</li>
<li><b>Plan for pre-workshop activities:</b> If applicable, share and distribute any
pre-workshop materials (<i>e.g.,</i> design kits) to participants in advance of the
workshop.</li>
<li><b>Distribute:</b> Share accepted position papers or workshop artifacts. This will
help participants to familiarize themselves with workshop content and encourage more
in-depth discussions.</li>
<li>Ensure the workshop organizers and participants are aware of <a
href="https://www.acm.org/code-of-ethics" target="_blank">the ACM Code of Ethics
and Professional Conduct</a>.</li>
</ul>
</div>
</div>
</div>
</section>
<section class="callout_section_2 p-3">
<div class="container">
<div class="row justify-content-md-center">
<div class="col-lg-8 mt-4">
<h3 class="text-center" tabindex="0">Registration for Workshops</h3>
<p><b>Workshop Organizers:</b> All organizers who plan to attend the workshop must register for the workshop and at least one organizer must register for the entire conference.</p>
<p><b>Workshop Attendees:</b> Must register for the workshop they are attending.</p>
<p><b>Registration fee:</b> Workshop registration fees can be found on the <a href="registration.html">registration page</a> – attendees do not need to
register for the conference to attend the workshops.</p>
<p>For further information or any questions regarding workshop submissions, please contact
the Workshop Chairs – Sowmya Somanath and Kyle Montague at <a
href="mailto:[email protected]">[email protected]</a>.</p>
</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>