AI TaxPilot← Back to site
ACCESSIBILITY

Accessibility Statement

How we make AI TaxPilot usable to everyone

Aicountant Ltd (trading as AI TaxPilot) Version 1.0 — Effective 04 June 2026

1. Our commitment

Aicountant Ltd, trading as AI TaxPilot, is committed to making our Service accessible to as many people as possible, including people with disabilities. We design and build to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA and treat accessibility as part of every feature, not a separate audit.

2. Standard we aim for

AI TaxPilot is built to conform to WCAG 2.2 Level AA. Where parts of the Service do not yet meet that standard we list them under "Known issues" below and commit to a remediation date.

AI TaxPilot is a commercial digital product rather than a UK public-sector website, so the Public Sector Bodies (Websites and Mobile Applications) (No.2) Accessibility Regulations 2018 do not apply directly to us. We nonetheless follow the same WCAG 2.2 AA baseline that those regulations require, and we treat the Equality Act 2010's duty to make reasonable adjustments as binding on us.

3. What is accessible today

The following features and behaviours are in place across the Service:

  • Skip navigation. A "Skip to main content" link is revealed on the first Tab press of every page so keyboard users can bypass the global navigation (WCAG 2.4.1 Bypass Blocks).
  • Landmark structure. Every page exposes proper <header>, <nav>, <main> and <footer> landmarks for screen-reader navigation.
  • Keyboard support. All interactive controls — links, buttons, form fields, calculator inputs, the AI chat composer, the submission flows — are reachable and operable using a keyboard alone, with visible focus indicators (WCAG 2.4.7 Focus Visible).
  • Reduced motion. When a visitor's operating system requests reduced motion, our CSS disables non-essential animations and transitions (WCAG 2.3.3 Animation from Interactions).
  • Colour contrast. Text foreground / background pairs across the marketing site, dashboard and legal pages have been designed to meet at least the 4.5:1 contrast ratio required for normal text and 3:1 for large text (WCAG 1.4.3 Contrast Minimum).
  • Text alternatives. Brand marks, decorative icons and emoji glyphs are marked aria-hidden="true" and accompanied by visible or off-screen text equivalents (WCAG 1.1.1 Non-text Content).
  • Form labels. All form inputs are programmatically associated with a visible label or an aria-label (WCAG 1.3.1 Info and Relationships, 3.3.2 Labels or Instructions).
  • Language. The page language is declared on the HTML root (WCAG 3.1.1 Language of Page).
  • Responsive layout. The interface reflows to single column on screens 320 CSS pixels wide and supports browser zoom up to 400% without loss of content (WCAG 1.4.10 Reflow, 1.4.4 Resize text).
  • Document content. Tax-figure tables use font-variant-numeric: tabular-nums so columns align consistently for users relying on screen magnification.

4. Known issues and roadmap

We track accessibility issues in the same backlog as other engineering work. The following items are known to be below WCAG 2.2 AA and are scheduled for remediation:

  • Independent audit. We have completed an internal accessibility review against WCAG 2.2 AA but have not yet commissioned an external audit by an accredited accessibility consultancy. We will commission this for the v1.1 release in Q3 2026 and publish the audit report alongside this statement.
  • Mobile companion app. Our React Native mobile app (iOS / Android) is being audited separately for WCAG 2.2 AA and platform conformance (iOS VoiceOver, Android TalkBack). Mobile conformance is targeted for v1.1.
  • Charts and data visualisations. A small number of charts in the dashboard rely on colour to distinguish series. We are adding pattern fills and accessible data tables as alternative representations.
  • PDF exports. The PDF outputs generated by our export flows (CT600 computations, SA-style summaries) are tagged but have not been independently checked for PDF/UA conformance. We are reviewing tagging fidelity for the next release.

If you encounter an accessibility barrier that is not listed here, please tell us — see "Reporting an accessibility problem" below.

5. How we test

  • We design against WCAG 2.2 AA from the start of every feature, not as a follow-up.
  • Our build pipeline includes static accessibility checks and our designers review new screens against an internal WCAG 2.2 AA checklist before release.
  • We perform manual keyboard-only walk-throughs of the critical journeys (sign-in, onboarding, calculator usage, AI chat, HMRC submission) before each major release.
  • We test with screen readers on at least two combinations: NVDA + Firefox on Windows and VoiceOver + Safari on macOS / iOS.
  • Contrast is verified using browser developer tools and automated analysers against the WCAG 2.2 AA ratios.

6. Assistive technology support

AI TaxPilot is designed to work with current assistive technology. We officially test against:

  • NVDA 2024 on Firefox and Chrome (Windows)
  • VoiceOver on Safari (macOS and iOS)
  • TalkBack on Chrome (Android)
  • Browser zoom up to 400% in current versions of Chrome, Firefox, Safari and Edge
  • Operating-system level high-contrast and dark modes

Other configurations should also work, but we test the combinations above on every release.

7. Reporting an accessibility problem

We want to hear from you if you experience any accessibility barrier in AI TaxPilot, including if you need information in a different format such as accessible PDF, large print, easy read, audio recording or braille.

  • Email accessibility@aitaxpilot.com with the page URL and a short description of the problem. We will acknowledge your message within 2 business days.
  • For urgent issues affecting your ability to file a return, email our support team at support@aitaxpilot.com and mark the subject as "Accessibility — urgent".
  • We aim to resolve confirmed WCAG 2.2 AA failures within 30 business days of receiving the report, or sooner where the barrier prevents a customer from filing a return.

8. Enforcement procedure

AI TaxPilot is a private-sector commercial service and is not subject to the Public Sector Bodies Accessibility Regulations 2018 enforcement procedure. However, the Equality Act 2010 places duties on us to make reasonable adjustments. If you are unhappy with how we have responded to an accessibility complaint, you can contact the Equality Advisory and Support Service (EASS).

9. Preparation of this statement

This statement was prepared on 4 June 2026. It was last reviewed on 4 June 2026 against an internal WCAG 2.2 Level AA assessment carried out by the engineering team using a combination of automated checks, manual keyboard and screen-reader testing.

The next planned review of this statement is December 2026 or when significant changes to the Service are released, whichever is sooner.

Questions? Contact our Data Protection Officer at dpo@aitaxpilot.com or write to Aicountant Ltd, England & Wales.