Accessibility | Kemback

Everyone in a household should be able to manage its money in Kemback, including people who use a screen reader, a keyboard instead of a mouse, magnification, or larger text. This statement explains what we aim for, what we have checked, and where we still fall short.

Our goal

We aim for kemback.com and the Kemback web app to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. This is a rule in how we build Kemback, not a one-off project: a change that breaks it doesn’t ship.

How we check

Automated checks on every change. Before any change to the website or the web app is released, an automated browser test runs the axe accessibility engine on every page of this website (the blog and the “page not found” page included), and on every screen of the web app, signed in and signed out. It checks each one in the light and dark themes, at desktop and phone widths, against the WCAG 2.0, 2.1 and 2.2 level A and AA rules axe covers, and the change fails if it finds anything.

Checks by hand. Automated tools find only part of what matters, so we also check by hand:

Keyboard only: creating an account, adding a transaction, editing a budget and editing website content can all be done without a mouse. There are no keyboard traps, focus moves in a sensible order, and the focused item is always visible, never hidden under the sticky header.
Zoom and reflow: pages work at 200% zoom and at 320 pixels wide without scrolling sideways, and still work when line, paragraph, letter and word spacing are increased.
Status messages: messages like “Saved.” and errors are announced by screen readers without moving focus.
Signing in: you can paste your password and codes, use your password manager, or sign in with a passkey. Kemback never asks you to solve a puzzle or remember something to sign in.
Consistent help and no repeated typing: help and contact links are in the same place on every page, and Kemback doesn’t ask for the same information twice in one process.

Charts in reports have a written summary and a table view with every value, and you can step through a chart’s months with the arrow keys. Kemback follows your device’s light or dark setting, and respects the “reduce motion” setting.

Known limitations

We’d rather tell you about these than have you find them:

Not yet tested with assistive technology users. Our checks are automated tests and our own testing by hand in the browser. They don’t yet include a full screen reader walkthrough, an audit by an independent specialist, or testing with disabled users. We plan all three.
The iPhone app (beta) has VoiceOver labels and supports Dynamic Type on its main screens, but hasn’t been tested end to end with VoiceOver. On the bills calendar, a bill’s status is shown by colour in the grid (VoiceOver reads it, and the list below the calendar says it in words). At the largest text sizes, some rows become cramped.
The Android and Windows apps are in development and haven’t been reviewed for accessibility.
Blog images written before October 2026 may lack descriptions. Our publishing tools now flag any image without one.
Two-step verification setup shows a QR code. If you can’t scan it, the setup key is shown as text beside it to type into your authenticator app.
Imported files and exports (OFX, QIF, CSV, JSON) are data files; how accessible they are depends on the program you open them with.

Tell us about a barrier

If something in Kemback is hard or impossible for you to use, please tell us at hello@kemback.com. Say which page or screen, what you were trying to do, and, if you like, the browser and assistive technology you use. We read every message and aim to reply within five working days. If we can’t fix the problem quickly, we’ll help you get done what you were trying to do another way.

About this statement

This statement was prepared in October 2026, from the checks described above. We update it whenever those checks or the limitations change.