Why headings and landmarks are so important -- A11ycasts #18

Channel:
Chrome for Developers
Subscribers:
792,000
Published on ● Video Link: https://www.youtube.com/watch?v=vAAzdi1xuUY


Duration: 7:18
34,019 views
724

Accessibility Fundamentals: Semantics and Navigating Content
https://goo.gl/KgU3v3

One of the key goals in building an accessible experience is to make sure users of assistive technology can browse the page efficiently. Proper usage of h1-h6 headings can really improve the browsing experience for someone on a screen reader, because they help the user quickly create a mental outline for the page content. Combine this with HTML5 landmark elements like main and nav, and the user can take advantage of built-in screen reader feature to quickly jump from one section of the site to the next. Today on A11ycasts I'll show you how this works using the VoiceOver screen reader and a few simple examples.

Screen reader navigation strategy survey: https://goo.gl/H6H8OB

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



Other Videos By Chrome for Developers


2017-07-06Push Messages - Supercharged
2017-06-29Offline Links - Supercharged
2017-06-23Building a Media Player #14: Season Roundup
2017-06-22Code Splitting: Live Code Session - Supercharged
2017-06-16Accessible Modal Dialogs -- A11ycasts #19
2017-06-15Building a Media Player #13: Background Fetch
2017-06-05Chrome 59: Headless Chrome, Native Notifications on macOS and the Image Capture API
2017-06-02Chrome 59 - What's New in DevTools
2017-06-02Supercharged: What Would You Like To See?
2017-05-31Building New Tools for Designers and Developers -- Designer vs. Developer #6
2017-05-26Why headings and landmarks are so important -- A11ycasts #18
2017-05-19Using Web Components with Angular (Google I/O '17)
2017-05-19Google I/O'17: Channel 6
2017-05-19Cranking Up Performance in Graphics Intensive Web Apps and Games (Google I/O '17)
2017-05-19DevTools: State of the Union 2017 (Google I/O '17)
2017-05-19Staying off the Rocks: Using Lighthouse to Build Seaworthy Progressive Web Apps (Google I/O '17)
2017-05-19Production Progressive Web Apps With JavaScript Frameworks (Google I/O '17)
2017-05-19Secure and Seamless Sign-In: Keeping Users Engaged (Google I/O '17)
2017-05-19The Future of Audio and Video on the Web (Google I/O '17)
2017-05-19Building for Your Next Billion Users (Google I/O '17)
2017-05-19Getting the Green Lock: HTTPS Stories from the Field (Google I/O '17)


Tags:
accessibility
web accessibility
accessible design
headings
headings and landmarks
wcag
h1 tag
html h1
heading tags
h1 h2 h3
accessibility testing
w3c validator
w3c css
web design
web development
aria
wai aria
web developer
programming
html
css
javascript
accessible
a11y
Chrome
Developers
Google
Web
product: chrome
fullname: Rob Dodson
Location: MTV
Team: Scalable Advocacy
Type: Screencast
Other: NoGreenScreen
GDS: Yes;