Accessibility matters
summary
Developer portals must meet WCAG-style rules: ARIA-labelledby for labels, color contrast tests for foreground/background, and keyboard-friendly skip links. Specifics: image alt text under 250 chars, link text must state file downloads, nav text around 16–18px and body 14–16px, avoid color-only cues, provide captions and transcripts, and use tools like alex.js to flag non-inclusive language. Accessibility is legal, benefits everyone, and requires ongoing audits and training.
AI-written summary · about
chapters (19)
- 0:00Start
- 1:48What is a developer portal?
- 2:20What is web accessibility?
- 2:40What disabilities?
- 2:57It's for everyone
- 3:43It's the law
- 4:07Principles of accessible content
- 4:50Parts of a website that need to be accessible
- 5:11Color
- 8:29Images
- 9:28Other media
- 10:08White space
- 10:40Screen readers and links
- 11:24More for screen readers
- 11:58Content structure
- 13:19Accessible language
- 14:04Inclusive language
- 17:29Summary
- 17:47Thank you!
related talks
01h 03mAccessibility: Making your websites more inclusive
22mWeb Accessibility - a better user experience for everyone!
48mThe Web Accessibility Basics
33mAccessibility Done Right
44mDesigning with Accessibility in Mind
41mAccessibility is a Requirement
01h 01mA web for anyone, anywhere, anytime
36mThe Human Side of Accessibility