Published in May 2018, WCAG 2.1 was the first major update to the WCAG standard in over 10 years. The update added a number of new Success Criteria primarily aimed at closing significant known gaps to address the needs of users with low vision, to address new concerns brought about by touch input and mobile screens, and to start to address the needs of people with cognitive disabilities.
One such new Success Criteria is SC 1.3.5 – Purpose of Controls.
But why? What are the real benefits of this requirement? How do I as a developer successfully meet that requirement? How and why did this Success Criteria come to be? As we started to ask people about their understanding of this requirement, there seemed to be some confusion. And confusion is never good.
In this presentation, John will do a deep-dive on SC 1.3.5: the history, the process, the blood-sweat-and-tears involved in getting a new Success Criteria through the WCAG process. We’ll look at the immediate benefit of this new Success Criteria today, as well as gain insight to the much larger goal that this Success Criteria kicks off. We’ll examine techniques (both current and future), and we’ll end up with a developer’s challenge – and there will be a prize!
John is the Principal Accessibility Strategist at Deque Systems and an internationally recognized Web Accessibility Specialist and advocate for the cause of web standards and universal accessibility. He has provided digital accessibility consultation services to government agencies, educational institutions and private sector companies since 1999.
John is an active and contributing participant in multiple W3C Working Groups and Task Forces, including the Accessibility Guidelines WG (formally the WCAG WG), Accessible Platform Architecture (APA) WG, the Web Platform WG (formally the HTML5 WG), as well as the W3C Television on the Web Interest Group. He is also an active contributor to the Personalization Task Force, the Pronunciation Task Force, and the “Project Silver” Task Force.