Accessibility has traditionally only factored in the last stages of the Product Development Life Cycle: if the developer decides to build responsibly, if the QA team catches an issue, or in the worst case scenario: if the company is sued by a customer after launch. However, accessibility and inclusive thinking really starts long before the first wireframe is sketched out or a single line of code is ever written. In this talk, I shared practical tips on how designers & content strategists can start capturing the 'subjective' aspects of accessibility in designs to take the guessing out of our developer and QA friends' work.
My presentation references Elle Waters' survey on why designers and developers do not factor accessibility in their work.
Referenced during my talk at the a11yTO Conference
Please note: As of October 18 2018, this does not include WCAG 2.1 updates.