A design canvas with two app screens, where a button is dragged from the component library into the payment screen.

We start with who uses the product and what they are trying to do, then design the flows and screens that get them there. The result is a design system: components, rules and tokens that developers build from without guessing. We also run accessibility reviews, including European Accessibility Act audits, so you know where the product falls short of the Act as well as where it falls short for your users.

A good fit if

  • Conversion or activation is stuck, and nobody knows why.
  • You sell to consumers in the EU and haven't checked accessibility since June 2025.
  • Screens drift apart as the team grows, and developers guess at the UI.
  • An AI-generated interface looks like every other app.

Not the right start if

The same six errors, on almost every site

Pick an error to see what it breaks, and the design system rule that stops it reaching your product.

Sign up for Lumen

We'll never share your email.

A screen reader says: "Sign up for Lumen, heading. Email, edit text. Create account, button." The rule that prevents these errors: every component ships with its name, label and contrast built in.

Every case

All fixed
A screen reader says: "Sign up for Lumen, heading. Email, edit text. Create account, button." The rule that prevents these errors: every component ships with its name, label and contrast built in.
Low-contrast text
The helper text drops to 2.8:1 contrast, and a screen reader hears no difference. It is hard to read for anyone with low vision, or anyone outside in sunlight. The rule that prevents it: text colors exist only at 4.5:1 or more, so this one can't be picked.
Missing alt text
A screen reader says: "logo-final-v2.png, image." The rule that prevents it: the image component needs alt text, or an explicit decorative setting.
Unlabeled field
A screen reader says: "Edit text, blank." The rule that prevents it: the field component has no version without a label.
Empty link
A screen reader says: "Link." The rule that prevents it: icon links take a required name.
Empty button
A screen reader says: "Button." The rule that prevents it: icon buttons take a required label.
Missing language
A screen reader reads the page with the wrong pronunciation. The rule that prevents it: the page template always sets the language.

95.9% Share of the top million home pages with detectable WCAG failures in WebAIM's 2026 scan. WebAIM Million, 2026

How it runs

  1. 01 of 08

    Plan the research.

    The questions, the people we need and the methods, on one page.

    You keep A research plan.

  2. 02 of 08

    Talk to users.

    Interviews or watching people work, about five to eight of them.

    You keep Notes, clips and an affinity map.

  3. 03 of 08

    Make sense of it.

    What people are trying to do and where they get stuck.

    You keep A journey map with the pain points marked.

  4. 04 of 08

    Flows and structure.

    How people move through the product, before any screen is styled.

    You keep Flow diagrams and a sitemap.

  5. 05 of 08

    Prototype.

    Clickable screens, or a coded prototype where the interaction is the question.

    You keep The prototype.

  6. 06 of 08

    Test in rounds.

    Five people per round, two or three rounds, with fixes between.

    You keep A findings log with severity and what changed.

  7. 07 of 08

    The design system.

    Every screen in every state, then tokens and components in Figma and in code.

    You keep The token file, the Figma library and coded components.

  8. 08 of 08

    Audit and build support.

    A WCAG 2.2 AA audit, then design reviews as developers build.

    You keep The audit, the fixes and a draft accessibility statement.

Small errors, repeated on every screen

  1. Accessibility failures.

    The same few errors keep shipping because nothing in the system stops them.

    Prevented in step 7
  2. Checkout friction.

    People abandon at steps nobody tested.

    Prevented in step 6
  3. Designs developers can't build from.

    No empty, error or loading states, so developers guess.

    Prevented in step 7

95.9%

Share of the top million home pages with detectable WCAG failures in WebAIM's 2026 scan.

WebAIM Million, 2026Checked Nov 2026

€500 a day

The penalty a French court set in June 2026 if Carrefour's online shop wasn't made fully accessible within six months.

Accessiway report on the Caen ruling, 2026Checked Nov 2026

What you keep

  • User research and flows

    Interviews and task flows that show where people get stuck.

  • Clickable prototype

    A realistic model to test with users before any code.

  • Design system

    Components, spacing, color and type, documented for developers.

  • Usability testing

    Sessions with real users and a written list of what to fix.

  • European Accessibility Act audit

    A review of your product against the accessibility requirements, with fixes ranked by impact.

Done means

  • Tested flows and screens in every state: empty, error and loading.
  • Tokens and components in both Figma and code.
  • A WCAG 2.2 AA audit with no open blockers.
  • A findings log showing what users struggled with and what changed.
  • Your developers can build a new screen without asking us.

Sample

Usability findings log

Round 2, finding 43 of 5 people missed the plan switcher
SeverityHigh: it blocks upgrading
ChangeMoved the switcher next to the price, and named it
Round 3 result5 of 5 found it
Illustrative values, not a client result.

Questions about UI/UX & Product Design

Still deciding?

Ask the people who would build it. We reply within one business day.

Both. You can take the designs to your own developers, or we build them. Either way the design system is yours.

AI drafts layouts in minutes, and we use it for that. But in Nielsen Norman Group's 2025 tests the output was "good from afar, but far from good": knowing what your users need still takes research and testing.

We test your product against WCAG 2.2 AA, the level the updated European standard EN 301 549 points to, with a keyboard and a screen reader, and give you a ranked list of fixes. It's an audit of your product, not a legal opinion, and no "EAA certificate" exists.

Because three rounds of five, with fixes between them, find more than one round of fifteen. For numbers you can quote, such as success rates, we test with 20 or more.

Not while the product's shape is still changing or the team is tiny. We pull one out of the screens once repeated decisions start costing time.

Yes. We test the prototype with people who match your audience, and we say in the report how many we spoke to, so you can judge how far to trust the result.

Have an idea or a stuck project? Let's talk.

We reply within one business day. If we're not the right team, we'll say so on the first call.

On the first call

  • What users struggle with today, and how you know.
  • Who your users are, and where.
  • Whether you sell to consumers in the EU.