Summary
The outcome of designing at scale won't be accessible products unless accessibility practices scale in parallel with design. There are six primary challenges to scaling accessibility: 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 includes both visible and invisible disabilities, impacting around 30% of users permanently, temporarily, or situationally.
-
•
Assistive technology acts as a bridge between users and software, requiring products to properly communicate with these tools for effective accessibility.
-
•
The WCAG guidelines (levels A, AA, AAA) are the international standard for accessibility, with AA being the most widely adopted compliance target.
-
•
Only about 30% of accessibility issues can be reliably detected via automated code inspection, with 50-66% needing human validation, making scale challenging.
-
•
Maintaining accessibility is harder than achieving it once; without process integration, accessible products tend to become inaccessible within 9-12 months.
-
•
Scaling accessibility in a cloud-based environment is particularly complex due to hundreds of deployments and continuous integration.
-
•
Embedding accessibility into the entire DevOps pipeline early (shift-left testing) dramatically reduces defects and improves outcomes.
-
•
Having accessibility embedded in hiring, onboarding, and retention processes fosters greater inclusion and improves organizational maturity.
-
•
Executive sponsorship, centralized resources, and local accessibility champions are essential for growing accessibility programs at scale.
-
•
Treating accessibility bugs as P1 (critical) issues and avoiding checkbox compliance leads to more meaningful and lasting accessibility.
Notable Quotes
"Either you need accessibility now or you will need accessibility in the future."
"About 30% of most user audiences have permanent, temporary, or situational disabilities."
"Assistive technology has to communicate with your product; if this communication breaks, accessibility fails."
"Getting something accessible is a straight line and a check-engineering problem; keeping it accessible requires process change."
"Cloud-based accessibility is the most complicated because of continuous integration and hundreds of releases per day or week."
"If you get a product accessible but don’t embed accessibility process changes, it will revert to inaccessible in 9 to 12 months."
"Accessibility has to be part of every product conversation, minimum viable product, and definition of done."
"People with disabilities are tired of complaining; 91% leave for more accessible competitors without giving feedback."
"Accessibility is a civil right under the Americans with Disabilities Act, but if you need a business case, 18% of users have disabilities."
"Don’t use overlays or checklists; they only offer a narrow perspective instead of holistic accessibility."
Or choose a question:
More Videos
"Can you show me your process, not just your portfolio? That shows me your real design thinking."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Many product managers got their roles because they know the business or subject matter, but they don’t know how to manage product development."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Governance frameworks can facilitate whatever an organization wants to do, fast or slow, loose or tight."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Green spaces in cities can greatly enhance our quality of life and resilience."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"It matters what you build, but it matters more if you learn."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Thick data is the opposite of big data; it’s stories, qualitative, and crucial during moments of rapid change."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"We used a Python algorithm with a correlation matrix to identify meaningful clusters from survey responses."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"The toy shouldn’t be the goal of play, but a tool or a process that unlocks the unlimited possibilities set forth before a child."
Designing Systems at Scale
November 7, 2018
"Most product teams work linearly, but systems thinking captures the real-world complexity of moving forward and sometimes stepping back."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
