Making A Strong Case For Accessibility

A presentation at Code on the Beach in July 2022 in Atlantic Beach, FL, USA by Todd Libby

Slide 1

Slide 1

Making a Strong Case for Accessibility Todd Libby @toddlibby

Slide 2

Slide 2

Thank you!

Slide 3

Slide 3

Maine

Slide 4

Slide 4

Arizona

Slide 5

Slide 5

Slide 6

Slide 6

Slide 7

Slide 7

Portland, Maine 🦞 Phoenix, Arizona 🥵 Accessibility Team Lead @ WebstaurantStore Accessibility Engineer @ Centre for Inclusive Design W3C Invited Expert - Accessibility & WCAG3 ➡︎ 23 years of developer, design, & accessibility experience

Slide 8

Slide 8

Using Data to Advocate

Slide 9

Slide 9

WebAIM Million Report • One million homepages https://webaim.org/projects/million/

Slide 10

Slide 10

WebAIM Million Report • One million homepages • 50.8+ million accessibility errors https://webaim.org/projects/million/

Slide 11

Slide 11

WebAIM Million Report • One million homepages • 50.8+ million accessibility errors • Decreased 1.1% since February 2021 https://webaim.org/projects/million/

Slide 12

Slide 12

WebAIM Million Report • 887 elements to 955 elements per home page

Slide 13

Slide 13

WebAIM Million Report • 887 elements to 955 elements per home page • Increased 7.7% since February 2021

Slide 14

Slide 14

WebAIM Million Report • 887 elements to 955 elements per home page • Increased 7.7% since February 2021 • 5.3% of all home page errors had a detected accessibility error

Slide 15

Slide 15

96.8% had WCAG 2 failures

Slide 16

Slide 16

Low Contrast Text

Slide 17

Slide 17

Slide 18

Slide 18

Slide 19

Slide 19

SC 1.4.3 Contrast (Minimum)(Level AA) “The visual presentation of text and images of text has a contrast ratio of at least 4.5 to 1” https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html

Slide 20

Slide 20

Missing Alternative Text

Slide 21

Slide 21

Slide 22

Slide 22

<img src=“/path/to/img/lobster.png”> 🚫 <img src=“/path/to/img/lobster.png” alt=“”> ✅ <img src=“/path/to/img/lobster.png” alt=“Todd’s lobster roll, hot butter, and blueberry soda.”> ✅

Slide 23

Slide 23

• Low contrast text • Missing alternative text of images • Empty links • Missing form input labels • Empty buttons • Missing document language

Slide 24

Slide 24

96.5% of all errors

Slide 25

Slide 25

Examples of practical digital accessibility “Low-hanging fruit” • Color contrast that exceeds guidelines (>10 to 1 ratio) • Accessible color schemes • Keyboard/screen reader accessible • Accessible components (accordions, modals, tooltips, etc.) • Performant web apps, PWAs, mobile apps, Web sites

Slide 26

Slide 26

More Examples of practical digital accessibility • Scrollable interactive content • Alternative text on images where necessary (infographics, charts, graphs) • Accessible when viewing mobile phone screen (glare from sun) • Other situational disabilities • Broken arm • Child on lap

Slide 27

Slide 27

Disability is just Blind, Deaf, or Paralysis. Right?

Slide 28

Slide 28

Slide 29

Slide 29

Learning / Cognitive ADHD / ADD Fibromyalgia / Arthritis Tremors / Parkinson’s Migraine Headaches / Photophobia

Slide 30

Slide 30

Excuses

Slide 31

Slide 31

“The client doesn’t have the budget for it.”

Slide 32

Slide 32

“We’ll get to it after launch.”

Slide 33

Slide 33

“Why do we even need to make this thing accessible?”

Slide 34

Slide 34

“Why do we even need to make this thing accessible?” “There is no time to do this.”

Slide 35

Slide 35

“Why do we even need to make this thing accessible?” “There is no time to do this.” “We don’t have disabled users.”

Slide 36

Slide 36

“Why do we even need to make this thing accessible?” “There is no time to do this.” “We don’t have disabled users.” “The people that use our product are not disabled.”

Slide 37

Slide 37

“It’s a huge waste of time.”

Slide 38

Slide 38

Slide 39

Slide 39

Slide 40

Slide 40

Slide 41

Slide 41

Buy-In

Slide 42

Slide 42

Buy-In How do I et buy-in from stakeholders, clients, collea ues? g g • Support trickles down from stakeholders to managers, teams, and individuals.

Slide 43

Slide 43

Buy-In How do I et buy-in from stakeholders, clients, collea ues? • Support trickles down from stakeholders to managers, teams, and individuals. g g • Do this from the start. Low maintenance is needed, because of accessible designs and clean code.

Slide 44

Slide 44

Buy-In How do I et buy-in from stakeholders, clients, collea ues? • Support trickles down from stakeholders to managers, teams, and individuals. • Do this from the start. Low maintenance is needed, because of accessibility and clean code. g g • Cite instances from the lawsuits that have been won against major corporations (Domino’s Pizza, Target, Bank of America).

Slide 45

Slide 45

Buy-In How do I et buy-in from stakeholders, clients, collea ues? • Support trickles down from stakeholders to managers, teams, and individuals. • Do this from the start. Low maintenance is needed, because of accessibility and clean code. • Cite instances from the lawsuits that have been won against major corporations (Domino’s Pizza, Target, Bank of America). g g • Live testing with disabled users recorded on video.

Slide 46

Slide 46

$8 Trillion Worldwide of disposable income of individuals with disabilities https://www.triplepundit.com/story/2022/investing-disability-inclusion/741416

Slide 47

Slide 47

$490 Billion Disposable income of individuals with disabilities in the U.S. https://diverseabilitymagazine.com/2018/09/buying-power-people-disabilities/

Slide 48

Slide 48

Advocates

Slide 49

Slide 49

Organization Advocates Teams or individuals that advocate in your or anization g • Having a person throughout each department or a team focused on accessibility as a liaison.

Slide 50

Slide 50

Organization Advocates Teams or individuals that advocate in your or anization • Having a person throughout each department or a team focused on accessibility as a liaison. g • Someone that can answer questions and work with others to practice the guidelines and work with others to make accessible products.

Slide 51

Slide 51

Organization Advocates Teams or individuals that advocate in your or anization • Having a person throughout each department or a team focused on accessibility as a liaison. • Someone that can answer questions and work with others to practice the guidelines and work with others to make accessible products. g • Help set up documentation and tooling, serve as an intermediary between departments.

Slide 52

Slide 52

Assessment

Slide 53

Slide 53

Assessment Assess the product and the proficiency within the or anization g • Gauging where the product(s) are as far as how inclusive and accessible they are is a key priority.

Slide 54

Slide 54

Assessment Assess the product and the proficiency within the or anization • Gauging where the product(s) are as far as how inclusive and accessible they are is a key priority. g • What is the current state of the product, website, or mobile application?

Slide 55

Slide 55

Assessment Assess the product and the proficiency within the or anization • Gauging where the product(s) are as far as how inclusive and accessible they are is a key priority. • What is the current state of the product, website, or mobile application? g • Getting the general idea of the level of knowledge that teams and people in the company currently have.

Slide 56

Slide 56

Assessment Assess the product and the proficiency within the or anization • Gauging where the product(s) are as far as how inclusive and accessible they are is a key priority. • What is the current state of the product, website, or mobile application? • Getting the general idea of the level of knowledge that teams and people in the company currently have. g • How versed are they in guidelines (WCAG) and practices?

Slide 57

Slide 57

Assessment Assess the product and the proficiency within the or anization • Gauging where the product(s) are as far as how inclusive and accessible they are is a key priority. • What is the current state of the product, website, or mobile application? • Getting the general idea of the level of knowledge that teams and people in the company currently have. • How versed are they in guidelines (WCAG) and practices? g • How much training do you have and will you need?

Slide 58

Slide 58

Training

Slide 59

Slide 59

Training Maintainin A Written Record • Of all accessibility training done g • To meet requirements that apply to the organization

Slide 60

Slide 60

Training Maintainin A Written Record • Of all accessibility training done • To meet requirements that apply to the organization g • Great way to keep data on all training done in organization

Slide 61

Slide 61

Training Maintainin A Written Record • Of all accessibility training done • To meet requirements that apply to the organization • Great way to keep data on all training done in organization g • Record the training and who trained and when it was completed

Slide 62

Slide 62

Training Maintainin A Written Record • Of all accessibility training done • To meet requirements that apply to the organization • Great way to keep data on all training done in organization g • Record the training and who trained and when it was completed • If there is no inter-organizational training use orgs that do training.

Slide 63

Slide 63

Training Maintainin A Written Record • Of all accessibility training done • To meet requirements that apply to the organization • Great way to keep data on all training done in organization • Record the training and who trained and when it was completed • If there is no inter-organizational training use orgs that do training. • Deque • TPGi g • WebAIM

Slide 64

Slide 64

Guidelines

Slide 65

Slide 65

Guidelines Consistent implementation • Design systems ensure accessibility and inclusivity and the understanding of code better

Slide 66

Slide 66

Guidelines Consistent implementation • Design systems ensure accessibility and inclusivity and the understanding of code better • Accessible components reduce time to implement

Slide 67

Slide 67

Guidelines Consistent implementation • Design systems ensure accessibility and inclusivity and the understanding of code better • Accessible components reduce time to implement ffi • Testing procedures implemented so people can do jobs well and e ciently

Slide 68

Slide 68

Guidelines Consistent implementation • Design systems ensure accessibility and inclusivity and the understanding of code better • Accessible components reduce time to implement • Testing procedures implemented so people can do jobs well and e ffi • Document guidelines in a collaborative manner using tools ciently

Slide 69

Slide 69

Standards

Slide 70

Slide 70

Standards Guidelines from different countries • American Disabilities Act (ADA) - United States • Section 508 (U.S. Government)

Slide 71

Slide 71

Standards Guidelines from different countries • American Disabilities Act (ADA) - United States • Section 508 (U.S. Government) • Accessible Canada Act (ACA) - Canada

Slide 72

Slide 72

Standards Guidelines from different countries • American Disabilities Act (ADA) - United States • Section 508 (U.S. Government) • Accessible Canada Act (ACA) - Canada • EN 301 549 - European Union

Slide 73

Slide 73

Standards Guidelines from different countries • American Disabilities Act (ADA) - United States • Section 508 (U.S. Government) • Accessible Canada Act (ACA) - Canada • EN 301 549 - European Union • Web Content Accessibility Guidelines (WCAG) - Internationally

Slide 74

Slide 74

Standards Guidelines from different countries • American Disabilities Act (ADA) - United States • Section 508 (U.S. Government) • Accessible Canada Act (ACA) - Canada • EN 301 549 - European Union • Web Content Accessibility Guidelines (WCAG) - Internationally • Convention on the Rights of Persons with Disabilities (CPRD) • Article 9 • Article 21

Slide 75

Slide 75

Testing

Slide 76

Slide 76

Use Cases/Testing Hirin disabled people g • Test & record cases where disabled users are using the product

Slide 77

Slide 77

Use Cases/Testing Hirin disabled people • Test & record cases where disabled users are using the product g • Present to colleagues/stakeholders

Slide 78

Slide 78

Use Cases/Testing Hirin disabled people • Test & record cases where disabled users are using the product • Present to colleagues/stakeholders • Outsource testing with companies: g • Fable

Slide 79

Slide 79

Use Cases/Testing Hirin disabled people • Test & record cases where disabled users are using the product • Present to colleagues/stakeholders • Outsource testing with companies: • Fable • Hire disabled people! g • Teaching and advocating

Slide 80

Slide 80

Accessibility Overlays

Slide 81

Slide 81

“We use an accessibility overlay. We’re okay.”

Slide 82

Slide 82

Slide 83

Slide 83

AccessiBe Audioeye Equalweb Facil’iti Usablenet Userway Many, many more!

Slide 84

Slide 84

Overlays will get you sued.

Slide 85

Slide 85

<script>(function(){ var s = document.createElement(‘script’), e = ! document.body ? document.querySelector(‘head’) : document.body; s.src = ‘https://acsbapp.com/apps/app/dist/js/app.js’; s.async = true; s.onload = function(){ acsbJS.init({ statementLink : ”, footerHtml : ”, hideMobile : false, hideTrigger : false, language : ‘en’, position : ‘left’, leadColor : ‘#000000’, triggerColor : ‘#000000’, triggerRadius : ‘50%’, triggerPositionX : ‘left’, triggerPositionY : ‘center’, triggerIcon : ‘people’, triggerSize : ‘small’, triggerOffsetX : 3, triggerOffsetY : 3, mobile : { triggerSize : ‘small’, triggerPositionX : ‘left’, triggerPositionY : ‘center’, triggerOffsetX : 3, triggerOffsetY : 3, triggerRadius : ‘50%’ } }); }; e.appendChild(s);}());</script>

Slide 86

Slide 86

!==

Slide 87

Slide 87

So what do we do?

Slide 88

Slide 88

Do The Work

Slide 89

Slide 89

Maintenance Accessibility is never done • Automated testing wherever possible with new releases or changes

Slide 90

Slide 90

Maintenance Accessibility is never done • Automated testing wherever possible with new releases or changes • Screen reader analysis before every release

Slide 91

Slide 91

Maintenance Accessibility is never done • Automated testing wherever possible with new releases or changes • Screen reader analysis before every release • Annual audits

Slide 92

Slide 92

Maintenance Accessibility is never done • Automated testing wherever possible with new releases or changes • Screen reader analysis before every release • Annual audits • User testing

Slide 93

Slide 93

Maintenance Accessibility is never done • Automated testing wherever possible with new releases or changes • Screen reader analysis before every release • Annual audits • User testing • Accessibility is never done! Keep moving forward!

Slide 94

Slide 94

Maintenance Accessibility is never done • Automated testing wherever possible with new releases or changes • Screen reader analysis before every release • Annual audits • User testing • Accessibility is never done! Keep moving forward! • Like the web, accessibility is always evolving

Slide 95

Slide 95

Slide 96

Slide 96

“…our industry as a whole thinks less and less about accessibility (not that we ever had an A game on the subject), and talks less and less about progressive enhancement, preferring to chase the ephemeral goal posts of overengineered solutions to non-problems.” Jeffrey Zeldman - https://www.zeldman.com/2019/12/01/bluebeanieday2019/

Slide 97

Slide 97

Slide 98

Slide 98

Design and develop for people not like yourself and keep that in mind when throwing words like “inclusive” and “accessible” around.

Slide 99

Slide 99

A11y is a right. NOT a privilege. https://cottonbureau.com/products/a11y-is-a-right#/5254640/

Slide 100

Slide 100

Links https://noti.st/colabottles/SJME5e/making-a-strongcase-for-accessibility https://toddl.dev/slides/ @toddlibby on Twitter

Slide 101

Slide 101

Thanks!