Accessibility Statement

Kivvo is a small New Zealand company — currently two people — building a goal-based savings app for New Zealanders. We care about making it usable by everyone, including people with disabilities. This statement describes the standard we work to, what we've done so far, what we know is still incomplete, and how to reach us if you encounter a barrier.

The short version

We aim to meet WCAG 2.1 Level AA, the internationally recognised standard for digital accessibility.

We are not yet fully conformant. We are honest about this. This page lists what we've done and what's still on our roadmap.

Kivvo supports dyslexia-friendly text spacing — you can increase text size, letter spacing, word spacing, and line height.

We recognise Te Tiriti o Waitangi and the place of te reo Māori in Aotearoa. We're at the beginning of this work and aim to do better.

If you encounter a barrier, tell us. Submit a support ticket via the Support page. We don't use email for support.

Our accessibility standard

Kivvo aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our primary accessibility standard. This is the internationally recognised benchmark for digital accessibility, and it's what we design, build, and test against.

We are not yet able to claim full conformance. Our current implementation meets many of the criteria; we are actively working through the rest. We treat this as an ongoing commitment, not a checkbox we complete once.

We also recognise Te Tiriti o Waitangi and the importance of te reo Māori in Aotearoa. We aim to use te reo Māori appropriately across Kivvo, and to make our service welcoming and usable for Māori users alongside all New Zealanders.

What we've done so far

The following practices are in place across Kivvo's web application. This list isn't exhaustive, but it describes the baseline we hold ourselves to.

Semantic HTML. Pages are built with meaningful HTML elements — headings, landmarks, lists, form controls — so screen readers and other assistive technologies can interpret the structure of each page.

Keyboard navigation. Every interactive control — links, buttons, form fields, dropdowns, modals — is intended to be reachable and operable using a keyboard alone. We avoid keyboard traps and return focus to a sensible location after modals close.

Focus visibility. Interactive elements show a visible focus indicator so keyboard users can see where they are on the page.

Colour contrast. We aim for text and interface elements to meet or exceed the WCAG 2.1 AA minimum contrast ratios: 4.5:1 for normal text, and 3:1 for large text and essential non-text elements.

Never colour alone. Information is never conveyed through colour as the only means. Status indicators, validation messages, and warnings include text and icons alongside colour.

Text alternatives. Meaningful images carry alternative text. Decorative images are marked so they're skipped by assistive technology.

Form labelling and errors. Form fields have associated labels, required fields are identified in text, and validation errors are announced and described clearly rather than only highlighted in red.

Responsive and zoomable layout. Kivvo is designed to remain usable when text is enlarged up to 200% and on small mobile viewports without losing content or requiring horizontal scrolling for primary tasks.

Consistent navigation. Repeated navigation elements — the top navigation bar, the sidebar in the documentation area, and the footer — use consistent placement and behaviour across pages.

Live region support. Where content changes dynamically (a saved notification, a validation error, a completed action) we aim to announce those changes to assistive technology where practical.

Dyslexia-friendly text spacing. Kivvo supports a more open, readable text layout. You can increase text size, letter spacing, word spacing, and line height to make reading more comfortable. This is designed for users with dyslexia and for anyone who finds dense text harder to read.

Known limitations

We're actively aware that the following areas do not yet fully meet WCAG 2.1 AA and are on our roadmap. Being honest about them is part of our commitment.

Comprehensive screen-reader testing. Our screen-reader testing to date has been limited. We have not yet completed full verification across VoiceOver (macOS and iOS), NVDA (Windows), JAWS (Windows), and TalkBack (Android).

Automated and manual test coverage. We have not yet implemented a full automated accessibility test suite (such as axe or Lighthouse) across every page, nor a complete manual audit against every WCAG 2.1 AA criterion.

Complex data visualisations. Charts and analytics on our goals and analytics pages may not yet fully meet WCAG 2.1 AA. Providing accessible alternatives — text summaries, accessible tables, or descriptions — is work still to complete.

Timed content and session expiry. Where sessions expire or content changes on a timer, the WCAG 2.1 AA requirements for warning, extending, or turning off the timer may not yet be fully implemented across every flow.

Third-party content. Some parts of our service rely on third-party components and services — for example, Stripe for payment fields and Supabase for authentication. We choose providers carefully, but we don't control their accessibility, and their conformance is their responsibility.

Older pages and edge-case flows. As an early-stage product, some less-used pages have not yet received the same level of accessibility attention as the primary paths through Kivvo.

Te reo Māori coverage. We are at the beginning of our work with te reo Māori. Not every part of the product yet reflects the level of bilingual care we want to achieve.

If you encounter a barrier that isn't listed here, please tell us. The most useful thing you can do for our accessibility work is report what you experience.

Assistive technologies we aim to support

Kivvo is intended to work with current versions of the following:

VoiceOver on macOS and iOS

NVDA and JAWS on Windows

TalkBack on Android

Dragon NaturallySpeaking and other voice-control software

Operating-system-level magnification and zoom

Keyboard-only navigation, including sticky keys and switch access

Dyslexia-friendly text spacing controls built into Kivvo

We recommend keeping your browser and assistive technology up to date, as older versions may not reflect current accessibility support.

Reporting an accessibility issue

If you experience any difficulty accessing or using Kivvo, please report it. You can do this by submitting a support ticket via the Support page. We do not use email for support.

To help us respond effectively, please include:

A description of what you were trying to do

The specific barrier you encountered

The page or feature involved, if you can identify it

The assistive technology and browser you were using, if applicable

The operating system and device type, if relevant

We'll acknowledge your ticket and, where we can, provide an accessible alternative or a workaround. Where we can't immediately resolve the issue, we'll tell you what we can do and when we expect to provide an update.

Requests for information in another format

If you need information from Kivvo presented in a different format — an accessible document, a plain-text version, or a summary that works with your specific assistive technology — you can request this through the same support process. We'll do our best to provide the information in a usable form.

Enforcement and escalation

We're committed to resolving accessibility issues in good faith. If you aren't satisfied with our response, you can raise the matter formally through our Complaints Policy, which sets out how complaints are received, investigated, and responded to.

As a New Zealand company, we're also mindful of the wider direction of digital accessibility expectations in Aotearoa and internationally. We intend to keep developing Kivvo in line with those expectations as they evolve.

Review of this statement

This Accessibility Statement will be reviewed periodically — at minimum annually, and more frequently as we make material changes to the product. When we update it, we'll revise the statement so it reflects our current practices rather than a historical snapshot.

This page was last reviewed in October 2026.

For questions, submit a support ticket via the Support page.