A presentation at John Slatin AccessU 2020 by Eric Eggert
Connecting the Accessibility Dots Eric Eggert · AccessU · May 2020
Eric Eggert Eric Eggert is a Web Developer and Teacher who works with on improving the Web for People with Disabilities, and everyone else. 2013–2020: W3C/Web Accessibility Initiative My name is Eric Eggert and I work with Knowbility and the W3C to improve the Web for People with Disabilities. I work with Knowbility as the tech team lead. And have worked with W3C in the past.
Connecting arbitrary dots that fits one’s own view.
Images: Till Credner, https://commons.wikimedia.org/wiki/User:Till_Credner
The Big Picture
98.1% Detectable WCAG Failures ↗ from 97.8% in February 2019 WebAIM: The WebAIM Million
WebAIM Million WCAG Failure Type Feb 2019 Feb 2020 Change Low contrast text 85.3% 86.3% +1.0% Missing alternative text for images 68.0% 66.0% −2.0% Empty links 58.1% 59.9% +1.8% Missing form input labels 52.8% 53.8% +1.0% Empty buttons 25.0% 28.7% +3.7% Missing document language 33.1% 28.0% −5.1% WebAIM: The WebAIM Million
How do I make this accessible?
this
Why…? → Why is accessibility important? → Why don’t we have safeguards that ensure accessibility? → Why did the designer design inaccessibly? → Why did the developer implement inaccessibly? → Why did the PM not catch it? → Why did we decide for this feature?
CRPD Convention on the Rights of Persons with Disabilities
United Nations
If ensuring accessibility is something that we as a society agree is the right thing to do, we need to work together to move it forward.
Accessibility is too hard.
Accessibility is easy.
Accessibility is easy to do wrong.
Why is Accessibility so easy to do wrong?
People are set up to fail. Not on purpose, of course. But accessibility can only be a reality if we all pull into the same direction
We need to prioritize accessibility higher. We must make sure that it is an integral part of building products.
Guidance needs to be better.
Guidance needs to include everyone.
Design Principles
Design Principles make projects successful
WCAG has design principles built in
! Tangent Isn’t it weird that we always look at the most granular guidance in WCAG? (The SCs.) The SCs are the hurdle and we run towards the hurdle without concentrating on the point where we need to jump. We run and run and run and suddenly – there it is. The hurdle. And then we try to jump over it without getting up to speed first.
WCAG Design Principles
Your product must be → 1. Perceivable → 2. Operable → 3. Understandable → 4. Robust
Other Design principles…
Dieter Rams → *20 May 1932 → Wiesbaden, Germany → Designer → Braun Consumer Products → Watch the Documentation – 1 free today only 1 https://www.ohyouprettythings.com/free
Good Design… 1. is innovative 2. makes a product useful 3. is aesthetic 4. makes a product understandable 5. is unobtrusive 6. is honest 7. is long-lasting 8. is thorough down to the last detail 9. is environmentally friendly 10. is minimal
Good Design… 1. is innovative 2. makes a product useful 3. is aesthetic 4. makes a product understandable 5. is unobtrusive 6. is honest 7. is long-lasting 8. is thorough down to the last detail 9. is environmentally friendly 10. is minimal 6. is honest – It does not make a product appear more innovative, powerful or valuable than it really is. It does not attempt to manipulate the consumer with promises that cannot be kept. 7. is long-lasting – It avoids being fashionable and therefore never appears antiquated. Unlike fashionable design, it lasts many years – even in today’s throwaway society. 8. is thorough down to the last detail – Nothing must be arbitrary or left to chance. Care and accuracy in the design process show respect towards the consumer. 9. is environmentally friendly – Design makes an important contribution to the preservation of the environment. It conserves resources and minimizes physical and visual pollution throughout the lifecycle of the product. 10. is minimal – Less is more. Simple as possible but not simpler. Good design elevates the essential functions of a product.
Good Design and WCAG… 1. is innovative – Accessibility can act as an incubator for innovation. 2. makes a product useful – 2. Operable 3. is aesthetic 4. makes a product understandable – 3. Understandable 5. is unobtrusive – 1. Perceivable/3. Understandable 6. is honest – 4. Robust 7. is long-lasting – 4. Robust 8. is thorough down to the last detail – 1. Perceivable 9. is environmentally friendly – 4. Robust 10. is minimal – 1. Perceivable
Good design centers on the user
Designers and Developers work for users
User Impairment Proficiency Accessibility Support
How do we make Accessibility easier to do right?
→ Keep the principles in mind and work towards them → Make sure you’re on the right track → Use tools and integrations to set you up for success
But we also need to do more as community to set us up for success.
→ Better education for designers and developers → Provide better, easier tools for accessibility → Guide and lead by designing products that are accessible and aesthetic → Make accessibility a welcoming space in which people want to participate → Provide more reliable implementation of technologies
For example: Improving form controls in Microsoft Edge and Chromium Improving form controls in Microsoft Edge and Chromium - Microsoft Edge Blog
See also HTML: The Inaccessible Parts Dave Rupert
Thank You! Eric Eggert Web: yatil.net E-Mail: mail@yatil.net Social: @yatil
It is easy to get lost in the requirements for accessibility, the needs of people with disabilities and intricate specific workings of assistive technologies. I addition there’s lots of jargon around that does makes picking up accessibility hard.