Accessibility statement
For Taxbix Books, the online accounting application at taxbix.com/accounting, the pages we send to your clients (onboarding, document signing, fee proposals and invoice payment) and the taxbix.com home page. Taxbix is a trading name of Gain Financial Solutions Ltd.
We want as many people as possible to be able to use Taxbix. This statement explains how accessible it is, where it still falls short, and how to contact us if you have a problem.
Compliance status
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Taxbix is partially compliant with this standard: the main screens we checked meet it, but the issues listed below remain and not every screen has been checked yet.
What you can expect
- You can use the main screens with a keyboard alone, and a visible outline shows where you are. A "Skip to main content" link is the first thing you reach.
- Pop-up windows (dialogs) take the keyboard focus when they open, keep it inside while they are open, close with the Escape key and return you to where you were.
- Form fields have names that screen readers read out. Sign-in and one-time code fields can be filled in by password managers, and you can paste into them. We never ask you to solve a puzzle to sign in.
- Short confirmation and error messages are announced by screen readers.
- Text and controls have enough colour contrast (at least 4.5 to 1 for normal text) in the standard light theme.
- Pages have headings in order and landmarks (header, navigation, main content), and the page language is set, including when you choose one of the 11 languages.
- The layout works on phones as well as larger screens. Animation is switched off when your device asks for reduced motion, and the moving demo on the sign-in page has a Pause button.
- The Support button is in the same place at the top of every screen of the app.
Known issues
These parts do not yet fully meet WCAG 2.2 AA. We are working on them:
- Not every screen and dialog has been checked. The app has many specialist screens (for example payroll submissions, working papers and the practice area tabs); we checked the most used ones first.
- We have not yet completed testing with screen readers on every screen. Some complex screens (bank reconciliation, report builder, document review) may be hard to follow with a screen reader.
- The dark theme has not been fully checked for colour contrast. Use the light theme if contrast is a problem for you.
- On the sign-in page some fields show their name only inside the field, so the name disappears while you type.
- Wide tables (bank transactions, reports) scroll sideways on small screens.
- When you choose a language other than English, a few labels that only screen readers read are still in English.
- Short confirmation messages disappear after about two seconds. They are announced by screen readers; tell us if you need more time.
- PDF documents the app creates (invoices, statements, signed letters) are not yet tagged for screen readers.
- The card payment form on the invoice payment page is provided by our payment provider in a secure embedded frame, and we cannot change it. You can always pay by bank transfer instead.
- Documents you or your clients upload (for example scanned receipts) may not be accessible themselves.
Feedback and contact
If you find any part of Taxbix hard to use, or you need information in a different format, please tell us. We will do our best to help.
- Email: contact@taxbix.com
- Phone: 07892 656 897
We aim to reply within 5 working days.
Enforcement procedure
If you contact us with a complaint about accessibility and you are not happy with our response, you can contact the Equality Advisory and Support Service (EASS). In Northern Ireland, contact the Equality Commission for Northern Ireland.
How we test
We check the main screens with an automated accessibility checker at desktop and phone sizes, and by hand with the keyboard. The automated checks are part of the tests we run before each release, so new problems on the checked screens are caught before they reach you.
Preparation of this statement
This statement was first prepared on 6 September 2026. It was last reviewed on 19 October 2026, after an audit against WCAG 2.2 AA.