Accessibility statement

1. What we are aiming at

Nesso is used standing in somebody else’s flat, on a phone, often in poor light and in a hurry. That is a demanding context for everybody, and an excluding one if the interface assumes a steady hand, sharp eyes or a mouse. We treat accessibility as part of whether the product works at all.

We hold Nesso to the Web Content Accessibility Guidelines 2.1 at level AA, which is the standard EN 301 549 refers to and the one European accessibility law is built on.

2. Where we actually are

3. What is measured, not asserted

These are checked by automated tests that fail the build, rather than reviewed by eye once and left:

• Every text colour is measured against both page backgrounds and must reach 4.5:1, or 3:1 where the text is large.
• Nothing that starts moving on its own keeps moving, and all motion is switched off for anybody whose device asks for reduced motion.
• Controls are at least 44 pixels tall, which is the target size a thumb needs.
• A control that records what you chose looks different from a control that invites you to press it, so choice is not signalled by colour alone.
• Bands are always written out (good, conditional, avoid) beside any colour that carries the same meaning.
• Filters announce themselves as pressed or not pressed, rather than as tabs, because several can be on at once.
• Every image carries a text alternative, and the pages are built from real headings, lists and tables rather than styled boxes.
• Pages respect the display area the phone leaves usable, so nothing sits under a notch or a home indicator.

4. What does not meet the standard yet

The map screens

The map is drawn on a canvas and an area is chosen by tapping it. There is no keyboard route to an area and no text alternative for the coloured surface, so WCAG 1.1.1 and 2.1.1 are not met on those screens. Once a panel is open, every figure in it is ordinary text and is read correctly: that is a mitigation, not a fix. A list view of the same areas is the intended remedy.

Steps that need a sensor

Some property-check steps ask you to hold the phone against a wall or point it at a window. If you cannot, refuse the permission or skip the step: the walk continues, the step is counted as unchecked, and the summary says so. No score treats a skipped step as a passed one.

Parts of the interface are in English only

The landing page, the legal pages, signing in and the account screens are published in more than one language. The rest of the app, including the property check, the maps and the measuring screens, is in Danish and English as far as the translation has reached, and English only otherwise. For a service in Denmark that is an accessibility problem as well as a translation one.

No independent audit

Everything above is a self-assessment carried out by the people who build it. It has not been reviewed by an external auditor or by a panel of disabled users, and self-assessment finds fewer problems than either.

5. If something is not reachable for you

Write to us at the address at the end of this page and tell us what you were trying to reach. We will send you the same information another way (the figures behind a map area as plain text, for instance), and we will treat it as a defect rather than as a request.

We answer within 10 working days. If we cannot fix something quickly we will say when we expect to, rather than leaving it open.

6. The legal position

The European Accessibility Act, Directive (EU) 2019/882, brought into Danish law by the act on accessibility requirements for certain products and services and applicable from 28 June 2025, sets accessibility requirements for consumer services and points at the standard EN 301 549. Art. 4(5) of the Directive exempts microenterprises providing services: fewer than 10 people and a turnover or balance sheet total of no more than €2 million. The Danish web accessibility act covers public bodies, not a private service like this one.

Whether Nesso in Denmark is covered or exempt depends on the business that operates it, and we have not established that yet. So we publish this statement and hold the product to WCAG 2.1 AA anyway. An exemption based on how small we are is not a reason to build something people cannot use, and it stops applying the moment we grow.

7. If we do not put it right

Tell us first, using the address at the end of this page. If you are not satisfied with the answer, you can contact the Danish Agency for Digital Government (Digitaliseringsstyrelsen, digst.dk), which can point you to the authority that supervises accessibility for this kind of service.

8. About this statement

Prepared on 1 October 2026 by self-assessment. The measured items in section 3 are checked automatically on every build; the rest was reviewed by hand on a phone. This statement is reviewed whenever a screen changes materially, and at least once a year.