Typing Towards an Accessible Web
summary
Argues that type safety prevents common accessibility mistakes and shows concrete tools and code: static checks in Elm stop a clickable div compiling, an open-source package accessible-html enforces empty alt for decorative images and bans event listeners on noninteractive elements, integration tests with Capybara surface missing semantics, and the Elm stack runs in production for about 3.5 years at No Red Ink — the library exists, compiles, and blocks class of accessibility bugs before deployment.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:15Tessa Kelly
- 9:37Integration Tests
- 14:33Runtime Exceptions
- 18:21Accessible Html
- 20:57Alternatives to the Clickable Div
- 22:40Accessible Color Palettes
- 25:38Decorative Image Function
- 28:15Accessibility Best Practices
- 29:02What about Using Aria Attributes To Make a Clickable Div Accessible
- 31:03Does Accessible Html Also Give Direct Suggestions on How To Improve Accessibility Is It Open Source
- 31:45What Are some Ways We Can Determine Which Aspects of Our Application Are Not Accessible
related talks
26m"A Month of Accessible Elm"
26mAccessibility Is a Marathon, not a Sprint
28mAccessibility with Svelte - Beyond Compiler Warnings
41mAccessibility is a Requirement
52mCommon Accessibility Pitfalls
53mAutomating Accessibility Assurance
27mAccessibility, what do you eat that with?
31mDecoding web accessibility through testing