Accessibility

We want meruma to be usable with a screen reader, with the keyboard alone, with enlarged text, and with colour vision that differs from the norm. This page says where we stand.

The standard we follow

We use the Web Content Accessibility Guidelines (WCAG) 2.2, level AA as our reference. We do not claim certified conformance: we state that this is the goal and that we work against it.

What is already done

• Contrast: the brand palette is built to meet level AA. Every colour-and-background pair was verified, and the accent green is not used as text colour precisely because it fell short of the minimum.
• Never colour alone: success, error and warning states always carry an icon as well as the colour, because in deuteranopia green and red look too much alike.
• Underlined links inside body text, for the same reason.
• Keyboard: the site and the application can be navigated with the tab key, focus is visible, menus open and close from the keyboard, and Escape closes whatever is open.
• Skip to content: the first element on every page is a link that skips the header, visible when you arrive with the keyboard.
• Semantics: headings in order, lists that are lists, tables with declared headers, and form fields with associated labels.
• Motion: entrance animations switch themselves off when the system has reduced-motion turned on.
• Text: it can be enlarged without the interface breaking, and we do not use images of text.

What we know is missing

We would rather say it:

• We have not run an external accessibility audit, nor systematic testing with screen reader users.
• Some dense parts of the application — the drag-and-drop pipeline board, the form builder and the site editor — have keyboard alternatives, but their screen reader experience is not polished.
• Files uploaded by our customers (documents, images, recordings) are outside our control: their accessibility depends on whoever created them.

If something does not work for you

Write to info@meruma.app with “Accessibility” as the subject, telling us which page or feature blocked you and with what assistive technology. We reply and, where we can, offer an alternative while we fix it.

It is the fastest route to getting it fixed: one concrete report is worth more than a generic audit.