Skip to content

Radix UI

An app everyone can use,
keyboard and screen reader included

Radix UI is a set of ready-made interface parts, such as menus, dialogs, dropdowns and tabs, that support the keyboard and screen readers from the start. Choose it when your app or site has to meet WCAG 2.1 AA and still look exactly like your brand.

Free 30-minute call · We usually get back to you within a few hours on business days

What Radix UI is and when to choose it

The hardest parts of accessibility are elements that open and close: menus, dialogs, tooltips, calendars. Built from scratch, they often don’t work with a keyboard or lose the screen reader. Radix UI provides proven behaviour for these parts, and the look follows your brand. For you that means fewer fixes during accessibility checks and an app more people can use.

What you gain

  • 01

    Keyboard support

    Menus, dialogs and lists work with Tab, Enter, Esc and the arrow keys, just as users expect.

  • 02

    Screen readers

    Elements have the right roles and labels, so a blind user knows what is open and where the focus is.

  • 03

    Your brand’s look

    Radix doesn’t impose a look. Colours, typefaces and shapes are yours, while the behaviour stays proven.

  • 04

    Fewer fixes before sign-off

    Accessibility is built into the parts from the start, not patched in at the end of the project when it costs the most.

How we work with Radix UI

We check accessibility while we build, not only when the project is handed over.

  • 01

    Build

    • Menus, dialogs, tabs and dropdowns on Radix UI
    • The look of your brand
    • Contrast and sizes in line with WCAG 2.1 AA
  • 02

    Checks

    • Automated accessibility tests
    • Going through the app with the keyboard alone
    • Key screens checked with a screen reader
  • 03

    After launch

    • New features built to the same rules
    • Fixes for issues users report
    • Component updates

When Radix UI is a good choice

  • An app or portal that has to meet WCAG 2.1 AA
  • An admin panel with many dialogs, menus and forms
  • A consumer service covered by the European Accessibility Act
  • A website for a public body, nonprofit or medical practice
  • An app where customers have reported usability problems

When we’d choose something else

  • A PrestaShop shop with a ready-made theme: there we improve accessibility in the theme
  • A site without dropdowns or dialogs: well-written HTML is enough
  • An app installed from an app store: there we rely on the accessibility built into the phone’s system

See also: React, Tailwind CSS

Accessibility in practice

A project where accessibility was a requirement from day one, not a fix at the end.

Frequently asked questions

Is Radix UI enough to meet WCAG?
Not on its own. Radix takes care of how menus, dialogs and lists behave, but accessibility also covers contrast, content, image descriptions and forms. So we check the whole app, and Radix saves the most work on the hardest parts.
Does accessibility cost extra?
No. We build WCAG 2.1 AA accessibility into every project from day one, at no extra charge.
Can you improve the accessibility of an existing app?
Yes. We first find which elements cause problems, then start the fixes with the screens your customers use most.

Want an app everyone can use?

Show us the site or describe the app. On a call we’ll tell you what to fix first and how to do it without rebuilding everything.

The button opens a short form: a link or a few sentences is enough. We usually get back to you within a few hours on business days and, if a call would help, suggest a free 30 minutes. You get a written quote for the scope before you decide anything.

See custom software

Not ready for a call? Start with a free website check: give us the address and within 48 hours you get a PDF report with the three key fixes.

Data stored on EU servers · GDPR-aligned · WCAG 2.1 AA accessibility · You own the code and the copyright