Accessibility

What we aim for

Every page of marling.io is meant to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We build to that line because the people our customers serve include people who need it, and a page that falls below it is a defect to us, the same as a broken link.

This statement covers marling.io, the website. It does not cover the Marling device’s own screens.

What we checked, and how

In October 2026 we put every page in the site map, the page shown for a missing address and the forms’ result pages through a real browser, at desktop and phone widths (1280, 360 and 320 pixels), at 200% zoom and at 200% text size. On each page we:

• walked the page with the keyboard only, and checked that focus is always visible and never hidden behind the fixed navigation;
• measured the contrast of text, and of the edges of controls, against what sits behind them;
• checked that every control has a name, every page has one heading structure, every image has a text alternative, and nothing is lost when text spacing is widened;
• watched what moves, with the reduce-motion setting on and with it off;
• ran the axe-core rule set for WCAG 2.0, 2.1 and 2.2 at levels A and AA.

The checks found ten problems. All ten are fixed, each in its own change, and measured again on the live site.

Where it still falls short

• We have not yet checked the site in Safari or on an iPhone, so a problem there may be one we have not seen.
• We have not yet listened to the site with a screen reader. We checked the names, roles and states a screen reader reads, not what one says aloud.
• On the home page, the example chat types and clears its phrases for about fifteen seconds before it stops, and there is no control on the page to pause it. It holds still when your reduce-motion setting is on.
• With JavaScript off, a form sent back with a mistake shows its message above the button and ties it to the fields it names, but the message is not read out when the page loads.

Telling us about a problem

If something on this site does not work for you, tell us and a person will answer. Use the contact form and choose “Something else” as the topic, or email hello@marling.io. Say which page it was and what happened, and if you know it, which browser or assistive technology you were using. We treat an accessibility problem as a defect, the same as a broken page.

How this page is kept true

The date at the top is the last full check of the whole site, and it moves only when we check again. The list above changes when something is fixed or found. An automated check runs on every change before it reaches the site: it reads the color pairs it can see, the heading structure, whether every control has a focus style, and the motion rules, so a new page starts from the same line.