Accessibility

What Zebal does for accessibility, honestly — including what we haven't gotten to yet.

Our commitment

Zebal was built with screen reader users, low-vision users, and anyone who finds typing difficult in mind from the start — not added on afterwards. Voice input exists because typing every expense is a real barrier for a lot of people, not just a convenience feature.

What's built in

The standard we build to

We build against WCAG 2.1 Level AA as our internal benchmark — the same standard used throughout the app's own code and this website (contrast ratios, focus indication, touch target sizing).

To be upfront: this is a standard we hold ourselves to, not a certification. Zebal has not been through a formal third-party accessibility audit. What's here reflects genuine, ongoing effort by a small team — not a compliance guarantee.

How we test

Mainly by using TalkBack on real Android devices while building each feature, rather than testing only at the end. Keyboard and switch-style navigation are checked where relevant. We also rely on people who use these tools day to day telling us when something doesn't work — see "Report a problem" below.

This website

The same principles apply here: every text/background colour pair meets the 4.5:1 contrast minimum, focus is always visible when navigating by keyboard, a skip link lets you jump straight past the header, and text sizes use rem units so your browser's own text-size setting keeps working.

Known limitations

Report a problem

If something in the app or on this site doesn't work with your screen reader, switch access, or any other assistive technology, please tell us — email quickconnect82@gmail.com. It helps to mention your device and what you were using (e.g. TalkBack on Android) so we can reproduce it. We treat these as priority reports, not routine feedback.

← Back to Zebal