Accessibility API 101

on YouTube ↗01h 04m

" summary

Claim: the accessibility API is an older, slimmer layer than the DOM and many JavaScript frameworks break the mapping between visual DOM and assistive tech. Demonstrations use Edge devtools and NVDA to show a div/span table reads as isolated cells but a native <table> exposes headers and column relationships to screen readers. ARIA existed to patch the gap because JavaScript doesn't talk to the accessibility API. Refactoring accessibility later costs about 6–8× more; rule of thumb: native HTML elements first.

AI-written summary · about

" chapters (6)

1. 0:00Introduction to accessibility
2. 10:35Native HTML elements importance
3. 21:53DOM vs accessibility API
4. 33:21JavaScript and accessibility myth
5. 44:17Web evolution and accessibility
6. 57:00Takeaways and Q&A

" related talks

• 12mHarnessing the Accessibility TreeCorina Murg · SquiggleConf 2024
• 26mAccessibility Is a Marathon, not a SprintBrittany Feenstra · React Conf 2019
• 26mDemystifying Accessibility in React AppsKateryna Porshnieva · React Brussels 2024
• 47mPeeling Back the Layers of Web AccessibilityJared Smith · Inclusive Design 24 (#id24) 2018
• 33mAccessibility and JS: side-by-sideFelipe de Albuquerque · JSConf US 2015
• 16mDemystifying accessibility in React appsKateryna Porshnieva · React Conf 2024
• 28mDeveloper's Guide to Accessibility MechanicsLéonie Watson · You Gotta Love Frontend 2016
• 37mAccessibility Matters: Creating a Better WebLindsey Dragun · DjangoCon US 2017