Crafting Comics for Literally Everyone
summary
Claims a working webcomic prototype that narrates panels to screen readers, built as an Ember single-page app with layered images and semantic HTML instead of duplicating content, uses an aria-live route announcer (page-title updates) to signal navigation, and leans on VoiceOver and NVDA for manual testing plus axe-core audits for regressions. Shows concrete accessibility wins and tradeoffs — avoids strobe effects after the Pokémon incident, cites the startling 2.2% figure from a million-site audit, and demonstrates that the demo actually reads and navigates.
AI-written summary · about
chapters (14)
- 0:00Introduction to accessible comics
- 1:09Comics and accessibility challenges
- 3:35Existing accessible comics initiatives
- 6:02Web comic app accessibility
- 8:47Semantic HTML and screen readers
- 11:16Screen reader navigation demo
- 13:42Beyond screen readers: fonts and zoom
- 15:07Pokémon shock incident safety
- 18:53Keyboard navigation in SPAs
- 20:22Ember’s accessibility solutions
- 22:09Why accessibility matters
- 23:53Web accessibility failure stats
- 24:55Tools and empathy for accessibility
- 26:00Call to action
related talks
27mCrafting Comics for Literally Everyone
31mCrafting Web Comics with Ember
34mCrafting Web Comics with Ember
28mCrafting Web Comics with Ember
01h 07mA web for anyone, anywhere, anytime
34mBuilding Accessible Web Apps in React
15mSweet, savory, and fresh! Accessible design system Storybook tests
46mExclusive design