-
Notifications
You must be signed in to change notification settings - Fork 1
/
talks.html
285 lines (249 loc) · 14.3 KB
/
talks.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
<!DOCTYPE html>
<html lang="en">
<head>
<title>Accessibility Camp Tour 2018</title>
<meta charset="utf-8">
<meta name = "format-detection" content = "telephone=no" />
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
<link rel="icon" href="favicon.ico" type="image/x-icon">
<!--link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css" integrity="sha384-Gn5384xqQ1aoWXA+058RXPxPg6fy4IWvTNh0E263XmFcJlSAwiGgFAW/dAiS6JXm" crossorigin="anonymous"-->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css" integrity="sha384-Gn5384xqQ1aoWXA+058RXPxPg6fy4IWvTNh0E263XmFcJlSAwiGgFAW/dAiS6JXm" crossorigin="anonymous">
<!--[if (gt IE 9)|!(IE)]><!-->
<!--[if (gt IE 9)|!(IE)]><!-->
<style>
div.intro {
margin-left: 30px;
}
h1,h2 {
color: #09477B;
}
h1 {
margin-top: 10px;
}
a.btn-primary {
background-color: #09477B;
}
ul.sponsor {
list-style-type: none;
margin-top: 5px;
padding: 0;
}
li.sponsor {
display: inline;
padding: 15px;
}
</style>
</head>
<body>
<section>
<div class="container p-2">
<h1>Talks</h1>
<div class="row">
<div class="col-sm-6 mb-2">
<div class="card">
<h2 class="card-header">Introduction to web accessibility</h2>
<div class="card-body">
<div class="card-text">
By: Nic Steenhout <br>
at Ottawa</p>
<p>You'll have heard about the importance of web accessibility. But what exactly is it? Who's affected by it? Why is it important and why should your site be accessible? And if you're a developer, why should you ensure the accessibility of the sites you create for your clients?</p>
<p>And once that's understood, what does an accessible site look like? Should we forget design and do a "text-only"site? Can we use JavaScript? We'll explore base concepts to ensure a site's accessibility.</p>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="card">
<span lang="fr">
<h2 class="card-header">L'accessibilité Web, ça mange quoi en hiver?</h2>
<div class="card-body">
<div class="card-text">
Par: Nic Steenhout<br>
à Montréal</p>
<p>Vous aurez probablement entendu parler de l'importance de l'accessibilité web. Mais c'est quoi, ça, au juste? Ça touche qui? Pourquoi est-ce important, et pourquoi votre site devrait-il être accessible? Et si vous êtes dévelopeur, pourquoi devriez-vous assurer l'accessibilité des sites que vous créez pour vos clients?</p>
<p>Mais une fois que c'est compris, de quoi ça a l'air, un site accessible? Est-ce qu'on doit oublier tout design et aller sur un site "texte seulement"? Peut-on garder un peu de JavaScript? Nous explorerons quelques concepts de base pour assurer l'accessibilité d'un site.</p>
</div>
</div>
</span>
</div>
</div>
</div>
<br>
<div class="card">
<h2 class="card-header">What's new in WCAG 2.1</h2>
<div class="card-body">
<div class="card-text">
<p>By: David MacDonald<br>
at Ottawa and Montreal</p>
<p>In this talk we'll go over the new Success Criteria in the WCAG 2.1 and learn about passive vs. active Success Criteria with David MacDonald, a veteran member of the team that wrote the standard.</p>
</div>
</div>
</div>
<br>
<div class="row">
<div class="col-sm-6 mb-2">
<div class="card">
<h2 class="card-header">Using SEO to get started with accessibility</h2>
<div class="card-body">
<div class="card-text">
<p>By: Myriam Jessier <br>
at Ottawa</p>
<p>Accessibility can sometimes sound like a New Year's resolution. Something we care deeply about but somehow, one month into our efforts, things start to slip. Why? Because let's be honest, sometimes, things can get hairy, scary or simply too complicated to handle.</p>
<p>Search engine optimization (SEO) is one of the digital marketing skills that can help you achieve quick results when it comes to accessibility. Let's go over some tips, tricks and tools that SEO experts use in their work everyday to help them optimize websites. </p>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="card">
<span lang="fr">
<h2 class="card-header">SEO French</h2>
<div class="card-body">
<div class="card-text">
<p>Par: Myriam Jessier<br>
à Montréal</p>
<p>French</p>
</div>
</div>
</span>
</div>
</div>
</div>
<br>
<div class="card">
<h2 class="card-header">Accessibility Testing Using Screen Readers</h2>
<div class="card-body">
<div class="card-text">
<p>By: Rabab Gomaa <br>
at Ottawa and Montreal</p>
<p>Testing websites using screen readers gives web developers the opportunity to make a real evaluation of their code and help identify accessibility issues that could be missed in manual checkup, or neglected by automatic verification tools. In this session we will demonstrate how blind people navigate the web and will show how to use screen readers for accessibility testing of web pages including interactive components and web forms.</p>
<p>At the end of the session, you will be able to:
<ul>
<li>Experience what it is like to use a screen reader</li>
<li>Identify challenges that screen reader users may face when navigating web pages and interacting with web forms</li>
<li>Apply practical screen reader techniques to test web pages and web forms</li>
</ul>
</div>
</div>
</div>
<br>
<div class="row">
<div class="col-sm-6 mb-2">
<div class="card">
<h2 class="card-header">accessibility in the age of artificial intelligence</h2>
<div class="card-body">
<div class="card-text">
<p>By: Denis Boudreau<br>
at Ottawa</p>
<p>The promises of artificial intelligence-based technologies are drastically changing not only the way in which we develop the Web, but also the way millions of people with disabilities and people over the age of 65 around the World interact with it, and evolve in the digital landscape. Automated text equivalents based on deep learning and conversational interfaces are but the tip of an iceberg of innovations on track to radically change the face of accessibility as we know it. These changes will also affect our interactions in the real world: self-driving cars, intelligent personal assistants, innovative wheelchairs and instant translation interfaces represent a tiny portion of the innovations that have already begun contributing to breaking down barriers for people with disabilities – and by extension, break down barriers for all humans. What might the impact of these technologies be for the various trades of the Web? How can these innovations benefit the whole of humanity? That is another angle we propose to explore, to give a sense of perspective into the revolution that is about to take us by storm. Together, let’s glimpse into a future that may be much closer than we think. Will you join us?</p>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="card">
<span lang="fr">
<h2 class="card-header">L’accessibilité à l'ère de l'intelligence artificielle</h2>
<div class="card-body">
<div class="card-text">
<p>Par: Denis Boudreau<br>
à Montréal</p>
<p>Les promesses des technologies basées sur l'intelligence artificielle modifient radicalement non seulement la façon dont nous développons le Web, mais aussi la façon dont des millions de personnes handicapées et de plus de 65 ans interagissent avec le monde, et évoluent dans le numérique. paysage. Les équivalents textuels automatisés basés sur le deep learning et les interfaces conversationnelles ne sont que la pointe d'un iceberg d'innovations en voie de changer radicalement le visage de l'accessibilité tel que nous le connaissons. Ces changements affecteront également nos interactions dans le monde réel: les voitures autonomes, les assistants personnels intelligents, les fauteuils roulants innovants et les interfaces de traduction instantanées représentent une infime partie des innovations qui ont déjà commencé à contribuer à faire tomber les barrières pour les personnes handicapées. Et par extension, abattre les barrières pour tous les humains. Quel pourrait être l'impact de ces technologies sur les différents métiers du Web? Comment ces innovations peuvent-elles bénéficier à l'ensemble de l'humanité? C'est un autre angle que nous proposons d'explorer, pour donner un sens de perspective à la révolution qui est sur le point de nous prendre d'assaut. Ensemble, jetons un coup d'œil sur un avenir qui pourrait être beaucoup plus proche que nous le pensons. Serez-vous des nôtres?</p>
</div>
</div>
</span>
</div>
</div>
</div>
<br>
<div class="card">
<h2 class="card-header">Creating accessible React apps</h2>
<div class="card-body">
<div class="card-text">
<p>By: Scott Vinkle <br>
at Ottawa and Montreal</p>
<p>React is a great way to create reusable, modular components that can be shared among projects. But how do you ensure your React apps are usable by all? Scott Vinkle will share tips on how to build your React apps with accessibility baked-in!</p>
</div>
</div>
</div>
<br>
<div class="card">
<h2 class="card-header">Draggable/Accessible</h2>
<div class="card-body">
<div class="card-text">
<p>By: Curtis Dulmage and Max Hoffman <br>
at Ottawa and Montreal</p>
<p>...</p>
</div>
</div>
</div>
<br>
<div class="card">
<span lang="fra">
<h2 class="card-header">AMI</h2>
<div class="card-body">
<div class="card-text">
<p>Par: Isabella Federigi <br>
à Montréal</p>
<p>...</p>
</div>
</div>
</span>
</div>
<br>
<div class="card">
<h2 class="card-header">Don’t Forget the Simple Things – MS Word and PDF</h2>
<div class="card-body">
<div class="card-text">
<p>By: Logan Trafford<br>
at Ottawa only</p>
<p>While technological advancements and coding enhancements allow us to create accessible, dynamic applications and websites, it is quite often the simplest elements that create barriers for users. Logan will examine some of the simple elements in MS Word documents, that help lead to the creation of an accessible PDF.</p>
</div>
</div>
</div>
<br>
<div class="row">
<div class="col-sm-6 mb-2">
<div class="card">
<h2 class="card-header">Closing notes</h2>
<div class="card-body">
<div class="card-text">
<p>By: Daniel Gervais <br>
at Ottawa</p>
<p>...</p>
</div>
</div>
</div>
</div>
<div class="col-sm-6">
<div class="card">
<span lang="fr">
<h2 class="card-header">Closing notes French</h2>
<div class="card-body">
<div class="card-text">
<p>Par: Daniel Gervais<br>
à Montréal</p>
<p>French</p>
</div>
</div>
</span>
</div>
</div>
</div>
</div>
</section>
<footer>
<div class="text-center">
<hr>
<h2>Sponsors and supporters</h2>
<ul class="list-unstyled list-inline pt-3 pb-3">
<li class="list-inline-item mr-5 mb-3 pb-3"><a href="https://www.deque.com/"><img src="img/deque.png" alt="Deque"></a></li>
<li class="list-inline-item mb-3 pb-3"><a href="http://www.ami.ca/"><img src="img/ami.png" alt="AMI Accessible Media inc"></a></li>
<li><a href="https://carleton.ca/read/"><img src="img/read.jpg" alt="READ Initiative"></a></li>
<li class="list-inline-item mr-5 mb-3 pb-3"><a href="https://www.meetup.com/a11yOttawa/"><img src="img/a11yyow.png" alt="Ottawa Digital Accessibility and Inclusive Design"></a></li>
<li class="list-inline-item mb-3 pb-3"><a href="https://www.meetup.com/a11yMTL"><img src="img/a11ymtl.png" alt="a11yMTL meetup - web accessibility and inclusive design"></a></li>
</ul>
</div>
</footer>
</body>
</html>