-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
executable file
·434 lines (407 loc) · 15.7 KB
/
index.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
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<title>Everyday Accessibility</title>
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/dylan.css" id="theme">
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.3.1/css/all.css" integrity="sha384-mzrmE5qonljUremFsqc01SB46JvROS7bZs3IO2EmfFsd15uHvIt+Y8vEf7N7fWAU"
crossorigin="anonymous">
<!-- Theme used for syntax highlighting of code -->
<link rel="stylesheet" href="lib/css/monokai-pro.css">
<!-- Printing and PDF exports -->
<script>
const link = document.createElement('link');
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match(/print-pdf/gi) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName('head')[0].appendChild(link);
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<div class="slides">
<!-- Introduction -->
<section>
<div class="grid-rows">
<div>
<img class="circle-img med-img" src="resources/me-500px.jpg" alt="" />
</div>
<h1>Dylan Sheffer</h1>
<ul class="flex-row content-center social">
<li><i class="fab fa-twitter"></i> @DylanSheffer</li>
<li><i class="fab fa-twitch"></i> DylanSheffer</li>
<li><i class="fab fa-slack"></i> DylanSheffer</li>
</ul>
</div>
</section>
<!-- Title -->
<section>
<div class="">
<h1>Everyday Accessibility</h1>
</div>
<aside class="notes">
The motivation behind this talk is to give developers the background and resources needed to create inclusive websites and applications.
</aside>
</section>
<section>
<h1>Overview</h1>
<ol>
<li class="fragment">What accessibility is and why it is important</li>
<li class="fragment">Foundational knowledge</li>
<li class="fragment">How assistive tech interprets a website</li>
<li class="fragment">Strategies for creating accessible page elements</li>
<li class="fragment">Basic Testing Methods</li>
</ol>
</section>
<section>
<section>
<div>
<h1>What is Accessibility?</h1>
</div>
</section>
<section>
<div>
<blockquote>Making your site usable by everybody regardless of ability.</blockquote>
<div class="flex-row justify-space-around">
<p class="fragment">Increase <br> Customer Pool</p>
<p class="fragment">No Lawsuits</p>
<p class="fragment">Better UX</p>
</div>
</div>
<aside class="notes">
Making your site usable for everyone has many benefits outside of creating a more inclusive experience.
<br>
There are also...
<ol>
<li>financial benefits from increasing potential customer base</li>
<li>removes the possibility of a lawsuit for discriminatory practices</li>
<li>increases the overall usability of your site</li>
</ol>
</aside>
</section>
</section>
<!-- Serious Section / Disclaimer -->
<section>
<section>
<h1>Real Talk</h1>
<aside class="notes">
Before I go any further, I wanted to talk about why it's critical we get accessibility right.
</aside>
</section>
<section>
<p class="large-text ">It is critical we do this right</p>
<aside class="notes">
<ul>
<li>A11y isn't something we can debate about doing like using the latest javascript framework or using a new programming pattern.</li>
<li>It is all of our responsibility, as developers, that we ensure the preservation of a fundamental human right. The access to information and self expression.</li>
<li>Remember that all of us are only an accident or a few years of age from needing assistive technology in order live an independent lifestyle.</li>
<li>So it's in all of our best interest to create an inclusive infrastructure for our increasingly digital lives.</li>
</ul>
</aside>
</section>
</section>
<!-- WCAG -->
<section>
<section>
<h1>WCAG</h1>
<p class="fragment"><strong>Web Content Accessibility Guidelines</strong></p>
<p class="fragment">The official guidelines published by the W3C on how to make the web accessible.</p>
<div class="fragment">
<div><img src="resources/webaim.png" alt="Web AIM Logo"></div>
<p><a href="https://webaim.org/standards/wcag/checklist">Web AIM's WCAG Checklist</a></p>
</div>
<aside class="notes">
The WCAG is a dense read and I think it's one of the reasons why developers are intimidated by accessibility.
<br>
<br>
If you're struggling understanding what the WCAG is saying checkout the website webaim.org. It has a more digestible checklist of the WCAG.
<br>
<br>
... The main idea of the WCAG is that we need to make our websites P.O.U.R
</aside>
</section>
<section>
<h2>P.O.U.R</h2>
<div class="flex-row justify-space-around">
<p class="fragment">Perceivable</p>
<p class="fragment">Operable</p>
<p class="fragment">Understandable</p>
<p class="fragment">Robust</p>
</div>
</section>
<section>
<h3>Perceivable</h3>
<p>
Available to the senses either through the browser or through assistive technologies.
</p>
<aside class="notes">
Mainly through vision and hearing.
Assistive technologies include screen readers, screen enlargers, audio captions, etc.
</aside>
</section>
<section>
<h3>Operable</h3>
<p>
Users can interact with all controls and interactive elements using either the mouse, keyboard, or an assistive device.
</p>
<aside class="notes">
</aside>
</section>
<section>
<h3>Understandable</h3>
<p>
Content is clear and limits confusion and ambiguity.
</p>
<aside class="notes">
This includes using explicit language for dialog actions, using simple language for content, and to not completely rely on metaphors like icons and changing colors for information.
</aside>
</section>
<section>
<h3>Robust</h3>
<p>
A wide range of technologies and devices can access the content.
</p>
<aside class="notes">
Our sites need to be robust enough to be used in various contexts such as screen readers, screen enlargers, switches, etc.
<br>
<br>
If you can verify that your site is P.O.U.R, then you likely don't have an accessibility issue.
</aside>
</section>
</section>
<!-- Types of Disabilities -->
<section>
<section>
<h1>Types of Disabilities</h1>
<div class="flex-row justify-space-around">
<p class="fragment">Motor</p>
<p class="fragment">Visual</p>
<p class="fragment">Auditory</p>
</div>
<br>
<br>
<div class="flex-row justify-space-around">
<p class="fragment">Cognitive</p>
<p class="fragment">Neurological</p>
<p class="fragment">Temporary</p>
</div>
<aside class="notes">
</aside>
</section>
</section>
<section>
<section>
<h1>How does assistive tech work with websites?</h1>
<p class="fragment">The browser scans the HTML code and creates both the DOM and the Accessibility Tree.</p>
</section>
<section>
<h2>Accessibility Tree</h2>
<div class="fragment">
<p>A tree representation of the webpage that contains all meta-data about every page element.</p>
<div>
<img src="./resources/a11y-tree.png" alt="Accessibility Tree of a form">
</div>
</div>
<aside class="notes">
Assistive tech reads the Accessibility Tree from top to bottom. This means that the order of content in your document matters a lot to assistive technology.
</aside>
</section>
<section>
<h3>What Assistive Tech Sees from the Tree</h3>
<div class="flex-row justify-space-around">
<p class="fragment">
Name
</p>
<p class="fragment">
State
</p>
<p class="fragment">
Role
</p>
<p class="fragment">
Value
</p>
</div>
</p>
<aside class="notes">
</aside>
</section>
<section>
<h2>WAI-ARIA</h2>
<div class="flex-row justify-space-around">
<blockquote class="fragment">
Web Accessibility Initiative - Accessible Rich Internet Applications
</blockquote>
</div>
<p class="fragment">Powerful tool that allows the developer to directly modify the accessibility tree.</p>
</p>
</section>
<section>
<h3>Number 1 Rule for using ARIA</h3>
<p class="fragment">No ARIA is better than Bad ARIA</p>
<p class="fragment">ARIA can modify an element's state, role, and properties, so using ARIA incorrectly misrepresents an element on a page.</p>
<br>
<p class="fragment"><i>Example:</i> Imagine a paragraph tag was styled to look like an input.</p>
</section>
</section>
<section>
<section>
<h1>Strategies for Building Accessible Page Elements</h1>
</section>
<section>
<h2>Use native HTML elements whenever possible</h2>
<div class="">
<p class="fragment">HTML is accessible by default and will have the proper semantics.</p>
</div>
</p>
<aside class="notes">
</aside>
</section>
<section>
<h3>Code Example - Custom Button vs Native Button</h3>
<aside class="notes">
https://codepen.io/dylansheffer/pen/qBWPGXG
</aside>
</section>
<section>
<h2>Consult the WAI-ARIA Authoring Practices first when you need to create a custom element</h2>
<br>
<a class="fragment" href="https://www.w3.org/TR/wai-aria-practices-1.1">W3C's guide on ARIA authoring</a>
</section>
<section>
<h2>Use Property Selectors Over Classes In CSS</h2>
<p class="fragment">It eliminates bloat from your HTML and clarifies your CSS.</p>
<div class="flex-row fragment">
<div class="">
<pre><code>
// Semantic Selectors
input:invalid,
[aria-invalid] {
border: 4px dotted #f64100;
}
</code></pre>
</div>
<div>
<pre><code>
// BEM Styled Class Selectors
input.input__invalid {
border: 4px dotted #f64100;
}
</code></pre>
</div>
</div>
</section>
<section>
<h2>Add Visually Hidden Markup</h2>
<p class="fragment">A lot of information is understood visually via context.</p>
<p class="fragment">Additional markup can be used to bridge that gap</p>
</section>
<section>
<h3>Code Example - Hidden Headings</h3>
<aside class="notes">https://www.dylansheffer.com/projects/dylansheffer.com/</aside>
</section>
</section>
<section>
<section>
<h1>Testing for Accessibility</h1>
</section>
<section>
<h2>Types of Testing</h2>
<p class="fragment">Automatic</p>
<p class="fragment">Manual</p>
</section>
<section>
<h2>Accessibility Insights By Microsoft</h2>
</section>
<section>
<h3>Demo</h3>
</section>
</section>
<section>
<h1>Thank You!</h1>
<br>
<p class="large-text fragment">Questions⁉</p>
</section>
<section>
<h1>Tools and Resources</h1>
<ul>
<li class="small-text"><a href="https://inclusive-components.design/">Heydon Pickering- Inclusive Components</a></li>
<li class="small-text"><a href="https://abookapart.com/products/accessibility-for-everyone">Laura Kalbag- Accessibility For Everyone</a></li>
<li class="small-text"><a href="https://webaim.org/">WebAIM - Excellent Guides and Articles</a></li>
<li class="small-text"><a href="https://www.deque.com/">Excellent Tools, webinars, guides, podcasts, etc</a></li>
<li class="small-text"><a href="https://www.youtube.com/watch?v=Ag3DMNbL_ig&list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g">A11y Cast with Rob Dodson</a></li>
<li class="small-text"><a href="https://developers.google.com/web/fundamentals/accessibility/">Google Developer Accessibility Docs</a></li>
<li class="small-text"><a href="https://ebay.gitbooks.io/oatmeal/content/">OATMEAL - EBay's Open Accessibility Guidelines</a></li>
<li class="small-text"><a href="https://a11yproject.com/checklist">A11y Project - Beginners Checklist</a></li>
<li class="small-text"><a href="https://www.deque.com/axe/">aXe Accessibility Audit Plugin</a></li>
<li class="small-text"><a href="https://squizlabs.github.io/HTML_CodeSniffer/">HTML Code Sniffer</a></li>
<li class="small-text"><a href="https://incl.ca/archives/">Part of a Whole Blog</a></li>
<li class="small-text"><a href="https://ui.reach.tech/">Reach - Accessible React Components</a></li>
<li class="small-text"><a href="https://bulbenergy.github.io/bulb-audit/">Bulb Audit - Open Sourced Professional A11y Audit</a></li>
<li class="small-text"><a href="http://colorsafe.co/">Color Safe - A11y Color Pallet Generator</a></li>
<li class="small-text"><a href="https://accessibility.18f.gov/">18f - A11y Guide</a></li>
<li class="small-text"><a href="http://chromelens.xyz/">Color Blindness Simulator for Chrome</a></li>
</ul>
</section>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>// More info https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
// The "normal" size of the presentation, aspect ratio will be preserved
// when the presentation is scaled to fit different resolutions. Can be
// specified using percentage units.
width: '100%',
height: '100%',
// Factor of the display size that should remain empty around the content
margin: 0.1,
// Bounds for smallest/largest possible scale to apply to content
// minScale: 1,
// maxScale: 1,
// More info https://github.com/hakimel/reveal.js#dependencies
dependencies: [
{
src: 'lib/js/classList.js',
condition() {
return !document.body.classList;
},
},
{
src: 'plugin/markdown/marked.js',
condition() {
return !!document.querySelector('[data-markdown]');
},
},
{
src: 'plugin/markdown/markdown.js',
condition() {
return !!document.querySelector('[data-markdown]');
},
},
{
src: 'plugin/highlight/highlight.js',
async: true,
callback() {
hljs.initHighlightingOnLoad();
},
},
{ src: 'plugin/search/search.js', async: true },
{ src: 'plugin/notes/notes.js', async: true },
],
});
</script>
</body>
</html>