Make screenreaders insert extra content, change pronunciations, or forget an element's semantics altogether – with just few lines of everyday CSS. I've returned to the ReactJS Dallas meetup to show off the influences that CSS has on screenreaders which blew my mind, and to dive deeper into browser and operating system internals.
Relevant Links
- Get the slides!
- Play with the demos yourself
- My posts which inspired this talk: CSS Can Influence Screenreaders and The Accessibility Tree
- Would you like me to put this talk on for your group? Reach out at ben@benmyers.dev!
- Related talks you might be interested in: CB Averitt at A11yTalks and Manuel Matuzović at Inclusive Design 24
Learn More
- "Screen Readers and CSS: Are We Going Out of Style (and into Content)?" by John Northup for the WebAIM Blog
- Core Accessibility API Mappings 1.2
- "The Accessibility Tree Training Guide" by WhatSock
- Table heuristics in the Chromium source code
- Table heuristics in the Firefox source code
- "Tables, CSS Display Properties, and ARIA" by Adrian Roselli