This statement covers the website at lekhio.app and the Lekhio web app you sign in to there. The iPhone and Android apps are not covered by this statement.
Lekhio Ltd runs this website. We want as many people as possible to be able to use it, with a screen reader, a keyboard, zoom or wider text spacing, in the light theme or the dark one.
How accessible this website is
We know some parts of this website are not fully accessible:
- Some info buttons share one name, so a screen reader cannot tell them apart.
- Some screens have no main heading of their own, and two tables have no header cells.
- Some name, business and email fields do not yet tell the browser what they hold.
- Some links in body text and the selected tab in the app are shown by colour alone.
- Some small text on the homepage and on the Can I claim it page falls below the contrast it should have.
- At high zoom the app's tab bar and the site's sticky bar can cover content.
- On a few pages, parts reach past the edge of a very narrow screen.
- Some field edges and the focus ring in the dark theme are too faint.
- With wider text spacing, a few figures on the homepage and in the invoice generator are cut off.
- The site menu and the reviews belt cannot yet be used by keyboard alone.
- The sorting deck's single key shortcuts can act outside it.
- The homepage animation and the reviews belt move with no way to pause them.
- There is no link to skip past the menu to the main content.
- Most app screens share one page title.
- When the delete sheet opens, focus does not move into it.
- Some buttons are named too generally to say what they do.
- On the calculators and a few forms the focus outline is removed.
- A voice note can still be sent after the finger slides off the button.
- Some form errors are not tied to the field they are about.
- The site menu and some info buttons do not say their name or state to a screen reader.
- The calculators and the sorting deck do not announce their result to a screen reader.
And some parts have not been checked by a person yet, so we cannot tell you they work. They are listed under what we have not checked yet, below.
Feedback and contact information
If you need anything on this website in a different format, or you find a problem that is not listed on this page, email info@lekhio.app with the word Accessibility in the subject. A person reads it and replies within 5 working days.
Technical information about this website's accessibility
We measure this website against the Web Content Accessibility Guidelines version 2.1, at levels A and AA. There are 50 criteria at those levels, and this page says where we stand on each.
Compliance status
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, because of the problems and the unchecked parts listed below.
Non-accessible content
These are the problems we know about, by criterion. We are working through them, and this page changes as each fix lands.
- 1.1.1 Non-text Content. Some info buttons share one name, so a screen reader cannot tell them apart.
- 1.3.1 Info and Relationships. Some screens have no main heading of their own, and two tables have no header cells.
- 1.3.5 Identify Input Purpose. Some name, business and email fields do not yet tell the browser what they hold.
- 1.4.1 Use of Color. Some links in body text and the selected tab in the app are shown by colour alone.
- 1.4.3 Contrast (Minimum). Some small text on the homepage and on the Can I claim it page falls below the contrast it should have.
- 1.4.4 Resize text. At high zoom the app's tab bar and the site's sticky bar can cover content.
- 1.4.10 Reflow. On a few pages, parts reach past the edge of a very narrow screen.
- 1.4.11 Non-text Contrast. Some field edges and the focus ring in the dark theme are too faint.
- 1.4.12 Text Spacing. With wider text spacing, a few figures on the homepage and in the invoice generator are cut off.
- 2.1.1 Keyboard. The site menu and the reviews belt cannot yet be used by keyboard alone.
- 2.1.4 Character Key Shortcuts. The sorting deck's single key shortcuts can act outside it.
- 2.2.2 Pause, Stop, Hide. The homepage animation and the reviews belt move with no way to pause them.
- 2.4.1 Bypass Blocks. There is no link to skip past the menu to the main content.
- 2.4.2 Page Titled. Most app screens share one page title.
- 2.4.3 Focus Order. When the delete sheet opens, focus does not move into it.
- 2.4.6 Headings and Labels. Some buttons are named too generally to say what they do.
- 2.4.7 Focus Visible. On the calculators and a few forms the focus outline is removed.
- 2.5.2 Pointer Cancellation. A voice note can still be sent after the finger slides off the button.
- 3.3.1 Error Identification. Some form errors are not tied to the field they are about.
- 4.1.2 Name, Role, Value. The site menu and some info buttons do not say their name or state to a screen reader.
- 4.1.3 Status Messages. The calculators and the sorting deck do not announce their result to a screen reader.
What we have not checked yet
A machine can check only part of what makes a website usable. These criteria need a person, with a keyboard and a screen reader, and that check has not happened yet. We know of no problem with them, but we cannot yet say they work.
- 1.3.2 Meaningful Sequence. Not yet checked by a person. No problem is known.
- 1.3.3 Sensory Characteristics. Not yet checked by a person. No problem is known.
- 1.3.4 Orientation. Not yet checked by a person. No problem is known.
- 1.4.5 Images of Text. Not yet checked by a person. No problem is known.
- 1.4.13 Content on Hover or Focus. Not yet checked by a person. No problem is known.
- 2.1.2 No Keyboard Trap. Not yet checked by a person. No problem is known.
- 2.2.1 Timing Adjustable. Not yet checked by a person for every time limit. No problem is known.
- 2.3.1 Three Flashes or Below Threshold. Not yet checked by a person. Nothing on the site is known to flash.
- 2.4.4 Link Purpose (In Context). Not yet checked by a person. No problem is known.
- 2.4.5 Multiple Ways. Not yet checked by a person. No problem is known.
- 2.5.1 Pointer Gestures. Not yet checked by a person. No problem is known.
- 2.5.3 Label in Name. Not yet checked by a person. No problem is known.
- 2.5.4 Motion Actuation. Not yet checked by a person. Nothing is known to act on movement.
- 3.1.2 Language of Parts. Not yet checked by a person. No problem is known.
- 3.2.1 On Focus. Not yet checked by a person. No problem is known.
- 3.2.2 On Input. Not yet checked by a person. No problem is known.
- 3.2.3 Consistent Navigation. Not yet checked by a person. No problem is known.
- 3.2.4 Consistent Identification. Not yet checked by a person. No problem is known.
- 3.3.2 Labels or Instructions. Not yet checked by a person. The probe found no field without a label.
- 3.3.3 Error Suggestion. Not yet checked by a person. No problem is known.
- 3.3.4 Error Prevention (Legal, Financial, Data). Not yet checked by a person. Paying and deleting each ask for a clear yes first.
What we have shown works, and what does not apply
- 3.1.1 Language of Page. Every probed page says it is in English.
- 4.1.1 Parsing. W3C says this criterion is always met by content written in HTML.
- 1.2.1 Audio-only and Video-only (Prerecorded). Does not apply. There is no audio or video content on the site or in the web app.
- 1.2.2 Captions (Prerecorded). Does not apply. There is no audio or video content on the site or in the web app.
- 1.2.3 Audio Description or Media Alternative (Prerecorded). Does not apply. There is no audio or video content on the site or in the web app.
- 1.2.4 Captions (Live). Does not apply. There is no audio or video content on the site or in the web app.
- 1.2.5 Audio Description (Prerecorded). Does not apply. There is no audio or video content on the site or in the web app.
- 1.4.2 Audio Control. Does not apply. Nothing on the site plays sound by itself.
What we're doing to improve accessibility
None of these is done yet. These are the planned steps, in this order, and this page changes as each one lands. The known problems listed above are fixed within them:
- Every app screen gets its own page title and one main heading.
- A focus outline you can see in the light theme and the dark one, and field edges with enough contrast.
- Everything usable by keyboard: the site menu, the reviews belt, a link to skip to the main content, and focus that moves into the delete sheet.
- A way to pause the homepage animation and the reviews belt, and a voice note that is thrown away when your finger slides off the button.
- Names for every info button, header cells on our tables, and form fields that say what they hold and describe their errors.
- Results the calculators and the sorting deck announce, and the sorting deck's single key shortcuts working only inside it.
- Links underlined in body text, the selected tab shown by shape as well as colour, small text on the homepage and the sources on Can I claim it at full contrast, and bars that give way at high zoom.
- The mileage calculator, the invoice generator and Can I claim it fitting a narrow screen without sideways scrolling, and the homepage card and the invoice generator's table keeping their text when spacing is increased.
- After those, a person walks the website with a keyboard and with VoiceOver, and this page reports what they find.
One fix is already in: the app's tab bar keeps its labels at full contrast when a blue button scrolls under it.
How we tested this website
We run our own checker, built on the open source axe-core 4.12.1, in a browser on our own machine. On each page it is given, it checks the light theme and the dark one, a screen 320 pixels wide, and wider text spacing, against the WCAG 2.1 A and AA rules and nothing else. It has run on:
- 6 October 2026: every page in our sitemap, the sign in and sign up pages, and three app screens.
- 16 October 2026: five app screens, among them the HMRC page and the new help screen for Making Tax Digital.
Most screens inside the web app have not been run through the checker yet, and no person has yet walked the website with a keyboard or a screen reader. Both are planned, and this page will say when they are done.
Preparation of this accessibility statement
This statement was prepared on 16 October 2026. It was last reviewed on 16 October 2026.