Accessibility

Accessibility statement

RelayLink is meant to be usable by everyone, with any assistive technology, and without a script. This page says what standard we build to, how we measure against it, what we know falls short, and how to tell us when something is out of reach. Last updated 19 September 2026.

The standard

We aim for the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA on every page we serve: the public site, the documentation, the guides, the account portal, the sign-in and consent screens, and the page a briefing link opens. We treat WCAG 2.2 AA as the target for new work.

Where we are

The site is partially conformant with WCAG 2.1 AA: an automated audit of every public and portal page passed on 4 September 2026 after four findings were fixed, and those fixes are held in place by tests. Pages added since then have been checked with an automated sweep for contrast, touch-target size, heading order and overflow. No full manual audit with assistive technology has yet been carried out; we will update this page when one has.

What that audit found and what changed:

  • Every section on the landing page used a misspelt labelling attribute, so a screen reader heard none of them as labelled. Fixed, and a test now scans the source for the misspelling.
  • Two text colours were a few points under the AA contrast ratio. Both are darker now, and a test computes the ratio from the stylesheet so a lighter tint fails it.
  • The sign-in and consent pages had no landmarks. Each has a header and one main region now.
  • A horizontally scrolling code example could not be reached from the keyboard. It has a tab stop and a region name.

How the site is built to be accessible

  • Everything works without JavaScript. The public pages and the account pages each load one script of our own, and it only adds to what is there: the story demonstration's player, copy buttons and a guide to the page's sections on the public pages; confirmations, notices and quicker page changes in the account. With it blocked, every form, menu and control is plain HTML that still works, and the page a briefing link opens loads no script at all.
  • Structure first. One main landmark per page, a skip link, a heading order that describes the page, labelled sections, named regions on anything that scrolls, and tables with header cells.
  • Colour and type. Text meets the AA contrast ratio on every surface it appears on, and that is measured rather than promised. Nothing is conveyed by colour alone: provenance labels are words, not tints.
  • Motion. Where the reduced-motion preference is set, animations become fades or static content, and nothing slides, scales or springs.
  • Content that moves on by itself. The story demonstration on the home page advances on its own. It has a pause button beside its progress, stops while a pointer rests on a scene, and every scene is also written out in the page for anyone reading without the script.
  • Video. The eighteen-second video on the home page has no sound and its own controls, starts by itself only where motion is welcome, and its caption says what it shows; the section around it makes the same case in text.
  • Keyboard. Every control can be reached and operated from the keyboard, with a visible focus indicator.
  • Email. Every email has a plain-text part carrying the whole message, so it reads correctly in a text-only client or a screen reader.

Known limitations

  • The audit was automated and at phone width. Manual testing with screen readers and at other sizes has not yet been done across every page.
  • Briefing content is written by other people. We render it as plain, structured text with the provenance labels as words, but we cannot make a sender's own wording clearer than they wrote it.
  • The site is in English only.

Tell us

If you cannot reach or use something on RelayLink, or you need any of it in another form, write to hello@relaylink.ai with “Accessibility” in the subject. It is the only channel we take this on; PillarStack LLC is in Richmond, Virginia, United States. Say which page and what happened, and which browser and assistive technology you were using if you can. We will reply within five business days and we will treat a barrier that stops somebody using their account as a defect to fix, not a request to consider.

If you are not satisfied

If we do not resolve a problem you have told us about, you can complain to the authority where you live. In the United States that may be the Department of Justice under the Americans with Disabilities Act; in the EU and the UK, the body that enforces the accessibility rules that apply to you. We would rather fix it, so please write to us first.