Steve Barnett / Getting “Accessibility Ready” for a Design System скачать в хорошем качестве

Steve Barnett / Getting “Accessibility Ready” for a Design System

Design systems help teams make more accessible products and services. How do we ensure the components in our design system are as accessible as possible? We'll use an example to show what "Accessibility Ready" means for components in a design system. What makes a good "Accessibility Ready" guidance document? What are the minimum requirements for release, plus additional internal requirements for quality, to ensure a component is "Accessibility Ready"? Why keep the document short? (Using the Supported Technology section as an example) About the speaker Steve is a human-centred front-end developer and user experience designer. He helps software teams have happier customers by making more user-friendly and engaging software. He’s been building things for the web professionally since 2005 (and built things for fun for a while before that). Accessibility has been a part of his work for many years, but now it’s part of his job title too! He makes sites and apps that everyone can use, regardless of their device, the network they’re on, or any disabilities they may have. https://inclusivedesign24.org