Be an ally! In the battle for an inclusive and accessible internet!
summary
States that 15 percent of people worldwide roughly one billion rely on assistive tech and gives concrete rules: use native HTML elements not divs for buttons, always provide alt text, keep content order rather than rearranging with CSS, and prefer tabindex 0 and -1 not positive values. Implement ARIA for role name state and value and use aria-live polite/assertive carefully while still coding keyboard handlers. Test with Chrome Accessibility Inspector and Lighthouse and enforce fixes via static analysis (tslint/ng‑lint) in CI and manual screen‑reader checks.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:42What is accessibility
- 4:49Content structure
- 6:10Alternative text
- 6:39Native elements
- 9:17Takeaways
- 12:27Checkbox
- 14:21assertive or polite
- 15:19add keyboard support
- 17:17checklist
- 17:44tab index
- 18:10enhanced navigation
- 19:21AA Success Criteria
- 21:54Manual audits
- 22:38Chrome accessibility inspector
related talks
33mAccessibility Done Right
26mMake the internet a better place - with coding for accessibility
35mAccelerating accessibility in web
01h 07mA web for anyone, anywhere, anytime
45mA Web for Anyone, Anywhere, Anytime
01h 01mA web for anyone, anywhere, anytime
36mThe Human Side of Accessibility
52mCommon Accessibility Pitfalls