Skip to content
Arbor

Accessibility statement

We sell accessibility audits, so our own site has to meet the standard we test against. This page says how far it does, and what we have not checked yet.

Last updated .

What we aim for

This site aims to meet WCAG 2.2 at levels A and AA in full. We also aim for four level AAA criteria: 1.4.6 Contrast (Enhanced) for body text, 2.4.13 Focus Appearance, 2.5.5 Target Size (Enhanced) for the main controls, and 3.1.5 Reading Level for our marketing pages.

How we tested this site

Every change to the site runs these checks before it can be published, on every page:

  • axe-core 4.14 with the WCAG 2.0, 2.1 and 2.2 A and AA rules, at widths of 320, 390, 768 and 1,440 CSS pixels;
  • a keyboard pass: the skip link comes first, every focusable element shows a visible focus ring, and no focused element is hidden or off screen;
  • the phone menu opened and closed by keyboard, with Escape returning focus to its button;
  • form errors: an error summary that receives focus and links to each field;
  • reflow at 320 pixels with no sideways scrolling, the WCAG 1.4.12 text spacing test, and Windows high contrast (forced colors) mode;
  • target size, one heading level 1 per page with no skipped levels, and valid HTML;
  • Lighthouse on a simulated mid-range phone, with Accessibility at 100.

Automated checks find only part of what matters. A perfect score from them is a floor, not proof.

What we have not tested yet

We have not yet completed a full manual pass of this site with the NVDA, TalkBack or VoiceOver screen readers. Until we have, we do not claim that the site conforms to WCAG 2.2 AA. We will update this page with the date, the screen reader versions and the results when that pass is done.

Known problems

The automated checks above report no open problems. If you find one, please tell us: it goes on this list with a fix date, and we aim to fix it within 10 working days.

Report a problem

Email hello@openeveryflow.tech, or use our contact form. Tell us the page, what you were trying to do and, if you like, the browser and assistive technology you use. We reply within 5 working days.