Intro to ARIA -- A11ycasts #13

Subscribers:
791,000
Published on ● Video Link: https://www.youtube.com/watch?v=g9Qff0b-lHk



Duration: 9:16
111,742 views
2,104


ARIA 1.1 Spec: https://goo.gl/1rGD7S
ARIA Authoring Practices 1.1: https://www.w3.org/TR/wai-aria-practices-1.1/

Here on a11ycasts I always try to encourage developers to use native controls rather than roll their own mainly because you get semantics and keyboard functionality for free. But there are situations where you need to build something and there's no native analog in the platform. For these occasions when you need to go offroad and build your own control, the Web Content Accessibility Initiatives Accessible Rich Internet Applications spec (WAI-ARIA) can help you add in the semantics your new custom control is missing. Today on the show I'll cover what ARIA is from a high level and show off some of the features and relationships ARIA let's you take advantage of.

Why do semantics matter?
https://www.youtube.com/watch?v=g2tzEil5TL0

Watch all A11ycasts episodes: https://goo.gl/06qEUW

Subscribe to the Chrome Developers YouTube channel for updates on new episodes of A11ycasts: http://goo.gl/LLLNvf







Tags:
Chrome
Developers
Google
Web
product: chrome
fullname: Rob Dodson
Location: MTV
Team: Scalable Advocacy
Type: Screencast
Other: NoGreenScreen
Accessibility
Development
a11y
Rob Dodson
screenreader
web accessibility
accessibility
accessible
ARIA
GDS: Yes;