Skip to main content

An accessible calendar for Android

Turn on TalkBack and many calendar apps become a guessing game: unlabeled buttons, no headings, no way to tell which view you're in. KashCal is built to be used by ear.

Using KashCal with a screen reader

Headings to jump between
Screen titles and the sections in Settings and the drawer are marked as headings, so you jump straight to what you want.
Labeled controls
Every icon-only button carries a label, so nothing reads as just "button."
Spoken status
Sync progress, going offline, a failed save, a sign-in error. KashCal announces the change instead of updating silently.
Event status, out loud
A cancelled event says "cancelled," a declined one says "declined." You hear an event's status, not just see it.
Which view you are in
The drawer announces the active view, not just highlights it.
Actions, not gestures
Delete a subscription from a menu action, not a swipe a screen reader can't reach.

Color is never the only signal

For KashCal users who are colorblind or have low vision, color alone isn't enough to go on. A cancelled event is crossed out, in the app and on the home-screen widgets, and a declined event is crossed out in the app, so their status shows without relying on color. A screen reader reads that status aloud too.

Accessibility is part of the build

WCAG is the international standard for making things usable by people with disabilities. KashCal holds itself to it, and doesn't leave that to chance.

Text and background colors are checked for readability, and the main screens run through Google's accessibility checks, the same ones behind Accessibility Scanner. Both run automatically every time KashCal is built, so an accessibility problem stops a release instead of shipping in it. It's a standing part of how the app is made and tested, not a one-time pass.

Read more about WCAG.

Frequently asked questions

How do I report an accessibility problem?

Open an issue on GitHub, or see reporting a bug. Tell us the screen, what your screen reader said or didn't say, and what you expected. Accessibility reports get treated as real bugs.