Highlights from our panel at Google Dev Group Mons with Julia Undeutsch, Emma Dawson, and Laura Wissiak on how companies can create truly inclusive products.
Originally published on my LinkedIn. Read a structured version here or listen to the space recording on X.
TL;DR
- Designers must embed accessibility into the blueprint.
- Skipping accessibility early costs far more later—both financially and legally.
- Every product should be inclusive; start with the disabilities most common in your user base.
- Aim for iterative improvement, not a mythical “100 % accessible” finish line.
🎙️ Who Was on the Panel?
- Julia Undeutsch – Accessibility strategist, known for her hands‑on design audits.
- Emma Dawson – Product lead, champion of cost‑effective, inclusive design.
- Laura Wissiak – User Experience Researcher for assistive technology.
The session was hosted by Google Developer Groups – Mons as part of the “Building for Everyone” series.
1️⃣ How Can Companies Ensure Their Products Are Accessible?
Julia’s Process:
- Audit Existing Knowledge – When joining a new team, first map out what the team already knows about accessibility.
- Empower the Designer – Designers create the product’s blueprints, so they must be fluent in accessibility fundamentals and annotate expected behaviours (e.g., ARIA roles, contrast requirements) directly in design files.
- Reduce Guesswork for Developers – Clear annotations mean developers don’t have to infer accessibility intent, cutting rework and errors.
Takeaway: Design is the gatekeeper. If accessibility is baked into the design stage, downstream implementation becomes smoother and cheaper.
2️⃣ The Core Argument for Investing in Accessibility
Emma’s Pitch:
“If you think you can’t afford accessibility at the start, you definitely can’t afford to retrofit it later.”
- Financial Angle: Retrofits often require extensive code rewrites, redesigns, and legal reviews—far pricier than proactive planning.
- Legislative Angle: Many jurisdictions (EU, US, Canada) now mandate compliance; non‑compliance risks fines and reputational damage.
- Human‑Centric Angle: While numbers matter, building for everyone is simply the right thing to do.
Bottom line: Cost‑of‑inaction > Cost‑of‑action.
3️⃣ Do All Products Need to Be Inclusive?
Laura's Answer: Absolutely.
- Start with Your Audience: Identify the most prevalent disability types among your users.
-
Example – Nutrition‑Tracking Service:
- Users may have type 2 diabetes, which can cause diabetic retinopathy (low vision) and neuropathy (motor impairments).
- Prioritise low‑vision and motor‑accessibility adjustments (large touch targets, high‑contrast UI, keyboard navigation).
This critical‑thinking exercise gives you a concrete entry point, after which you can expand research and iterate.
4️⃣ Myth‑Busting: “100 % Accessible” Doesn’t Exist
- No single standard declares a product fully accessible.
- As you learn more about diverse disabilities, new issues surface.
- Iterative Approach: Release, gather feedback (including from assistive‑technology users), refine, repeat.
Remember: Progress, not perfection, is the realistic goal.
Closing Thoughts
The panel reinforced three pillars for any organization:
- Design‑first accessibility – annotate, educate, and empower designers.
- Early investment – treat accessibility as a core requirement, not an afterthought.
- Iterative mindset – continuously improve based on real‑world usage and emerging knowledge.
Got questions about applying these ideas to your own product? Drop a comment below or reach out—happy to help you start building for everyone! 🚀
Original event: Google Developer Groups – Mons, Building for Everyone (6/6/2024).
Panelists: Julia Undeutsch, Emma Dawson, Laura Wissiak
Event Recording
Top comments (0)