Accessibility for Project Managers
summary
Project management guidance that demands concrete actions: prioritize WCAG 2.1 conformance in acceptance criteria, treat accessibility as ongoing work not a one-off, and budget time for manual review. Cites litigation rising from 814 federal suits in 2017 to over 2,000 the next year. Recommends tools like axe, WAVE, Siteimprove and the NoCoffee filter, enforces alt text (or explicit decorative flags) in CMSs such as Drupal 8, and phases remediation with crawl/walk/run plus quick wins like contrast and required alt tags.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:39LEARNING OBJECTIVES & OUTCOMES
- 2:01THE CASE FOR ACCESSIBILITY
- 5:31EMPATHY
- 5:43ACCESSIBILITY SUPPORTS SOCIAL INCLUSION
- 9:31LAWS AND GUIDELINES
- 12:03PUTTING PEOPLE AT THE CENTER OF THE PROCESS
- 14:20OPERABLE
- 15:29UNDERSTANDABLE
- 17:02ROBUST
- 17:35WCAG 2.1 LEVELS OF CONFORMANCE
- 18:42LOTS AND LOTS OF INFORMATION
- 19:29DRUPAL 8 ACCESSIBILITY FEATURES
- 20:12TOOLS AND TEST APPS
- 22:23HOW DO YOU CHANGE YOUR TEAM'S MINDSET
related talks
24mWeb Accessibility Strategies for Non-Accessible Projects
41mArchitecting for Accessibility
50mMaking a Strong Case for Accessibility
01h 03mAccessibility: Making your websites more inclusive
41mAccessibility is a Requirement
24mAccessibility needs better marketing
53mAccessing Accessible Accessibility
22mAccessibility in Practice