forked from ASSETS-Conference/assets2023
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathexperience_reports.html
304 lines (279 loc) · 14.2 KB
/
experience_reports.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
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Experience Reports / ASSETS 2025</title>
<meta
name="description"
content="The 27th International ACM SIGACCESS Conference on Computers and Accessibility"
/>
<meta name="keywords" content="Accessibility, Technology, Conference, Assets 2025" />
<meta name="author" content="ACM SIGACCESS" />
<link rel="icon" href="favicon.svg" type="image/svg+xml" />
<!-- Preload stylesheets -->
<link rel="preload" href="reset.css" as="style" />
<link rel="preload" href="styles.css" as="style" />
<!-- Load stylesheets -->
<link rel="stylesheet" href="reset.css" />
<link rel="stylesheet" href="styles.css" />
<link rel="preload" href="setup.js" as="script" />
<script src="setup.js" defer></script>
</head>
<body>
<nav id="nav-container" data-active="authors"></nav>
<main class="content-block-container">
<div class="grid-helper">
<div class="text-block">
<h1>Experience Reports</h1>
<p>
Research on accessible and assistive technologies is primarily motivated by the needs of
people with disabilities and other stakeholders. Understanding these needs is crucial
but often requires first-hand experience that might be unavailable to all researchers in
the community. ASSETS 2025 invites Experience Report track submissions that reflect
people’s experiences with disabilities and the challenges and opportunities related to
accessible and assistive technologies. These reports will be reflective in nature and
will give authors an opportunity to share their experiences as people with disabilities,
caregivers, rehabilitation professionals, educators, researchers, developers,
entrepreneurs, or other stakeholders.
</p>
<p>
Experience report submissions should clearly explain how the research community will
benefit from the reported experience. When applicable, the focus of the report should be
described, including the citation of appropriate references. Potential topics include
but are not limited to:
</p>
<ul>
<li>Accessibility challenges or solutions with existing technology;</li>
<li>Everyday problems for which effective assistive technologies do not yet exist;</li>
<li>Barriers to accessing technologies due to costs, cultural aspects, etc.;</li>
<li>
Challenges or solutions in the development and distribution of accessible and
assistive technologies;
</li>
<li>Recommendations for technologies which leverage best practices;</li>
<li>
Requirements of specific communities, such as people with multiple disabilities,
children with disabilities, or older adults;
</li>
<li>
Challenges or solutions related to conducting research in an accessible and equitable
manner;
</li>
<li>Challenges or solutions related to regulatory policies;</li>
<li>
Challenges or solutions arising in the field of accessibility and computing education;
</li>
<li>
Challenges or solutions of tools and methodologies in the field of education of people
with disabilities;
</li>
<li>Other topics relevant to the ASSETS conference</li>
</ul>
<p>
We encourage authors to not be constrained by the technical paper format, and offer
authors the chance to submit their work in the form of a pictorial.
</p>
<p>
We have curated a few examples of past experience reports that fit within the scope of
the track:
</p>
<ul>
<li>
<a href="https://dl.acm.org/doi/10.1145/3517428.3551351" target="_blank"
>It's Enactment Time!: High-fidelity Enactment Stage for Accessible Automated
Driving System Technology Research</a
>
</li>
<li>
<a href="https://dl.acm.org/doi/abs/10.1145/3441852.3476473" target="_blank"
>Lost in Translation: Challenges and Barriers to Sign Language-Accessible User
Research</a
>
</li>
<li>
<a href="https://dl.acm.org/doi/10.1145/3517428.3551356" target="_blank"
>Performing Qualitative Data Analysis as a Blind Researcher: Challenges, Workarounds
and Design Recommendations</a
>
</li>
<li>
<a href="https://dl.acm.org/doi/10.1145/3373625.3418011" target="_blank"
>Putting Tools in Hands: Designing Curriculum for a Nonvisual Soldering Workshop</a
>
</li>
</ul>
<p>Experience reports are not:</p>
<ul>
<li>
Personal accounts written under pressure. Although experience reports are an
appropriate track for people to consensually share personal experiences, it is not a
track for senior mentors to pressure students with disabilities and/or other
minoritized identities to share experiences they do not want to share.
</li>
<li>
Works in progress. If the work you are considering submitting would qualify for the
posters and demos track, please submit it there. The experience reports track is meant
to bring out knowledge that is not highlighted by other tracks. We understand the line
can be thin; for example, someone sharing reflections on conducting a particular type
of research study in an accessible manner may also publish a case study or technical
paper reporting an evaluation of their accessible study design. Similarly, reflexive
thematic analysis and other techniques recognize the researcher’s positionality in a
similar way that experience reports are meant to foreground lived experience. However,
reviewers will evaluate submissions according to how they uniquely fit within the
experience reports track.
</li>
</ul>
<h2>Important Dates</h2>
<p>All deadlines are 11:59 P.M. Anywhere on Earth (UTC -12:00).</p>
<ul>
<li>Wednesday, June 11, 2025 – Experience Reports Submission Deadline</li>
<li>Wednesday, July 9, 2025 – Notification of Acceptance</li>
<li>
Wednesday, July 16, 2025 – Final versions of Experience Reports due. Following this
deadline, authors will receive instructions for completing their eRights forms,
validating and submitting their paper to TAPS, and submitting their final accessible
PDF.
</li>
<li>Wednesday, July 23, 2025 – Video Presentations Submission Deadline</li>
</ul>
<h2>Submission Guidelines</h2>
<p>
ASSETS uses
<a
href="https://authors.acm.org/proceedings/production-information/taps-production-workflow"
target="_blank"
>the ACM Publication System (TAPS) process</a
>
to generate final multi-format representations of accepted papers.
</p>
<p>
The correct template for submission is: single-column
<a
href="https://authors.acm.org/proceedings/production-information/preparing-your-article-with-microsoft-word"
target="_blank"
>Word Submission Template</a
>
and
<a
href="https://authors.acm.org/proceedings/production-information/preparing-your-article-with-latex"
target="_blank"
>single-column LaTeX</a
>
(using “manuscript” style available in the template). You may also choose to use
<a
href="https://authors.acm.org/proceedings/production-information/overleaf"
target="_blank"
>Overleaf</a
>.
</p>
<p>
Experience Reports proposals are limited to 8 pages in the single-column submission
format, and references do not count toward page limits. Submissions are NOT
double-anonymized: the authors' names should be on the paper.
</p>
<p>
<a
href="https://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-writing-guide/"
target="_blank"
>Writing Guidelines</a
>
are available to help authors choose appropriate language for writing about technology
and people with disabilities. Particularly for Experience Reports, when discussing their
own experiences of disability, authors are encouraged to use their preferred language to
describe their disability identity.
</p>
<p>
All submissions will be peer-reviewed by an international panel, per the ASSETS policy
on Program Committees.
</p>
<p>Accepted Experience Reports will be published in the conference proceedings.</p>
<h2>Accessible Submissions</h2>
<p>
Your PDF submission must be accessible. It may take several hours to make your PDF file
accessible (adding alt tags, etc.), so be sure to leave time before the submission
deadline to do so. Please refer to the
<a
href="https://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-pdf-author-guide/"
target="_blank"
>instructions on creating an accessible ACM conference paper information</a
>
on how to accomplish this.
</p>
<p>
It is expected that experience reports will be made accessible both at the time of
review and for the final submission.
<strong>Submissions that are not accessible will be desk rejected.</strong> If you have
questions about making your workshop or demonstration submission accessible, please
contact the Accessibility Chairs at
<a href="mailto:access-assets25@acm.org">access-assets25@acm.org</a>.
</p>
<h2>Authorship Guidelines</h2>
<p>
The ACM Publications Board has recently updated the ACM Authorship Policy in several
ways:
</p>
<ul>
<li>Addressing the use of generative AI systems in the publications process</li>
<li>Clarifying criteria for authorship and the responsibilities of authors</li>
<li>Defining prohibited behavior, such as gift, ghost, or purchased authorship</li>
<li>
Providing a linked FAQ explaining the rationale for the policy and providing
additional details
</li>
</ul>
<p>
Please read the updated policy at
<a
href="https://www.acm.org/publications/policies/new-acm-policy-on-authorship"
target="_blank"
>https://www.acm.org/publications/policies/new-acm-policy-on-authorship</a
>
and ensure your submission adheres to it.
</p>
<h2>How to Submit</h2>
<p>
The submission deadline is Wednesday, June 11, 2025, 11:59 P.M. Anywhere on Earth (UTC
-12:00). Please submit via the ASSETS 2025 Experience Reports submissions site.
</p>
<h3>Important-Author PCS Account Requirements</h3>
<p>
ACM continues to update the publication process. Currently, paper metadata will be
pulled directly from your personal PCS account. This means that it is crucial for you
and all of your co-authors to update the contact information so that names,
affiliations, AND primary email addresses are stylized precisely in the way that you all
would want to see them in the ACM digital library and on your paper. For example, if you
use a personal email address (xyz123@hotmail.com) as your primary contact email in PCS
then this email will appear on your paper. Please check your author information and make
the necessary changes.
</p>
<h2>Further Information</h2>
<p>
By submitting your article to an ACM Publication, you are hereby acknowledging that you
and your co-authors are subject to all ACM Publications Policies, including ACM's new
Publications Policy on Research Involving Human Participants and Subjects. Alleged
violations of this policy or any ACM Publications Policy will be investigated by ACM and
may result in a full retraction of your paper, in addition to other potential penalties,
as per ACM Publications Policy.
</p>
<p>
Please ensure that you and your co-authors obtain an ORCID ID, so you can complete the
publishing process for your accepted paper. ACM has been involved in ORCID from the
start and we have recently made a commitment to collect ORCID IDs from all of our
published authors. We are committed to improving author discoverability, ensuring proper
attribution and contributing to ongoing community efforts around name normalization;
your ORCID ID will help in these efforts.
</p>
<p>
For further information or any questions regarding the event or submissions, please
contact the Experience Report Chairs Amy Hurst and Lauren Race at
<a href="mailto:experience-reports-assets25@acm.org"
>experience-reports-assets25@acm.org</a
>.
</p>
</div>
</div>
</main>
<div id="footer-container"></div>
</body>
</html>