Meytal Dahan
Back to insights

A Design System That Survives an Accessibility Audit

Government & Public SectorEngineering LeadersDesign SystemsGovTech
In govtech, a design system isn't a nicety for designers — it's risk management your engineering org can bank on. When WCAG conformance is a legal requirement rather than a stretch goal, you cannot afford to relitigate contrast ratios, focus states, and keyboard traps on every screen. So I build accessibility into the component layer itself: an accessible button, field, and modal that ship correct-by-default, so a developer can't easily make them non-conformant. That moves compliance left, out of QA firefighting and into the primitives. For an R&D leader, the payoff is throughput. Tokens for color, spacing, and type mean a citizen-facing service and an internal caseworker tool stay coherent without a coordination tax. It also de-risks i18n — components built for RTL, long German compounds, and dynamic text scaling from day one don't get re-engineered per locale. I keep the system deliberately mature and un-flashy: documented states, versioned changes, deprecation notices. The goal is a foundation that a new engineer can adopt in a sprint and that survives external scrutiny, audits, and the next administration's roadmap — not a library that looks impressive in a demo and fractures under real public load.
Explore selected work

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Government & Public Sector
FoundersFrom MVP to Full Version

Why GovTech MVPs Don't Look Like Startup MVPs

Founders are taught to ship the scrappiest MVP and iterate in public. In govtech, that instinct can sink you. A citizen service that looks like a beta — or breaks for a screen reader user — loses trust you may never win back. So I redefine 'minimum': not a thin slice of everything, but one complete, accessible, end-to-end path a real person can finish with dignity. Narrow the use cases brutally. Never narrow the quality. Then grow in concentric circles — keep the simple core intact, layer depth around it. Your launch version should be something you'd defend in a public hearing. That's the bar.

Read
Government & Public Sector
CEOsPersonalization & Tailored Models

Personalization That Survives Public Scrutiny

When CEOs hear 'personalization' they picture a consumer feed that learns you. In a public service, that's a liability — citizens didn't opt into being profiled, and any hint of differential treatment invites fairness questions you don't want to answer in public. So I reframe it as relevance, not prediction. Not a model guessing what you want — a service showing each person only what actually applies to them, driven by their situation, not surveillance. A parent sees the parent path. Someone who already applied sees status, not a fresh form. That cuts confusion and call volume, and every tailoring decision stays explainable. The efficiency of personalization, without the consumer-playbook downside.

Read
Government & Public Sector
Project ManagersUsability Testing

Usability Testing as Schedule Insurance for Public Services

Usability testing isn't a threat to your timeline — it's insurance on it. The costly defects aren't the ones found in a session; they're the ones found after launch when the fix means re-planning everyone's quarter. Test early, test on the worst device, and label every finding by whether it blocks the core task. A PMO can schedule around that. It can't schedule around surprises.

Read
Meytal Dahan

About

Making complicated into easy for users.

Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.