Accessibility – Proven, Easy Integration into Design and Development Workflows
summary
Web accessibility is practical not mystical: about 20% of Americans have disabilities and spend roughly $175 billion annually, so aim for WCAG 2.0 levels A/AA (not just vague promises). Bake accessibility into contracts, map WCAG criteria to roles, test early with keyboard and real users, and automate checks with tools like WP Accessibility plugin, Access Monitor (Tenon/10on API), quail and color contrast analyzers. Follow concrete rules: semantic HTML, alt text best practices, readable grade ~8, clear focus and error states, and caption/video transcripts.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 1:05Why accessibility matters
- 4:45Accessibility as an afterthought
- 5:27Roles in project accessibility
- 7:54Understanding WCAG guidelines
- 10:22Accessible content best practices
- 15:41Designing for accessibility
- 19:17Simulating low vision in design
- 20:22Development with web standards
- 23:52Keyboard accessibility and testing
- 24:14Accessible WordPress themes
- 25:41Accessible plugins and core
- 26:23Q&A session begins
