Skip to main content
Back to Reyolk

Accessibility

Effective 9 October 2026

Our aim

Reyolk should work for everyone who runs a business on it and for every customer who books, enquires or reviews a quotation through it. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA.

Reyolk partly meets that standard today. This page says what we tested, what passed, and where we know it falls short.

What we tested

On 9 October 2026 we checked these parts of Reyolk:

  • The public site: the home page, Our Vision, the demo and waitlist pages, and the privacy, terms, refunds, cookies and linked-accounts pages.
  • Signing in: sign-in, sign-up and password reset, and the first step of setting up a new business.
  • The workspace: Home, Today, the inbox and an open conversation, customers and a customer's record, the calendar, a job, new bookings and service plans, quotations, invoices, Ask Reyolk, reports, sales, prospects, your account, and the main business settings pages.
  • What customers see: a business website made with Reyolk, with its booking and enquiry forms as they first appear, its privacy page, and the page a customer opens to review a quotation.

How we tested

  • Automated checks: every page above was scanned with axe-core 4.13 against the WCAG 2.0 and 2.1 level A and AA rules, in Chromium, at a desktop size of 1920 by 1080 pixels and a phone size of 390 by 844 pixels.
  • Keyboard only: in Chromium at desktop sizes (1440 by 810 and 1920 by 1080 pixels), without a mouse, we signed in, opened a conversation in the inbox and moved through it to the reply box and its send button, approved an action, created an invoice, and opened and closed the search and dialog windows. We checked the order of tab stops, that focus is always visible, that dialogs keep focus inside, close with Escape and return focus to the button that opened them, that nothing traps the keyboard, and that a skip link leads past the navigation.
  • In the code: the accessibility lint rules (eslint-plugin-jsx-a11y, recommended set) now run on every change, and an automated browser test fails if any of the pages above gains a serious or critical accessibility problem.

What we found and fixed

  • The “Required” note on form fields and the counts on list filters had too little contrast. Both are now readable.
  • There was no way to skip past the navigation. Every page now starts with a “Skip to main content” link.
  • Opening the invoice panel from a conversation, and approving an action on Today, lost keyboard focus. Focus now moves into the panel (and back when it closes), and after an approval it moves to the next item.
  • Some summary figures, the reply box and the business profile tabs described themselves incorrectly to screen readers. Their structure is now correct.

After these fixes the automated checks found no WCAG 2.1 level A or AA failures on any page listed above, at either size. In the keyboard pass every control in those tasks could be reached and used, focus was always visible, and no step trapped the keyboard.

Known gaps

  • Customer media has no captions. Voice notes, audio and video that customers send arrive without captions or transcripts, and Reyolk does not create them.
  • The launch film has no captions. It has music and no speech; every line shown in the film is written out beside it on the home page.
  • One browser, no screen readers yet. We tested in Chromium only. We have not yet tested with screen readers such as NVDA, JAWS or VoiceOver, in Safari or Firefox, with zoom at 200 percent or in high-contrast (forced colours) mode.
  • Some parts were not in this check. The website editor, the invoice design editor, dragging jobs on the calendar board, the window used to sign in to a linked account, and the booking form after its first step were not tested.
  • Long conversation lists. To reach an open conversation with the keyboard you tab past every conversation in the list first.
  • Some checks need a person. On several pages the automated tool could not decide the contrast of text over images or overlapping elements; those spots have not all been checked by hand.

Report a problem

If something in Reyolk is hard to use with your keyboard, screen reader, zoom or any other way you browse, tell us at [email protected]. Please include the page, what you were trying to do and the browser or assistive technology you use.

If the problem is on a business's own website or quotation, you can also contact that business directly.