Accessibility statement for VoxaMTD

1. Using VoxaMTD

We want as many people as possible to be able to use VoxaMTD. For example, you should be able to:

• zoom in using your web browser (zoom is never blocked)
• move around most of the web app using just a keyboard
• use the web app in portrait or landscape
• listen to most of the website using a screen reader
• read the transcript of any audio we provide
• review your figures and tick a declaration before anything is sent to HMRC

2. How accessible VoxaMTD is

We know some parts of VoxaMTD are not fully accessible:

• some text has low colour contrast, including grey helper text, teal links, red error messages and the website footer
• some buttons that show only an icon (such as the menu, show password and delete buttons) have no name for screen readers
• many form labels are not linked to their fields, and the sign-in and sign-up forms do not support autofill of your details
• some error messages are not announced by screen readers, and some disappear after about 5 seconds
• several signed-in pages, such as Settings and Billing, do not have their own page title
• some options when adding a property cannot be chosen with a keyboard
• there is no "skip to main content" link
• the dashboard chart of income and expenses relies on colour and has no text alternative
• some records delete straight away, with no confirmation or undo
• in the iPhone app, most text does not get bigger when you change the Larger Text setting
• in the iPhone app, some buttons have no VoiceOver label, the business-use slider cannot be set with VoiceOver or Switch Control, and the app only works in portrait

3. Feedback and contact information

If you need help using VoxaMTD, or information in a different format, email hello@voxamtd.com.

We'll consider your request and get back to you within 5 working days.

4. Reporting accessibility problems with VoxaMTD

We're always looking to improve the accessibility of VoxaMTD. If you find any problems not listed on this page, or think we're not meeting accessibility requirements, email hello@voxamtd.com. Please tell us the page or screen, and what you were trying to do.

5. Technical information about VoxaMTD's accessibility

Voxa MTD Ltd is committed to making VoxaMTD accessible.

Compliance status: VoxaMTD is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

6. Non-accessible content

The content listed below is non-accessible for the following reasons. Non-compliance with the accessibility regulations:

• Some text and controls do not have enough colour contrast. This fails WCAG 2.1 success criteria 1.4.3 (Contrast (Minimum)) and 1.4.11 (Non-text Contrast).
• Some icon-only buttons and logo links have no accessible name. This fails 1.1.1 (Non-text Content), 2.4.4 (Link Purpose) and 4.1.2 (Name, Role, Value).
• Many visible form labels are not programmatically linked to their fields, and some fields rely on placeholder text. This fails 1.3.1 (Info and Relationships) and 3.3.2 (Labels or Instructions).
• The web sign-in, sign-up, password reset and settings forms do not identify the purpose of fields such as email and password. This fails 1.3.5 (Identify Input Purpose).
• Most fields are not marked as invalid when there is an error, and inline errors are not announced. This fails 3.3.1 (Error Identification) and 4.1.3 (Status Messages).
• Notification messages, including some errors, close after about 5 seconds. This fails 2.2.1 (Timing Adjustable).
• Several signed-in pages do not set their own title. This fails 2.4.2 (Page Titled).
• Some choice cards and table rows work only with a mouse, and some tooltips cannot be reached by keyboard. This fails 2.1.1 (Keyboard).
• On mobile, the closed menu stays in the keyboard tab order, and the confirmation screen after a submission does not take focus. This fails 2.4.3 (Focus Order) and 2.4.7 (Focus Visible).
• There is no way to skip repeated navigation. This fails 2.4.1 (Bypass Blocks).
• The dashboard income and expenses chart relies on colour. This fails 1.4.1 (Use of Colour).
• Some income, expense and capital allowance records are deleted with no confirmation or undo. This fails 3.3.4 (Error Prevention).
• In the iPhone app, most text does not follow the Larger Text (Dynamic Type) setting. This fails 1.4.4 (Resize Text).
• The iPhone app works in portrait only. This fails 1.3.4 (Orientation).
• In the iPhone app, the business-use slider cannot be operated with VoiceOver or Switch Control, and deleting a transaction needs a swipe. This fails 2.1.1 (Keyboard) and 4.1.2 (Name, Role, Value).

We have not yet tested reflow at 320 CSS pixels, text spacing, or 200% zoom on every page (1.4.10 Reflow, 1.4.12 Text Spacing, 1.4.4 Resize Text).

We plan to fix these issues. We will update this statement as we fix them.

7. What we're doing to improve accessibility

We have listed every known issue above and in the WCAG 2.1 AA checklist we have given to HMRC. We will work through them, starting with colour contrast, unnamed buttons, form labels and errors, and text size in the iPhone app.

8. Preparation of this accessibility statement

This statement was prepared on 20 October 2026. It was last reviewed on 20 October 2026.

VoxaMTD was last tested on 20 October 2026. The test was a self-assessment, carried out by Voxa MTD Ltd by reviewing the code of the website, the web app and the iPhone app against WCAG 2.1 AA. It has not yet been tested by a third party or with assistive technology on a device.