Accessibility statement
Last updated: 19 May 2026
nlit is committed to making translation management usable for everyone, including people who rely on assistive technologies. This statement explains the standard we aim for, where we currently fall short, and how to tell us about a barrier so we can fix it.
The standard
We aim for Web Content Accessibility Guidelines (WCAG) 2.1 Level AA across the nlit web application and marketing site. This is the standard referenced by the EU Web Accessibility Directive and adopted by the European Accessibility Act (EAA), which applies to digital services offered to EU consumers from 28 June 2025.
Conformance status
nlit is partially conformantwith WCAG 2.1 AA. “Partially conformant” means that some parts of the content do not fully meet the standard, as honestly listed below. We will not claim full conformance until an external audit confirms it.
Known gaps
The following areas are currently not fully accessible and are tracked for improvement:
- Keyboard navigationthrough the translation editor's plural-form rows can require a high tab count. We are evaluating a roving-tab-index pattern.
- Colour-contrast on certain status badges (Approved ✓ chip, AI chip) falls in the 3.5:1–4.0:1 range against the surrounding surface in dark mode — short of the 4.5:1 WCAG 2.1 AA target for normal text. The text size is small (10–12px) which makes the gap more visible. A palette pass is queued.
- Screen-reader announcements for live regions (auto-save toasts, “Approved” confirmations) are not yet wired with
aria-live. Users on screen readers may miss feedback after saving. - Reduced-motion preferences are honoured for most animations, but a few hover-only transitions in the marketing pages still run regardless of
prefers-reduced-motion.
This list is not exhaustive. As we audit more pages we will add and remove items here; the “Last updated” date at the top reflects when the list was last revised.
What we have done
- Semantic HTML throughout (headings in order, lists for lists, native form controls, real buttons).
- Form labels associated with inputs via
htmlFor+id; visible focus rings on all interactive elements. - Native browser language inheritance via
langattributes on text blocks where translation language is fixed. - Page titles and metadata that reflect the page contents, so screen-reader users can orient themselves quickly.
- Light and dark themes that both pass WCAG 2.1 AA contrast for body text.
Tell us about a barrier
If you encounter a part of nlit that is not accessible to you, please tell us — your report is the fastest way for us to fix it. Email support@nlit.app with a description of the issue, the page you were on, and the assistive technology you were using. We aim to acknowledge accessibility reports within 5 working days and to fix or document a workaround within 30 days.
Enforcement
In Sweden, accessibility complaints about digital services can be escalated to the Swedish Agency for Digital Government (Digg). Other EU member states have equivalent national bodies.
Also see our Privacy Policy and Terms of Service.