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
"A regular heartbeat and familiar structure are really important principles to keep a community alive."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"Most of the primitives of how you do work are portable to climate tech from other industries."
Dem Gerolemou Alexis Oh Neef RehmanClimate technology fundamentals
May 15, 2024
"Doing at least two benchmarking rounds lets you see if optimizations have measurable impacts over time."
Daniela Magaña Flores Ariane Rahn Jeff Ephraim BanderAhead of Competition: Learn What UX Benchmarking Can Do for Your Business Today
March 10, 2022
"I got a no. The message I was hearing was, scale the best you can with what you have and make it work."
Abbey Smalley Sylas SouzaScaling UX Past the Size of Your Team
January 8, 2024
"We created a tiers of support model so even low priority projects get some level of guidance, even if just a 45-minute consultation."
Patrick CommarfordDesign Staffing for Impact
January 8, 2024
"We mapped every individual journey on Google Earth attaching quotations and photographs to each location to represent human experiences."
Xenia Adjoubei Sean BruceEmpowering Communities Through the Researcher in Residence Program
March 29, 2023
"If going from no design system to a system, you should see an increase in product development efficiency by at least 25%."
Craig VillamorDesign Systems for Ethical Design
January 26, 2023
"User research is really only part of the information schema that we’re talking about."
Jon Fukuda Ellie KryslDesign Planning and Management Support
October 3, 2023
"31% say design just executes product’s vision, 48% say product and design have different visions, only 21% say they work together towards shared goals."
Iain McMaster IHan ChengDesign and Product: from Frenemy to Harmony
November 29, 2023
