Accessibility statement
For OpenCT at tax.openli.ai, version 1.4.111
Last evaluated: 7 November 2026. Next review due: 7 May 2027 (every six months).
1. Conformance status
This website is partially conformant with the Web Content Accessibility Guidelines version 2.1 AA standard. ‘Partially conformant’ means that some parts of the content do not fully conform.
The standard is the Web Content Accessibility Guidelines (WCAG 2.1), Level AA. The method is a self-evaluation by the WCAG-EM evaluation methodology; no third party has audited OpenCT.
2. Scope
This statement covers every page of tax.openli.ai. It was evaluated on the pages below, which include every step of filing a Company Tax Return and the accounts with Companies House.
Pages open to everyone
- Home (
/) - Pricing (
/pricing) - For accountants (
/for-accountants) - This accessibility statement (
/accessibility) - Sign in (
/login) - Create an account (
/register) - Forgotten password (
/forgot-password) - Reset password (opened without its link: the refusal and its way on) (
/reset-password) - Terms of service (
/terms) - Privacy policy (
/privacy) - Refund policy (
/refund-policy) - Acceptable use policy (
/aup) - AI assistant disclaimer (
/ai-disclaimer) - Tax advice disclaimer (
/tax-disclaimer) - Filing authorisation (
/filing-authorisation) - Data processing agreement (
/dpa) - Subprocessors (
/subprocessors) - Security policy (
/security-policy) - Cookie policy (
/cookie-policy)
Pages after signing in
- Dashboard (
/dashboard) - Set up your organisation (
/onboarding/first-company) - Companies (
/companies) - Enter the figures (
/books) - Figures & adjustments (
/accounts) - Accounts (an association's PDF) (
/accounts-pdf) - Tax computation (
/tax-computation) - The CT600 form (
/ct600) - Review & sign-off (
/review) - Submit to HMRC and File with Companies House (
/submissions) - Company check (
/companies-house) - Accounts questions (
/companies-house/questions) - Documents (
/documents) - Charities & CASCs (
/charitable-exemptions) - R&D relief (
/rd-relief) - CIS deductions (
/cis-deductions) - Adjustments (
/adjustments) - AI assistant (
/chat) - Billing & subscription (
/billing) - Team (
/team) - Settings (
/settings) - Audit trail (
/audit-trail) - HMRC credentials (
/companies/[companyId]/credentials) - Integrations (
/integrations) - Management accounts (
/management) - Company secretary (
/secretary) - Administration: audit log (
/admin/audit-log) - Administration: settings (
/admin/settings)
Not covered: the sites of HMRC, Companies House and others that we link to, and the files OpenCT makes for HMRC and Companies House to read by machine (the CT600 XML and the iXBRL accounts and computation).
3. How we test
- Automated, at every release. axe-core checks every page above against the WCAG 2.1 A and AA rules, in the light and the dark theme. A release is stopped by any critical or serious violation, by a page without exactly one main landmark, by content outside the page's landmarks, by a skipped heading level, by an empty table header, and by a listed page that answers “not found”.
- By keyboard and at 320 pixels. Each evaluation also goes through the main pages of the filing journeys with the keyboard alone, checking that each stop has a visible focus indicator, and checks that they reflow at a width of 320 CSS pixels, and with the text zoomed to 200 %, without scrolling sideways.
- By a person with a screen reader. A manual check with VoiceOver follows this release (section 4, What we are doing).
4. Non-accessible content
As at 8 November 2026: the issues found by our scripted audit of 7 November 2026 — landmarks and heading order on shared page shells, a form label, empty table headers on the accounts page, the audit log and the financial-year card, the price ladder, reflow of the statement page, the CT600 grid at 320 px, the cookie button's accessible name — were fixed in release v1.4.111 on 8 November 2026 and await re-audit on the released version.
What we are doing: a scripted audit of every route on the released version and a manual screen-reader (VoiceOver) check follow this release; this statement is updated with their results.
No independent audit. This statement rests on OpenCT's own evaluation. No third party has audited OpenCT for accessibility, and OpenCT holds no accessibility certificate.
5. Found a barrier? Tell us
If anything stops you using OpenCT, please tell us so we can fix it as a priority. We answer reports of an accessibility barrier within 5 business days.
- Email: support@openli.ai
6. Enforcement
If you contact us about an accessibility barrier and are not happy with our response, you can contact the Equality and Human Rights Commission (EHRC) who are responsible for enforcing the Equality Act 2010 in the UK, including accessibility of digital services.
7. Technical specification
OpenCT relies on HTML, CSS, JavaScript and WAI-ARIA. The automated checks run in Chromium; the screen-reader check uses Safari with VoiceOver on macOS. We rely on semantic HTML (one <main> per page, named <nav> landmarks, a <footer>, headings in order, labelled form fields) and on one set of theme colours so that the light and dark themes meet the same WCAG AA contrast.
8. Preparation of this statement
This statement was last reviewed on 8 November 2026, for OpenCT v1.4.111, from the evaluation of 7 November 2026. The evaluation report is kept in our source repository as docs/06-testing/accessibility/wcag_em_self_audit_v1_4_111.md; ask support@openli.ai for a copy.