Accessibility at Scale
Summary
1) Reliance on human testing which is especially complicated for large/dynamic products.
2) SaaS/Native app "release whenever you want" timelines.
3) Third party code/content managers.
4) Achieving "substantive WCAG conformance"
5) Closing the feedback loop by getting defects/feature requests from people with disabilities into the backlog.
6) Shifting the focus to an accessible experience, not just an accessible product.
Key Insights
-
•
Accessibility encompasses both visible and invisible disabilities, affecting roughly 30% of users via permanent, temporary, or situational impairments.
-
•
Assistive technologies communicate bidirectionally with software, requiring products to support this interaction cleanly to be accessible.
-
•
WCAG standards are the international source of truth for accessibility, with version 2.1 AA widely mandated and 3.0 on the horizon.
-
•
Automated tools catch about 30% of accessibility issues, machine learning tools currently only about 4%, leaving over half to human validation.
-
•
Making a product accessible initially is straightforward with resources and people; maintaining accessibility over time is far more complex and process-driven.
-
•
Scaling accessibility in cloud and continuous integration environments is challenging due to rapid, frequent software releases.
-
•
Integrating accessibility from the beginning into design, development, and definition of done prevents costly retrofitting later.
-
•
Organizational culture changes including executive buy-in, centralized resources, and accessibility champions are essential for scaling.
-
•
Hiring and retaining employees with disabilities and ensuring all workplace tools and events are accessible fosters inclusion and eases product accessibility efforts.
-
•
Accessibility defects should be treated like any other critical bugs and prioritized accordingly to ensure timely remediation.
Notable Quotes
"Accessibility isn’t just about visible disabilities; it’s about invisible disabilities and situational impairments too."
"Either you need accessibility now or you will need accessibility in the future."
"Assistive technology has to communicate with the destination, that’s your website or product."
"You’re not supposed to sell to the US public sector unless you’re WCAG 2.0 AA compliant."
"Getting something accessible is a straight line; keeping something accessible requires process change."
"Keeping something cloud-based accessible is the most complicated because of hundreds of releases per day in continuous integration."
"Accessibility at scale can put you into the VUCA world – volatile, uncertain, complex, ambiguous."
"You want to catch accessibility defects early through automated testing in your CI/CD pipeline, what we call shifting left."
"If you’re rewarding designers for delivering on time, great, but if you reward them for delivering accessible products on time, you’ll get better results."
"Accessibility defects are bugs. If it’s a P1 blocking bug for an accessibility issue, treat it like any other P1 bug."
Or choose a question:
More Videos
"Translation is a traitor because meaning is lost in translation between design and code."
Abby Covert Tomer SharonPanel: Collaboration Tools
November 6, 2017
"If you are a glue person expecting to be indispensable, you are more dispensable than you think. But if you’re a catalyst moving information and translating to action, that’s more valuable now."
John CutlerThe Alignment Trap
November 29, 2023
"Focus on the destination, not the vehicle, because AI tools will change every single day."
Erika FlowersAI-Readiness: Preparing NASA for a Data-Driven, Agile Future
June 10, 2025
"Our nervous system is ancient; it can’t tell the difference between an angry email and a tiger lurking."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 9, 2022
"Our job is to help others do great work, not to create perfect components for our own ego."
Dan DonaldDesign Systems as a Vehicle for Systemic Change
June 1, 2023
"Our digital swag bag is free to all registered attendees and packed with awesome sponsor offers."
Bria AlexanderOpening Remarks
June 9, 2021
"Trauma-informed approaches are like seat belts and airbags for tech products."
Carol Scott Melissa EgglestonAvoid Harming Your Team and Users: Promoting Care and Brand Reputation with Trauma-Informed UX Practices
February 5, 2025
"The most important thing you can do as a colleague, boss, or friend is ask what helps you work better."
Jessica NorrisADHD: A DesignOps Superpower
September 9, 2022
"Momentum is great, but without a disciplined system, things will go back to the way they were."
Kyria Stephens Marlon KernerPower to Heal: Civic Design in the Aftermath of Tragedy
November 17, 2022
