Skip to main content
Meytal Dahan
Back to insights

Accessibility in the Field Means Gloves, Glare, and One Free Hand

WCAG is the floor, not the ceiling — and for frontline apps, the standard compliance checklist misses the conditions that actually disable your users. I tell engineering leaders to design for situational accessibility alongside permanent disability, because in the field they collapse into the same requirements. A warehouse worker wearing gloves can't reliably hit a small tap target. A technician in direct sunlight can't read low-contrast gray-on-white. Someone on a loading dock has one free hand and a lot of ambient noise, so voice prompts fail and tap targets need to be large. These aren't edge cases; they're the daily operating environment. So I push for oversized touch targets, high-contrast modes that survive glare, large legible type, and workflows that prefer camera, QR, and a single confirming tap over multi-field forms. Screen reader support and proper focus order still matter — and they get easier when you've already minimized text entry. There's also a payoff R&D leaders care about: accessible-by-constraint design reduces input errors at the source, which means cleaner data flowing into your legacy HR and payroll systems and fewer support tickets. Build for the glove, the glare, and the one free hand, and you'll clear WCAG on the way.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Enterprise Mobile
CEOsSpecific Feature ROI

The ROI Hides in the Feature Nobody Mandated

CEOs often ask me to justify a B2E feature in isolation. Wrong frame. The mandated features get compliance, not adoption. The feature that gives the field worker something back — offline schedules, a camera report that kills minutes of typing, a payslip without a call to HR — is what makes them open the app at all. And once they open it, your mandated workflows finally get used. Don't price a feature by its own ROI. Price the adoption it unlocks across the whole product.

Read
Enterprise Mobile
Engineering Leaders

B2E Apps With Complex Integrations: How Do You Design Mobile-First So It Doesn't Break on Legacy Systems?

Engineering leaders on B2E apps: the challenge isn't the build – it's the integrations with legacy systems. In our enterprise mobile app project, we designed "Cached Display" for latency situations and full Offline Mode for field workers. Design + technical reality = an app that works in production.

Read
Enterprise Mobile
FoundersColor & Psychology

Color Earns Trust Before Your Feature Set Does

Founders ask me to make their enterprise app feel 'premium.' For field tools, the real job of color isn't premium — it's trust and legibility. Your user is a technician handed an app they didn't ask for. A restrained palette where color means something — synced, saved, done — tells them the tool respects their day. Never color alone (colorblind users, WCAG, harsh sun). Get it right and the app earns credibility in ten seconds. That's the window where adoption is won.

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.