Making A Strong Case For Accessibility

A presentation at Connect.tech 2021 in November 2021 in Atlanta, GA, USA by Todd Libby

Slide 1

Slide 1

Making A Strong Case For Accessibility Todd Libby Slides: https://noti.st/colabottles/y0skmR/making-a-strong-case-for-accessibility @toddlibby

Slide 2

Slide 2

Thank You! #ConnectTech

Slide 3

Slide 3

Thank you, sponsors!

Slide 4

Slide 4

Slide 5

Slide 5

Who Are You?

Slide 6

Slide 6

Accessibility Engineer @ WebstaurantStore Front End/Backend Developer, Accessibility Advocate, W3C Member

Slide 7

Slide 7

Slide 8

Slide 8

https://webaim.org/projects/million/

Slide 9

Slide 9

“The design of mainstream products and/or services that are accessible to, and usable by, as many people as reasonably possible… without the need for special adaptation or specialized design.” — The British Standards Institution (2005) https://shop.bsigroup.com/upload/Download/30317424.pdf

Slide 10

Slide 10

https://www.w3.org/TR/WCAG21/#contrast-minimum

Slide 11

Slide 11

https://www.w3.org/WAI/WCAG21/Understanding/contrastminimum.html

Slide 12

Slide 12

Slide 13

Slide 13

<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 rolls”> ✅

Slide 14

Slide 14

Slide 15

Slide 15

Other Examples Other examples of practical di ital accessibility Scrollable interactive content Alternative text on images where necessary (infographics, charts, graphs) Sunlight when viewing mobile phone screen Other situational disabilities Broken arm g Child on lap

Slide 16

Slide 16

“The client doesn’t have the budget for it.” “We’ll get to it after launch.”

Slide 17

Slide 17

“The client doesn’t have the budget for it.” “We’ll get to it after launch.” “The people that use our product aren’t disabled.”

Slide 18

Slide 18

“The client doesn’t have the budget for it.” “We’ll get to it after launch.” “The people that use our product aren’t disabled.” “We don’t have disabled users.”

Slide 19

Slide 19

Slide 20

Slide 20

“You’ll be saving the company a lot of money when you do this from the start.” “When maintenance is needed, it won’t take the team as long to maintain the code because of accessibility and clean, semantic code.” “Your developers will feel less stress, less pressure, less headaches, less time spent reworking things.” “You’re less likely to be sued by an individual or individuals when they come across your product and they cannot access it.”

Slide 21

Slide 21

Buy-in How do I et buy-in from stakeholders, clients, collea ues? • Once you have stakeholder support, then you may see support trickle down to managers, then teams, and then individuals. • “You’ll be saving the company a lot of money when you do this from the start. When maintenance is needed, it won’t take the team as long to maintain the code because of accessibility and clean code.” • Cite instances from the lawsuits that have been won against Target, Bank of America, Domino’s Pizza, and others. • Live testing with disabled users are also another way to get buy-in across g g the board.

Slide 22

Slide 22

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

Slide 23

Slide 23

Assessment Assess the product and the proficiency within the or anization • Gauging the point 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? • What is the current state of the website or mobile application? • Getting the general idea of the level of knowledge that teams and people in the company currently have. 1. How versed are they in accessibility guidelines and practices? 2. Do they know anything about the Web Content Accessibility Guidelines (WCAG)? g 3. How much training do you have and will you need?

Slide 24

Slide 24

Training Maintainin A Written Record g • 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 such as: • WebAIM • Deque • TPGi

Slide 25

Slide 25

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

Slide 26

Slide 26

Slide 27

Slide 27

Slide 28

Slide 28

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 29

Slide 29

Slide 30

Slide 30

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

Slide 31

Slide 31

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! • Like the ever-evolving web, accessibility is always evolving

Slide 32

Slide 32

Slide 33

Slide 33

Now What?

Slide 34

Slide 34

Do The Work

Slide 35

Slide 35

Slide 36

Slide 36

Slide 37

Slide 37

“…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 over-engineered solutions to nonproblems.” Jeffrey Zeldman - https://www.zeldman.com/2019/12/01/bluebeanieday2019/

Slide 38

Slide 38

Slide 39

Slide 39

Slide 40

Slide 40

Slide 41

Slide 41

Slide 42

Slide 42

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

Slide 43

Slide 43

Thank you! @toddlibby https://toddl.dev https://noti.st/colabottles/y0skmR/making-a-strong-case-for-accessibility