Accessibility

By Suraj Giri

Everything the editors who sign as the love gurus publish should work for everyone; this page says how we test that and what is still wrong.

What accessibility standard does LoveCalculator.love meet?

We test against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The first release check ran on 22 September 2026 on the pre-launch build: the automated check found no violation on any of the 70 pages, every one of the eight Wave 1 tools could be worked by keyboard alone, and no accessibility issue is open. One part of the protocol has not been done by a person yet, the screen-reader run, and this page says so rather than counting the automated check as that run.

We want every tool and page on this site to be usable by everyone, including people who use a screen reader, a keyboard only, magnification, or reduced motion.

What is checked on every release?

Before a release, each calculator and quiz has to pass five accessibility checks:

  • Automated check (axe): no critical or serious findings.
  • Keyboard-only pass: every control reachable and operable by Tab, Enter and Space; visible focus.
  • Screen-reader pass: the result is announced when it appears; every form field has a label; the label badge and the score are read as text, not as an image.
  • Colour contrast: at least 4.5 to 1 for text.
  • Sound and motion: the Love Tester's sound has to turn off, and its animation has to respect the "reduce motion" setting.

The result of each check is published with the other release results on the methodology page. A check that nobody ran reads "not run", never "passed". On the 22 September 2026 run the automated check, the keyboard-only pass and the contrast check passed; the screen-reader pass was covered only as far as a harness can cover it (every result in a live region, every field labelled); the sound and motion line does not apply yet, because the Love Tester has no sound or animation.

What accessibility issues are known?

The list below is rendered from the current known-issues file: each open item with its page and its fix date, or a dated statement that no issue is open. An item leaves this list when it is fixed, and the fix is dated on the changelog.

No accessibility issue is open as of (release 0.1.0). Checked: axe-core 4.13 against WCAG 2.0 A and AA, 2.1 A and AA and 2.2 AA on all 70 built pages, contrast included; keyboard-only runs of the eight Wave 1 tools; every page with JavaScript switched off.

Not yet testable, and listed so nobody reads a pass into them:

  • Share cards: the card renderer is not built, so there is no card whose alt text could be checked.
  • The Love Tester's sound and motion: the tester has no sound or needle animation yet; when they ship, the off switch and the reduced-motion setting are checked under this heading.
  • A screen-reader pass by a person: the automated and keyboard checks confirm that every result sits in a live region and every field has a label, but nobody has yet run the tools with a screen reader.

How do you report an accessibility barrier?

You report an accessibility barrier by email, in three steps:

  1. Email info@lovecalculator.love with the page and what happened, or contact the love gurus through the contact page.
  2. We reply within 5 working days.
  3. We treat an accessibility barrier as a correction: fixed within 72 hours where we can, or a dated note on the changelog saying when.

When was accessibility last reviewed?

22 September 2026, on the pre-launch build (release 0.1.0). Run: axe-core 4.13 against WCAG 2.0 A and AA, 2.1 A and AA and 2.2 AA on all 70 built pages, in Chromium; keyboard-only runs of the eight Wave 1 tools, in Chromium; every page with JavaScript switched off. Not run: a screen-reader pass by a person, and the device rows of the browser matrix.

The full release protocol, with all eight checks, is described in our methodology.