Accessibility

Accessibility statement

Kontala is committed to making its products accessible to everyone, including people with disabilities. We are working towards full compliance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This statement covers every Kontala product, including the web application you sign in to.

Our products

This statement applies to the following Kontala products:

  • Kontala web application (go.kontala.com)
  • Kontala marketing website (kontala.com) - the site you are reading now
  • Kontala mobile app for iOS and Android - currently in development

The conformance status and the known limitations below come from our audit of the Kontala web application, which is where the day-to-day accounting work happens. The marketing website and the mobile app have not yet been audited to the same depth, and we say so under How we tested.

Standards and conformance

Our target standard is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

Kontala is currently partially conformant with WCAG 2.2 Level AA. “Partially conformant” means that some parts of the content do not yet fully meet the standard. We know about the issues listed below and active remediation work is under way to close them.

Our most recent audit assessed all 55 Level A and Level AA success criteria. As things stand, 45 pass, 3 do not yet pass, 1 cannot be confirmed until we complete screen reader testing, and 6 do not apply to Kontala because they cover pre-recorded audio and video, which our products do not use.

This statement was prepared on 11 September 2026 and was last reviewed in September 2026.

Known limitations

The content below is not yet accessible, for the reasons given. Each item names the WCAG 2.2 success criterion it relates to. This list is taken from our audit of 11 September 2026 and we update it as issues are fixed.

  • The word DRAFT is watermarked across the year-end report in a very pale tone. It is decorative, it is hidden from screen readers, and the same point is made in ordinary text directly above the report - but because it is drawn as live text rather than as a background image, it still counts against the contrast requirement. This is now the only place in the product where contrast falls short.1.4.3 Contrast (Minimum) · Level AA
  • Pages now reflow correctly when made narrow or zoomed to 400 percent across every screen we have been able to measure. Three areas are not yet measured, so we do not yet claim them: the detail page for an individual capital asset, the second and later tabs of tabbed pages, and dialogs and pop-up panels.1.4.10 Reflow · Level AA
  • The scrollable list inside a dropdown cannot be scrolled with the keyboard on its own, although every option in it can still be reached with the arrow keys. This comes from a third-party component, and the usual remedy introduces a worse keyboard problem, so we have recorded it and will re-test when that component is updated.2.1.1 Keyboard · Level A

If you come across an accessibility barrier that is not listed here, please tell us using the contact details below.

What we’re doing

Our current priority is closing the gaps in what we have measured rather than the issues themselves: the screens and states we have not yet been able to check for reflow, and the screen reader testing described below. The issues listed above are recorded and scheduled alongside that work.

Accessibility is part of how we design, build and maintain our products. Our current practices are:

  • Automated accessibility testing with the axe-core library, run across every screen as part of our development and continuous integration (CI) pipeline.
  • An accessibility-specific lint pass over the application source, so common markup problems are caught before they reach a screen.
  • Manual keyboard-only testing across a structured sample of screens and each end-to-end VAT return journey.
  • Manual colour contrast, page zoom and reflow checks over the same sample.
  • WAI-ARIA attributes where the semantics of HTML elements alone are not sufficient to convey purpose to assistive technologies.
  • A periodic re-audit against WCAG 2.2 Level AA, with the open findings published here, so this statement reflects what we have measured rather than what we intend.

How we tested

The Kontala web application was last tested on 11 September 2026. We carried out a self-assessment following the W3C Website Accessibility Conformance Evaluation Methodology (WCAG-EM). It combined an automated axe-core pass over every screen and screen state, an accessibility lint pass over the source, and manual keyboard, contrast, zoom and reflow checks over a structured sample of screens and each end-to-end VAT return journey.

What we have not yet tested

  • Our declared screen reader support baseline is macOS with Safari and VoiceOver. We have not yet completed testing with the Windows screen readers NVDA and JAWS, which are common among UK bookkeepers and accountants, so behaviour with those combinations is not yet confirmed.
  • One criterion, 4.1.3 Status Messages, depends on a screen reader announcing a change without moving focus. We have confirmed the underlying markup is in place, but we cannot confirm the announcement itself until that testing is done.
  • The marketing website and the mobile app have not yet been audited to the same depth as the web application.

Technical specifications

Accessibility of Kontala relies on the following technologies working with your browser and any assistive technologies or plugins installed on your device:

  • HTML
  • CSS
  • JavaScript (Vue 3 and Nuxt)
  • WAI-ARIA

These technologies are relied upon for conformance with the standards set out above.

Reporting and contact

If you experience an accessibility barrier on any Kontala product, if you need something from Kontala in a different format, or if you have feedback on how we can improve, please contact us:

Email: accessibility@kontala.com

We aim to respond within 5 business days.

Enforcement

If you are not satisfied with our response, you may wish to contact the Equality and Human Rights Commission (EHRC) if you believe your rights under the Equality Act 2010 have been affected. The EHRC can be reached at equalityhumanrights.com.

Last reviewed: September 2026