How accessible DII Accounts is

The standard we work to

Dhruvi Infinity Inspiration Ltd aims to meet the Web Content Accessibility Guidelines version 2.2 at Level AA for DII Accounts. That is the level HMRC expects of web-based software used for Making Tax Digital, and it is the level we hold ourselves to for the rest of the product as well.

We also have duties under the Equality Act 2010 to make reasonable adjustments so that disabled people are not put at a substantial disadvantage when they use this service. This statement is written so that you can see what we have checked and what we have not, rather than a claim that everything is fine.

Current status: partially conformant

DII Accounts is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means most of the standard is met on the parts of the service we have tested, and some parts of the service have not been tested at all. The known exceptions are listed below, individually, rather than summarised away.

We do not claim full conformance, and we have not been audited by an independent accessibility organisation.

What we have tested, and how

Testing so far is our own, and it is of two kinds.

• Automated rule checks in a real browser. The axe accessibility rule engine runs inside our browser test suite against the WCAG 2.0 A, WCAG 2.0 AA, WCAG 2.1 AA and WCAG 2.2 AA rule sets. These checks run on every change, so a regression on a covered page fails the build rather than reaching you. They currently cover: the public landing page, sign up, sign in, business setup, creating an invoice, importing a bank CSV, the reconciliation workspace, viewing a VAT return, and this statement.
• Code-level guards. Automated checks fail the build if a page layout loses its document language declaration, or if a stylesheet removes a focus outline without providing a replacement — the two regressions we found were easiest to introduce silently.

Automated tools find a minority of accessibility problems. They are a floor, not a ceiling, and we say so here rather than presenting them as proof the service works for you.

What we fixed to get here

• No page declared its language, so a screen reader could read English accounting terms with another language's pronunciation rules. Every layout now declares British English.
• The keyboard focus indicator did not have enough contrast against the page, and five components removed it entirely. Focus is now visible on every interactive element we style, including the date picker.
• Form validation failures were shown but not announced. A failed submission now moves focus to a summary that a screen reader reads out, each entry links to the field that produced it, and each field carries its own error message and an invalid state that assistive technology can detect.
• Confirmation and error banners were not in a live region, so they were never announced. They now are.
• Several colours — success and warning text, muted body copy, and one status pill — sat between 2.8:1 and 4.1:1 against their backgrounds. They were darkened to clear 4.5:1. Nothing else about the design changed.
• The nine VAT return boxes were a visual grid with no table semantics. Their row and column relationships are now declared.

What we know does not conform yet

These are real, current, and not yet fixed.

• Most of the service has not been assessed. Automated checks cover the nine screens listed above. The accountant practice workspace, the AI Accountant, reporting, payroll, CIS, quotes, bills, expenses, settings, billing, the article editor, and the admin and owner surfaces have had no accessibility testing. We cannot tell you they conform, so we are not going to.
• No screen reader testing. Nobody has used this service end to end with JAWS, NVDA, VoiceOver or Dragon, and we have not tested with disabled users. Programmatic markup being correct is not the same as the journey being usable.
• Data tables mostly lack explicit column scope. Two shared table components declare it; the roughly four hundred table headers written directly into individual pages do not. Simple tables are usually still navigable, but wide accounting reports are exactly where this matters most.
• The field guidance buttons all announce the same name. Every "?" button on a form is announced as "Explain this field", so a screen reader user listing the controls on an invoice form hears the same label repeatedly and cannot tell which field each belongs to (WCAG 2.4.6).
• Third-party components are unassessed. The Trix rich text editor in the article editor and the Flatpickr date picker are external components. We have added a visible focus indicator to the date picker, but we have not verified their keyboard and screen reader behaviour.
• Generated PDFs are not tagged. Invoices, statements and reports exported as PDF are not structured for assistive technology. If you need one of these in an accessible format, ask us and we will provide it another way.
• Session timeout. Signed-in sessions expire after a period of inactivity and we have not verified that the warning and recovery behaviour meets WCAG 2.2.1.

If something here blocks you

Write to legal@dii.ltd and tell us what you were trying to do, where you got stuck, and what you use to browse — for example the screen reader, magnifier, or speech input, and its version. You do not need to know which guideline is involved.

We aim to reply within five working days. If you need information that is in the product but not reachable for you — a report, a VAT figure, an invoice — say so and we will get it to you in a format you can use while we fix the underlying problem.

You can also write to us at the registered office address at the foot of this page.

Enforcement

The Equality and Human Rights Commission is responsible for enforcing the Equality Act 2010. If you are unhappy with how we respond to your complaint, you can contact the Equality Advisory and Support Service, which is the body that handles individual accessibility complaints in Great Britain. In Northern Ireland, contact the Equality Commission for Northern Ireland.

How this statement is kept honest

This statement is part of the application, not a separate document, and the automated checks described above run against the journeys it names. When we extend testing to another part of the service, or fix something on this page's list, this page changes with it. If you find a claim here that does not match your experience, that is a defect and we want to hear about it at legal@dii.ltd.