edit text blank – Inputs & Accessibility

A presentation at JSVidCon in May 2020 in by Oscar

Slide 1

Slide 1

🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨🚨 🚨 60,909,278

Slide 2

Slide 2

edit text blank Accessibility, Inputs & JavaScript tournant I think we need to talk about accessibility more broadly Oscar, he/him Tournant

Slide 3

Slide 3

https://r.ovl.design/jsvidcon Slides, Resources & Co. Twitter: @_ovlb

Slide 4

Slide 4

Babelfish

Slide 5

Slide 5

WAI W3C Web Accessibility Initiative https://www.w3.org/WAI/ Group of authors in W3C working improving accessibility in websites

Slide 6

Slide 6

ARIA Accessible Rich Internet Applications https://www.w3.org/WAI/standards-guidelines/aria/ A Specification «These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup.»

Slide 7

Slide 7

«WAI-ARIA provides a collection of accessibility states and properties […].» ARIA https://www.w3.org/TR/wai-aria/#usage which are used to support platform accessibility APIs on various operating system platforms Markup static, ARIA allows developers to change things dynamically. Hence the rich

Slide 8

Slide 8

WCAG Web Content Accessibility Guidelines https://www.w3.org/WAI/standards-guidelines/wcag/ Define Success Criteria Show Techniques

Slide 9

Slide 9

A11Y Shorthand for accessibility Eleven letters between a and y Term itself is not undisputed in the accessibility community

Slide 10

Slide 10

Slide 11

Slide 11

«The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.» Tim Berners-Lee, 1997 https://www.w3.org/Press/IPO-announce When the W3C launched the Web Accessibility Initiative

Slide 12

Slide 12

«98.1% of home pages had detectable WCAG 2 failures!» The WebAIM Million – WCAG CONFORMANCE https://webaim.org/projects/million/ Accessibility is a topic incredibly hard to test automatically WCAG conformant sites probably under 1 %

Slide 13

Slide 13

🤦 What happened?

Slide 14

Slide 14

Neglect

Slide 15

Slide 15

These are very basic things Mostly easy to fix Alt text for large publications requires a team effort, especially if it is missing for a long time

Slide 16

Slide 16

2019 survey

Slide 17

Slide 17

🙈 24% of organisations think they are WCAG compliant Web Key IT

Slide 18

Slide 18

👨👨👨👨👨👨👨👨👨👨 Mostly white, male and able-bodied

Slide 19

Slide 19

It’s not us. It’s society. But also us. We are privileged We are responsible for what we do with it

Slide 20

Slide 20

Slide 21

Slide 21

«Privilege is not my fault. But it is my responsibility.» Tatiana Mac https://www.youtube.com/watch?v=Hzs_8e3Xhhc

Slide 22

Slide 22

Complexity Over time websites have evolved from a medium to exchange scientific papers to one in which you can do basically anything These are the things that are – more often than not – not easy to fix

Slide 23

Slide 23

🚀

Slide 24

Slide 24

Accessibility is no rocket science. Some things are hard, yes. But let’s get the basics right.

Slide 25

Slide 25

WE NEED TO ACT. If we don’t want to look like a bunch of overpaid bollocks. Get people involved in web dev Listen to those who speak up

Slide 26

Slide 26

Making the Web Accessible

Slide 27

Slide 27

COLLABORATION On your own, understanding the ARIA and WCAG pages can be daunting

Slide 28

Slide 28

«The only way this work gets done is if we start small, and if we work together.» Ethan Marcotte – The web we broke https://ethanmarcotte.com/wrote/the-web-we-broke/ He asked the question «What’s one thing I wish I understood better about accessibility?»

Slide 29

Slide 29

USE SEMANTIC MARKUP. And ARIA where applicable. The first rule of ARIA is «Do not use ARIA» e.g. buttons «ARIA, the language created to help make interfaces more accessible, was found on more than sixty percent of the home pages surveyed. Unfortunately, those home pages were more likely to have detectable accessibility errors.» Ethan Marcotte citing from AIM 1 million

Slide 30

Slide 30

USE ASSISTIVE TECHNOLOGY. Start small, by clicking around and listen to the SR output Start navigating around with your keyboard Close your eyes

Slide 31

Slide 31

ASK USERS. They are the experts. Nothing about us without us Be humble We are not able to say what works, e.g. steep wheelchair ramp

Slide 32

Slide 32

PUT ACCESSIBILITY IN THE DEFINITION OF DONE … and be it your own. That means things you are going to do. It’s impossible to just make a whole existing site accessible. Try to get the people you are reporting aboard and agree

Slide 33

Slide 33

Accessible Inputs Why talk about this?

Slide 34

Slide 34

https://playground.owlish.dev/inclusive-inputs/

Slide 35

Slide 35

«56% of the 3.4 million form inputs identified were unlabeled (either via <label>, aria-label, or aria-labelledby), down from 59% in 2019.» The WebAIM Million – Form Labeling https://webaim.org/projects/million/#labels «Pages with at least one unlabeled form control averaged 43 more detectable errors than pages without any label errors.» 30 in 2019 Past interfaces I built are full of errors, present ones probably too

Slide 36

Slide 36

Structure taken from an online course Not everything is just divs

Slide 37

Slide 37

Slide 38

Slide 38

LABELING

Slide 39

Slide 39

Slide 40

Slide 40

Slide 41

Slide 41

Dragon natural speaking, talkback and VoiceOver don’t support implicit labels in Voice Control mode

Slide 42

Slide 42

Very little has changed

Slide 43

Slide 43

aria-label

Slide 44

Slide 44

Slide 45

Slide 45

Two circling hearts, button

Slide 46

Slide 46

DON’T MAKE YOUR USERS GUESS. Unless you write the crosswords for the New York Times.

Slide 47

Slide 47

Slide 48

Slide 48

Slide 49

Slide 49

ACCESSIBLE ICON BUTTONS https://www.sarasoueidan.com/blog/accessible-icon-buttons/

Slide 50

Slide 50

MARKING REQUIRED FIELDS

Slide 51

Slide 51

Slide 52

Slide 52

Slide 53

Slide 53

aria-hidden Hide an element from Assistive Technology

Slide 54

Slide 54

HIDING ELEMENTS FROM SCREEN READERS USING aria-hidden https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/hidden/

Slide 55

Slide 55

Slide 56

Slide 56

Source: Scott O’Hara – Inclusively Hidden https://www.scottohara.me/blog/2017/04/14/inclusively-hidden.html

Slide 57

Slide 57

Slide 58

Slide 58

Slide 59

Slide 59

REQUIRED ATTRIBUTE REQUIREMENTS https://developer.paciellogroup.com/blog/2019/02/requiredattribute-requirements/

Slide 60

Slide 60

DESCRIBING FIELDS

Slide 61

Slide 61

Slide 62

Slide 62

And with this problem we leave the realm of native HTML

Slide 63

Slide 63

aria-describedby Describe an element using the text content of another aria-describedby, provides the means to associate an element with the text of another object, or objects, in the document. When properly used, this attribute can provide the necessary information to assist in creating inclusive user experiences.»

Slide 64

Slide 64

DESCRIBING aria-describedby https://developer.paciellogroup.com/blog/2018/09/describing-aria-describedby/ Scott O’Hara

Slide 65

Slide 65

Slide 66

Slide 66

Slide 67

Slide 67

Slide 68

Slide 68

Slide 69

Slide 69

Expanding the Toolbox 🧰

Slide 70

Slide 70

«The only way this work gets done is if we start small, and if we work together.» Ethan Marcotte – The web we broke https://ethanmarcotte.com/wrote/the-web-we-broke/

Slide 71

Slide 71

https://www.ovl.design/text/inclusive-inputs/

Slide 72

Slide 72

Install all you problems away

Slide 73

Slide 73

https://r.ovl.design/jsvidcon Slides, Resources & Co. Twitter: @_ovlb

Slide 74

Slide 74

#LeaveNoOneBehind https://www.flickr.com/photos/acampadabcnfoto/39943411872/

Slide 75

Slide 75

Unbreak the web. tournant https://ui.tournant.dev @tournantdev ♡