Accessibility statement

Prepared 4 August 2026 · last reviewed 2 October 2026 · applies to the TaxStats client and practice portal.

TaxStats is committed to making its software accessible, in line with the Equality Act 2010. Our conformance target is WCAG 2.1 Level AA.

Compliance status

This application is partially compliant with WCAG 2.1 AA. Our core filing journeys (sign-in, Making Tax Digital for VAT and for Income Tax) are keyboard operable, use HMRC's declaration wording and confirm before any return is submitted. A code audit on 2 October 2026 identified the known issues below, so we do not yet claim full conformance.

Known issues we are fixing

  • Some form fields, mainly in the wider accounting screens (invoicing, inventory, fixed assets, payroll and practice forms), do not yet have a fully associated text label for screen readers. We are linking these screen by screen, highest-traffic first.
  • A number of custom clickable elements are not yet operable by keyboard alone. We are converting these to keyboard-operable controls.
  • Form field borders and some focus indicators do not yet meet the 3:1 contrast ratio for user-interface components, and some secondary text in the dark theme falls below 4.5:1.
  • Some icon-only buttons do not yet have an accessible name, and some dialogs do not yet move keyboard focus into themselves.
  • Tutorial videos in the help centre do not yet have captions.
  • Short notification messages disappear after a few seconds; the information they carry is also shown on the page it relates to.

The authentication screens and the Making Tax Digital filing journeys are being prioritised. Accessibility lint rules are run during development; we are making them a required check so that new issues of these types cannot be introduced while the existing ones are worked down.

Reporting an accessibility problem

If you cannot access any part of this service, email robert@taxstats.co.uk with the page and the problem. We aim to respond within 5 working days and will help you and prioritise a fix.

How this statement was prepared

This statement was prepared on 4 August 2026 following an automated accessibility audit of the portal and manual checks of the primary journeys, and reviewed on 2 October 2026 against a criterion-by-criterion audit of the code. It will be reviewed as our remediation plan progresses.