I am Rob Dodson. Ask me anything.

View original thread
John Eisenberg's photo

Hi Rob! Thanks for the AMA.

What are some problems that need to be solved regarding the web accessibility in 2018? The top priorities.

Rob Dodson's photo

Developer Advocate @ Google

Great question!

We still need more folks to understand the fundamentals of tabbing/arrowing through a site and getting familiar with at least one screen reader. For anyone not sure how to get started with that, we have a free course up on Udacity (https://bit.ly/web-a11y).

We also need better APIs. I've seen a lot of folks building pretty fancy UIs for their apps and making them accessible by flipping ARIA attributes is tough stuff! I'm super excited for AOM (https://github.com/WICG/aom), inert (https://github.com/WICG/inert), and :focus-visible (https://github.com/WICG/focus-visible).

I'd also love to see more folks using and contributing to the ARIA Authoring practices guide (https://www.w3.org/TR/wai-aria-practices-1.1/). This is basically your cheat sheet for component accessibility. It's an amazing doc put together by a handful of awesome folks. It's all on GitHub (https://github.com/w3c/aria-practices) so if folks want to try to contribute more patterns or examples, that would be great :)

I personally also want to spend more time working on cross-browser support and cross-assistive technology support. Recently I've seen teams who are building pretty complex UIs which they finally get working in one or two screen readers, only to find that another popular screen reader offers a really different experience. It's hard to stay on top of every screen reader + OS + browser combo, so whatever we can do to make those experiences more consistent would be a big win, IMO.