Accessible Development: Customize Only When Necessary
summary
The talk examines building web and mobile apps with highly customized UI components and warns that creating bespoke controls instead of using native or widely adopted framework components often leads to inaccessible and lower-quality solutions. It argues for customizing only when necessary and highlights accessibility risks of overly custom implementations.
AI-written summary · about
chapters (7)
- 0:00Accessibility introduction
- 3:12Standards vs customization
- 11:58Date picker usability
- 17:01Megamenus complexity
- 23:33Carousels semantics
- 31:13Nested components semantics
- 35:13Q&A
related talks
40mAccessibility: What If We Let Users Customize ...
50mAccessible App Design
48mBeyond Default Boundaries: Designing Accessible Non‑Standard Components
55mAccessible Wow Effect
39mElegant Accessibility
12mAccessibility-First Development: Making Applications Inclusive from Day One
57mAccessible Development: Where We Are and Where We’re Going
35mAccelerating accessibility in web