Tweet
Tweet

Slide 1

Slide 1 text

Refactoring for Accessibility Kim Schlesinger Denver Node.js Meetup - May 2019 @kimschles

Slide 2

Slide 2 text

An accessibility refactor will improve your product and your codebase more effectively than a code-only refactor. @kimschles

Slide 3

Slide 3 text

Kim Schlesinger Ops, Education & Software @kimschles

Slide 4

Slide 4 text

@kimschles

Slide 5

Slide 5 text

@kimschles

Slide 6

Slide 6 text

Roadmap 1. Why 2. What 3. How @kimschles

Slide 7

Slide 7 text

The Why @kimschles

Slide 8

Slide 8 text

I thought I knew more than I did... @kimschles

Slide 9

Slide 9 text

@kimschles

Slide 10

Slide 10 text

Dunning-Kruger Effect is a psychological phenomenon in which people of the lowest ability in a subject rate themselves as most competent compared to others. -- Hubspot @kimschles

Slide 11

Slide 11 text

WebAIM Million 97.8% of home pages had detectable WCAG 2 failures @kimschles

Slide 12

Slide 12 text

2.2% of home pages had no WCAG 2 failures @kimschles

Slide 13

Slide 13 text

! @kimschles

Slide 14

Slide 14 text

The What @kimschles

Slide 15

Slide 15 text

What is accessibility? Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. --WC3 Web Accessibility Initiative @kimschles

Slide 16

Slide 16 text

Question: How do we know when something is accessible and when it's not? @kimschles

Slide 17

Slide 17 text

Answer: STANDARDS @kimschles

Slide 18

Slide 18 text

@kimschles

Slide 19

Slide 19 text

Web Standards The World Wide Web Consortium Goal: Interoperability between different types of computers and browsers @kimschles

Slide 20

Slide 20 text

A short list of W3C Standards • HTML • CSS • DOM • XML • ARIA @kimschles

Slide 21

Slide 21 text

WCAG Web Content Accessibility Guidelines Versions 2.0 and 2.1 @kimschles

Slide 22

Slide 22 text

POUR Perceivable Operable Understandable Robust @kimschles

Slide 23

Slide 23 text

WCAG 2.0 Guidelines @kimschles

Slide 24

Slide 24 text

@kimschles

Slide 25

Slide 25 text

Other standards or guidelines • Section 508 @kimschles

Slide 26

Slide 26 text

The How @kimschles

Slide 27

Slide 27 text

1. Use multiple tools to identify accessibility issues @kimschles

Slide 28

Slide 28 text

WAVE Extension @kimschles

Slide 29

Slide 29 text

alt text @kimschles

Slide 30

Slide 30 text

Before const CompanyProfileCard = (props : Props) => ( @kimschles

Slide 31

Slide 31 text

Before const CompanyProfileCard = (props : Props) => ( @kimschles

Slide 32

Slide 32 text

After const CompanyProfileCard = (props : Props) => ( @kimschles

Slide 33

Slide 33 text

Use JS template literals to dynamically populate alt text for images. @kimschles

Slide 34

Slide 34 text

Checklists, Exemplars and Screenreaders • A11y Checklist • Good examples you can deconstruct • The A11y Project • Eric Bailey Design • Inclusive Design Principles • Manual Testing with a Screen Reader @kimschles

Slide 35

Slide 35 text

Provide a “Skip to main content” link @kimschles

Slide 36

Slide 36 text

Add the skip nav code, or component, to the top of your header @kimschles

Slide 37

Slide 37 text

import React from 'react'; const SkipNav = () => (
  • Skip to Main Content
  • Accessibility Statement
); export default SkipNav; @kimschles

Slide 38

Slide 38 text

.skipnav-item { border: 0; clip: rect(0, 0, 0, 0); height: 1px; margin: -1px; overflow: hidden; padding: 0; position: absolute; width: 1px; } @kimschles

Slide 39

Slide 39 text

@kimschles

Slide 40

Slide 40 text

Skip Navigation Links • Create a way for people using screen readers to skip to the main content of the page • If you're using a JS framework, make this a component you can easily reuse @kimschles

Slide 41

Slide 41 text

1. Use multiple tools to identify issues @kimschles

Slide 42

Slide 42 text

2. Commit to accessibility being an ongoing process, not a one time fix @kimschles

Slide 43

Slide 43 text

Accessibility Statement @kimschles

Slide 44

Slide 44 text

import React from 'react'; const SkipNav = () => (
  • Skip to Main Content
  • Accessibility Statement
); export default SkipNav; @kimschles

Slide 45

Slide 45 text

import React from 'react'; const SkipNav = () => (
  • Skip to Main Content
  • Accessibility Statement
); export default SkipNav; @kimschles

Slide 46

Slide 46 text

Why? • Show your users that you care about accessibility and about them • Provide them with information about the accessibility of your content • Demonstrate commitment to accessibility, and to social responsibility -- W3C Web Accessibility Initiative @kimschles

Slide 47

Slide 47 text

Examples • diversity Accessibility Statement • Eric Bailey Accessibility Statement @kimschles

Slide 48

Slide 48 text

Accessibility Statement • Include an accessibility statement to state your intentions, your known accessibility issues and how to contact someone if there are barriers to access • Continue working on making your site accessible, and update your statement as needed @kimschles

Slide 49

Slide 49 text

An accessibility refactor will improve your product and your codebase more effectively than a code-only refactor. @kimschles

Slide 50

Slide 50 text

What Can I Do? @kimschles

Slide 51

Slide 51 text

If you work at a company • Find ways to discuss accessibility with people in positions of leadership • Offer to lead a lunch and learn on the topic @kimschles

Slide 52

Slide 52 text

If you're in school • Ask your instructor when you'll be covering accessibility in the curriculum. • If it will not be covered, respectfully ask 'why not?' • Give a lightning talk or lesson about the topic @kimschles

Slide 53

Slide 53 text

Everyone • Attend the the Front Range Accessibility and Inclusive Design Meetup in Boulder! • Subscribe to the A11y Weekly Newsletter • Come to Develop Denver! @kimschles

Slide 54

Slide 54 text

Recap 1. Why 2. What 3. How @kimschles

Slide 55

Slide 55 text

How 1. Use multiple tools to identify issues 2. Commit to accessibility being an ongoing process, not a one time fix 3. Insist that developing accessible applications is core to your organization @kimschles

Slide 56

Slide 56 text

Accessibility Resources • Wave Web Accessibility Evaluation System • a11y Web Accessibility Checklist • Inclusive Design Principles • Eric Bailey: Fighting Uphill • Crystal Preston-Watson Demystifying Accessibility Talk @kimschles

Slide 57

Slide 57 text

Questions @kimschles

Slide 58

Slide 58 text

Contact Me kimschlesinger.com developdenver.org hirediversity.us @kimschles on twitter, github and twitch @kimschles