Close Encounters of an Inclusive Design: A Case Study Introducing IDX into One Compan...
summary
Company migrates a desktop land‑registration product to web and injects inclusive design by forming a cross‑functional working group, mapping AODA and WCAG requirements into an explicit checklist, and pairing automated scans with manual QA and device testing. Developers implement keyboard accessibility and focus management, merge error messages into field labels and removed redundant asterisk behavior, test across five major browsers and JAWS NVDA VoiceOver, and defer complex map accessibility as maps deferred to later project while noting improved keyboard workflows for law‑clerk users.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:41Start with Joint High Level Understanding
- 7:58Create A Team
- 9:22Understand & Define High Level Requirements
- 13:26Create a List of What You Don't Know
- 19:08Build into Implementation and Testing
- 21:49Some Primary Lessons Learned
related talks
51mThe Intersection Of Accessibility And Inclusive Design
44mOut with accessibility - In with inclusive design
46mExclusive design
01h 02mAccessibility - how to get the job done in a highly collaborative manner
12mAccessibility-First Development: Making Applications Inclusive from Day One
15mBeyond Compliance Creating Inclusive and Usable Digital Products
44mDesigning with Accessibility in Mind
32mEmbracing usability and accessibility: a Pace case study