Skip to main content
Meytal Dahan
Back to insights

Accessibility for a Spatial Configurator That Isn't a Shop-Floor Tool

Zammit — Designed the Retail Shelving Planning System - the platform's most demanding configurator, where every dimension, shelf, edge profile, and placement rule is defined - into a spatial design tool retail professionals could use without CAD knowledge.
Accessibility conversations about manufacturing software often jump straight to ruggedized touchscreens and gloves. Zammit deliberately wasn't that. There were no shop-floor operators, no offline-mode requirements — the users were engineers, architects, contractors and retail professionals doing digital procurement on web and mobile. That reframes accessibility for an R&D leader entirely. The hard problem here was cognitive and spatial, not environmental. The flagship Retail Shelving Planner asked people to configure dimensions, shelf count, edge profiles, and per-shelf depth and placement — a genuinely spatial task — explicitly without CAD knowledge. Industry-specific accessibility, in that context, means the spatial model must be legible to someone who has never read a technical drawing: clear feedback when a configuration violates a manufacturing rule, units and terminology that don't assume domain fluency, and interaction patterns that degrade gracefully from desktop to a smaller mobile viewport. Standard WCAG concerns — contrast, focus order, input alternatives for a visual configurator — still apply and matter more, not less, when the core interaction is spatial. The principle I hold: accessibility isn't only about disability accommodation; in a domain like this it's also about not gatekeeping a complex purchase behind expertise the user was never required to have.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Zammit
Project ManagersUsability Testing

Testing a Spatial Configurator Without CAD

On Zammit's shelving configurator, we asked people to lay out custom shelving — dimensions, shelf count, depth, placement — with zero CAD knowledge. That is a usability risk you cannot hand-wave. So I ran testing as a recurring checkpoint tied to delivery milestones, not a one-off before launch. The payoff is for project managers as much as designers: testing turns a scary, vague risk ('can buyers do this without a salesperson?') into specific, scheduled, fixable issues. And inside an engine with real constraints, testing early tells you which problems are worth engineering time and which a better sequence solves for free. Predictability beats surprises.

Read
Zammit
Product ManagersMicro-interactions & Animation

Micro-interactions That Made an Engine's Rules Feel Like Feedback

Rule-heavy configurators feel like the system is fighting you — unless feedback shows why. On Zammit, micro-interactions turned the engine's logic into a conversation: a value recalculating, the summary shifting, an invalid option visibly settling out of reach instead of vanishing. PMs, the test for every animation: does it explain the system's behavior, or just decorate it? Only the former protects flow completion.

Read
Zammit
Project ManagersDelivery & Handoff to Development

Handing Off 40 Configurators Without Losing the Thread

Handing off ~40 configurators, 25 e-commerce flows, and 6 onepagers — solo, over ~2 years — taught me that handoff isn't an event, it's a rhythm. At that volume the real risk a project manager loses sleep over is drift: checkout behaving one way here, another way there. My defense was deliberate pattern reuse and handing off the decision logic, not just visuals — especially for configurators bound to the DriveWorks engine's rules. Shared patterns are schedule insurance: estimates hold, review cycles shrink, and developers implement without guessing. Clear intent plus clear constraints beats a backlog of clarifying questions every time.

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.