Accessibility is My Favorite Part of the Platform - Google I/O 2016

[@AdrianColley]

0:00 Why Accessibility Is Important 6:30 The kinds of accommodation for different users 9:55 WCAG 2.0 and WebAIM Checklist 10:48 Practical advice: figure out the primary "user journeys" and analyze their a11y 11:47 Focus and tab order 14:48 Practical advice: let DOM order be the natural tab order 16:15 Practical advice: focusability is for interactive elements, not important ones 17:42 Practical advice: using native elements saves you a lot of work managing focus 18:50 tabindex 21:38 WAI-ARIA Authoring guide 22:32 Practical advice: Amortize the toil by building reusable web components 23:36 Modal windows and paper-dialog 26:00 What are semantics and how to they benefit our users? 28:00 Crucial element semantics: roles, names, states, and values. 29:02 Practical advice: using native elements saves you a lot of work managing semantics 30:34 WAI-ARIA, which changes semantics but not behavior 33:59 aria-label and aria-labelledby 36:15 Practical advice: how to try out a screen reader 36:39 Practical advice: use the Chrome accessibility dev tools 37:37 Polymer web components showcase 39:05 Wrap-up and TL;DR I made this table of contents because I was frustrated that so much of the beginning of this talk was wasted advocacy, seeking to convince us all that a11y is important. If we weren't already convinced, we probably wouldn't even be here!

[@DrRobrez]

definitely important to put emphasis on a11y as a design requirement rather than an afterthought. thanks rob

[@letswatchrob]

+robrez thanks man! glad you enjoyed it :D

[@AndiGalpern]

Excellent talk and spoken with great clarity and confidence. Great job!

[@JustinJohn107]

Awesome talk! Excited for when the full blown Udacity course launches.

[@murielsilveira]

Excellent talk Rob! It would be nice to put the links you talked about on the description, that way it's easy to check out them after the talk :)

[@JeffTheOwens]

Great talk! Covered a broad range of topics quickly and with clarity. What was the tool being used to show screen reader output on the "Shop" example site?

[@letswatchrob]

Thanks! The screen output was just the default display from the VoiceOver screen reader on Mac

[@Andrewilll]

Great video, I'm creating an application to use just with a keyboard, tabindex is awesome!

[@jerryoglesby4205]

I would like some help from Goodwill

[@jerryoglesby4205]

I would like somebody to help me get hooked up with ESPN

[@jerryoglesby4205]

I didn't went through the process of filling out the play the everything they asked me

[@jerryoglesby4205]

I need some help with Google

[@zhangtao2000]

Could you share the slides? Thanks!

[@letswatchrob]

+Tao Zhang yep! they're up at speakerdeck.com/robdodson/accessibility-is-my-favorite-part-of-the-platform

[@vrjb100]

reinventing every existing component into a web component makes sense. A my-checkbox SHOULD have a non null label as a property, then you can add the aria things, so that users of my-checkbox get accessibility for free. A checkbox without a label is useless for the non impaired user. it's obviously a case of demonstrating html is defective by design, because it lacks any form of design. The inventors of sgml and therefore html were junior amateurs on programming. ditch html5 go for a new standard, w3c should be left out, they are too slow. leave out commercial companies, they are only interested in short term profits, not good products.