Accessibility Statement

Nemi is made by GuusLab, a one person company in the Netherlands. This page says how accessible Nemi is today, what you can change to suit how you read and work, what we already know is difficult, and how to tell us when you hit something that is not on the list.

The European Accessibility Act applies from 28 June 2025, and it exempts a microenterprise that provides services from its requirements. We are that size, so the statement you are reading is not one we are obliged to publish. We publish it because the exemption is about paperwork and reporting, not about whether a person can use the product, and because a promise nobody wrote down is not a promise.

We aim at WCAG 2.1 level AA, and Nemi is partially conformant with it. Partially conformant means most of the product meets the standard and some parts do not yet. Section 4 lists the parts we know about.

We are saying partially rather than fully for a reason worth being plain about: Nemi has not had an independent accessibility audit. Our assessment is our own, made by testing with a keyboard, with the operating system's own accessibility settings, and with screen readers on the browsers we support. That is honest work and it is not the same as an audit, so we do not describe it as one.

Some of this is built into the interface and needs nothing from you.

• Colour is never the only carrier. A status, a ring around a profile photo, a chart band or a badge always states in words what the colour says, in the visible text or for a screen reader.
• Controls are large enough to hit. Buttons, checkboxes and menu rows are built from one set of sizes that clears the WCAG target size floor, rather than each screen picking its own.
• Your system settings are honoured. Reduced motion, increased contrast and keyboard focus set in your operating system are picked up by Nemi without you configuring anything here.
• Page changes are announced. Moving to a new page and the status messages that follow an action are read out to a screen reader.

The rest is yours to set. Open Settings, Accessibility, or press Alt Shift A anywhere in the app for the quick panel. There is no save button and no separate mode to turn on: you change a setting and look at the result.

• Text size at 100, 110, 125, 150, 175 or 200 percent. Nemi scales the type and leaves the layout in place rather than zooming the page, so larger text gives you roomier reading instead of content pushed off the edge.
• Contrast at System, More or High.
• Motion, to remove animation and page transitions even when your device does not ask for it.
• Underlined links, reading spacing, a bold focus ring that shows for pointer and switch input and not only for the Tab key, a highlighted focus row, larger tap targets and reduced transparency.

These settings are stored on your device, so they carry across the parts of Nemi, and on your account, so they reach your next device as soon as you sign in. They are applied before the page draws, which is why a page never appears at the default size and then jumps. The help centre goes through each one with what it changes.

This is the part of the page that is actually worth reading. These are real and current.

• No independent audit. Nothing here has been verified by anyone outside GuusLab, so there are certainly problems we have not found. That is the single biggest limitation on this page.
• The editors capture their own keyboard shortcuts. While you are typing in a document, a spreadsheet or a canvas, Alt Shift A may be taken by the editor instead of opening the accessibility panel. Press Escape first.
• A canvas is a drawing. Freehand work on a canvas, and a whiteboard in a meeting, have no automatic text alternative, and a screen reader cannot describe them. If a canvas has to be readable by everyone, put the same information in a document.
• Meetings do not always have captions. Live captions in Meet are switched on by the host, for each meeting, and the hours are limited by the host's plan. A participant cannot turn them on for themselves, so a call you join may have none.
• We are not responsible for what people put in Nemi. A PDF, an image, a video or a document someone uploads or shares with you is their content. A scanned PDF with no text layer and a video with no subtitles stay inaccessible inside Nemi, because Nemi passes the file through rather than rewriting it.
• A share page is laid out by the sender. The page a recipient sees behind a download link is designed by the person who sent it. We hold the structure to a readable order and a single reading sequence, but we do not control what they wrote or which blocks they chose.

Email support@nemilab.com. Accessibility reports are treated as bugs, not as feature requests, and they are not put behind other work because of how many people they affect.

Three things make a report much faster to act on:

• Which screen you were on, and what you were trying to do.
• Which assistive technology, if any, and which browser. A screen reader and a browser together usually identify the cause on their own.
• What you expected instead. Text that ignores the size setting, a control you cannot reach with the Tab key and a label a screen reader does not announce are all bugs worth reporting.

You get a reply within two business days. If a fix is going to take longer than that, we will say what we are doing and whether there is a way around it in the meantime.

If you are not satisfied with how we answer, you can raise it with the Dutch consumer authority, the Autoriteit Consument en Markt, which supervises the Accessibility Act in the Netherlands.