Accessibility

We want Ledgers to be usable by everyone, including people who rely on assistive technology. This statement explains where we stand and how to tell us when we fall short.

Last updated 26 September 2026 · Version 1.1

1. Our conformance target

Ledgers aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We consider the product partially conformant: most of it meets the standard, and the known gaps below are being worked through.

2. How we assessed it

In August 2026 we ran automated audits with axe-core against production builds, using the WCAG 2.0 and 2.1 Level A and AA rulesets. They covered the homepage, the /login page and 96 signed-in pages of the application. Every reported colour-contrast failure was re-measured against the background actually painted on screen, so the figures below count genuine failures, not tool false positives.

• Colour contrast — zero violations after remediation.
• Form labels — zero violations after remediation.
• Accessible names on links, selects and icon-only controls — zero violations after remediation.

These were automated audits by our own team. No independent or manual expert audit has been carried out yet, and automated tools find only part of what WCAG covers.

3. What we do

• Semantic HTML with landmark regions (navigation, main content, footer).
• A “skip to main content” link so keyboard users can bypass the navigation.
• A visible keyboard-focus outline on interactive controls.
• Labels on form fields (not placeholder text alone) and accessible names on icon-only controls.
• Text colours set to at least a 4.5:1 contrast ratio, checked by the audits above.
• Respect for the operating-system reduced-motion preference — animations are minimised when you ask for that.
• A page language set to British English so screen readers pronounce content correctly.

4. Known limitations

We are honest about where we’re not there yet. As of this statement:

• 13 remaining issues, all one rule: on some signed-in pages, links inside a block of text are distinguished from the surrounding text by colour alone (WCAG 1.4.1, Use of Colour, Level A). This mainly affects people with colour-vision deficiency. The fix is to underline those links, and it is awaiting a design change.
• Keyboard-only journeys, focus order and screen-reader behaviour have not yet been tested by hand, and no testing with assistive-technology users has taken place.
• Automated audits see each page in its default state, so content inside dialogs, expanded panels and less common form states is less thoroughly covered.
• Some data-dense tables and interactive charts have not been fully optimised for screen-reader narration.
• A small number of marketing pages do not yet carry an explicit main landmark.

These are on our roadmap, and reported issues are prioritised.

5. Tell us about a problem

If something is hard or impossible to use with assistive technology, please tell us — it helps us fix it. Email support@ledgers.work with the page, what you were trying to do, and the assistive technology you were using. We aim to acknowledge accessibility reports within 5 working days and will keep you updated on a fix.

6. Enforcement

If you contact us about an accessibility problem and are unhappy with our response, in the UK you can contact the Equality Advisory and Support Service (EASS).

This statement was prepared on 26 September 2026 from our own automated audits of August 2026. We will update it as we close the items above and when a manual audit is completed.

Questions about this document? Contact legal@ledgers.work or book a call.