Accessibility statement for KINTO Join Admin Portal

This accessibility statement applies to the KINTO Join Admin Portal website.

This website is run by KINTO Join. We want as many people as possible to be able to use this.
For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the app using just a keyboard
  • navigate most of the app using speech recognition software
  • listen to most of the app using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the app text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible:

  • an empty form field is present and may be announced by screen readers
  • the focus order of the page is not always logical
  • navigate most of the app using speech recognition software

Feedback and contact information

If you need information on this app in a different format like accessible PDF contact us via:

We’ll consider your request and get back to you in 14 days.

Contacting us or reporting accessibility problems with the app

We’re always looking to improve the accessibility of this app. If you find any problems not listed or think we’re not meeting accessibility requirements, contact: support@kintojoin.io

Technical information about this app’s accessibility

Compliance status

This app is fully compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, the non-compliances and exemptions are listed below

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

A form field with no content or label within the cookies overlay is focused by screen readers. This fails WCAG 2.2 success criterion 1.1.1 (Non-Text Content).

Within the OneTrust cookie overlay, a form field without content or label may be focused by screen readers. This issue originates from the third-party component and is outside of our direct control. We will adopt improvements once provided by the vendor.

 

The focus order of the page is not logical. Users who rely on a keyboard to access for operating a page benefit from a logical, usable focus order. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order).

 

Within the OneTrust cookie overlay, the focus order is not fully logical for keyboard navigation. This issue is inherent to the third-party component and cannot be directly remediated by us. We will implement updates as soon as the vendor provides a compliant solution.

 

Menu elements are not always announced accurately. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).

 

Some menu states are announced differently, even though the component is not a traditional dropdown. This wording accurately reflects the state within our application. Accessibility reviewers accepted this usage but flagged it as non-compliant. As this is a documented design decision, we consider the current implementation valid unless broader standards dictate otherwise.

 

Preparation of this accessibility statement

This statement was prepared on 11/09/2025. It was last reviewed on 11/09/2025. This website was last tested on 11/09/2025. The test was carried out by Zoonou. Zoonou used WCAG-EM to define the pages tested and test approach.