Articles and Research

Questions about Implementing Accessibility in an Organization

In this episode of the podcast, Chad and Dax chat with Eugene Woo, CEO of Venngage, about the challenges and strategies for implementing accessibility in organizations. Eugene shares insights on how to approach gaining accessibility knowledge, the time it takes to integrate accessibility workflows, and effective ways to convince decision-makers to equip designers with the right tools. They also dive into how Venngage fosters a discoverable learning experience for users, leverages AI for generating alt-text, and integrates accessibility teaching directly into the design process. Plus, Eugene discusses balancing workload while ensuring accessibility and answers the burning question: how much accessibility is enough to avoid legal issues?

Listen to more Chax Chat Podcast Episodes

Guest Profile

Eugene is the CEO of Venngage, the first design platform to integrate built-in accessibility features that make visual communication both engaging and inclusive. With a background in engineering and planning, and a history of founding and scaling successful ventures, he brings a deep passion for innovation and accessible design. Eugene leads with the belief that design should empower everyone to share their ideas effectively.

Podcast Content

3:42 – Skip koi pond chat
5:43 – How to approach gaining accessibility knowledge
7:36 – How long does it take to implement an accessibility workflow into an organization
8:56 – What is the best way to implement accessibility in an organization
9:58 – The struggles of content creators in PowerPoint
10:59 – Setting the Reading Order (Tag Order) in Venngage
12:21 – How to convince the decision-maker to give designers the right tools
17:13 – Venngage model of a discoverable learning experience
19:23 – How to start down the road of accessibility knowledge
20:50 – Venngage leverages AI for generative Alt-text
26:43 – How Venngage teaches you about accessibility as you design
29:16 – Go vote to fix the latest bug in Acrobat
33:33 – How do you balance the workload and accessibility implementation?
37:03 – How much is enough accessibility to not get sued?