Accessibility Statement

Trove is committed to making its website and app usable by as many people as possible, including people who rely on assistive technologies. Accessibility is an ongoing effort, and we treat it as part of building a good product rather than an afterthought.

1. Conformance target

We measure ourselves against the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard most widely referenced by accessibility law in North America and elsewhere.

Trove is partially conformant with WCAG 2.1 AA. "Partially conformant" means most of the product meets the standard, but some content or interactions may not yet fully conform. We describe the known gaps in section 3.

2. What we've done

Measures we've built into Trove include:

• Semantic, structured markup — headings, lists, tables, and landmarks so screen readers can navigate the page logically.
• Keyboard access — interactive controls are reachable and operable with a keyboard, with visible focus indicators.
• Labels on controls — form fields and icon-only buttons carry text labels or aria-labels so their purpose is announced.
• Colour contrast — text and essential UI are designed to meet the AA contrast ratios, in both light and dark themes.
• Never colour alone — status and meaning (e.g. income vs. expense, over-budget) are conveyed with text or icons in addition to colour.
• Responsive and zoomable — layouts reflow from phone to desktop, text can be resized, and page zoom is never disabled.
• Reduced motion — we keep animation subtle and respect the operating system's "reduce motion" preference.
• Larger touch targets — primary controls are sized for touch on mobile.

3. Known limitations

We're a small, independent team and we're honest about where we fall short. Areas we're still improving:

• Data visualisations — the "Money flow" diagram and progress charts are primarily visual. We provide the same figures as text and tables, but the interactive charts themselves are not fully optimised for screen readers yet.
• Imported documents — the accuracy and structure of an imported bank CSV or PDF depend on the file your bank produces, which is outside our control.
• Third-party components — a few flows rely on external providers (for example, sign-in and payment screens) whose accessibility we do not fully control.

Where a feature isn't fully accessible, we aim to make sure the underlying information or action is available another way. If it isn't, please tell us.

4. Giving us feedback

If you run into an accessibility barrier in Trove, we want to hear about it — your reports directly shape what we fix first.

• Email: support@householdtrove.com
• In-app: the feedback button (the chat bubble in the bottom-right of every screen).

Please include the page or feature, what you were trying to do, and the assistive technology or browser you were using, if you can. We aim to acknowledge accessibility reports within 5 business days and will work with you on a resolution or a usable alternative.

5. Ongoing effort

Accessibility isn't a one-time checkbox. We review it as we ship new features, and we update this statement as the product and our conformance change. This statement was last reviewed on the date shown above.