Development for all the people
summary
Claims that accessibility often requires only a few lines of code and yields big gains backed by real user counts and an experiment are shown with concrete fixes: set accessibilityLabel and traits, implement UIAccessibilityContainer for complex cells, enable VoiceOver and Dynamic Type, and use the Accessibility Inspector and automated audit. Notes include Apple listing 31 accessibility features, contrast ratios (3:1 large text, 4.5:1 regular), 44×44 tap targets, an Amazon product page failure and an ecobee slider fixed in five lines. Test with screen curtain / blindfold test.
AI-written summary · about
chapters (18)
- 0:00Accessibility in development
- 3:22Why accessibility matters
- 7:14Accessibility needs overview
- 11:52Visual info accessibility
- 16:51Common app failures
- 19:21Accessibility needs desires
- 20:02Key accessibility tech
- 24:08Amazon’s accessibility fixes
- 27:40Advanced accessibility features
- 28:44Dynamic type support
- 30:49Accessibility design tips
- 33:59Testing with VoiceOver
- 37:17Screen curtain testing
- 38:20Xcode inspector overview
- 39:24Top five accessibility tests
- 41:19Examples of accessible apps
- 43:14Thinking outside the box for accessibility
- 44:56Key takeaways
related talks
44mCrafting Great Accessible Experiences
29mInclusive and Accessible App Development
31mAccessibility for the App You're About to Ship
40mAccess to Tech, Tech to Live
21mAccessibility 101: Getting started with assistive technology and product inclusion
33mAccessibility needs to be the future of better technology
28mBuilding an Accessibility Culture, One Step at a Time
35mAccessibility in Action