Eric Eggert, Knowbility — AHG 2018
Eric Eggert works with Knowbility and the W3C on improving the Web for People with Disabilities, and everyone else.
Observe
Understand
Apply
*But not a graphic designer 😉
Observe
Understand
Apply
Do I observe what and who I need?
Do I draw the correct conclusions from my observations?
How do I make sure that my understanding is reflected in my app?
Accessibility
Performance
Look/Design
Security
Data protection
Usability
Photo by Robson Hatsukami Morgan on Unsplash
Information and user interface components must be presentable to users in ways they can perceive.
Text Alternatives, Captions, Transcriptions,
Audio Descriptions, Adaptable, Distinguishable
User interface components and navigation must be operable.
Keyboard, Enough Time, Seizures and Physical Reactions, Navigable, Input Modalities🆕
Information and the operation of user interface must be understandable.
Readable, Predictable, Input Assistance
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Compatible
Build with Accessibility in Mind!
Minimal Gap
non-slip surface
contrasting color
Keep it simple, stupid!
By Casablanca Records (Billboard, page 52, 17 Dec 1977) [Public domain], via Wikimedia Commons
The following example can make your website less accessible!
<!-- (BAD) -->
<h1 role="button">heading button</h1>
<!-- (GOOD!) -->
<h1><button>heading button</button></h1>
<th
tabindex="0"
role="button"
aria-label="Sort column"
>Name</th>
<th>
Name
<button aria-label=
"Sort column">
🔼🔽
</button>
</th>
<body aria-hidden="true">
…content…
<div id="modal" aria-hidden="false">
…modal content…
</div>
…content…
</body>
Eric Eggert, Knowbility & W3C/WAI
@yatil@micro.yatil.net
@yatil@twitter.com
https://yatil.net