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
Section titles in Settings and the drawer are headings. So are the title in an event's details, the date on a day's event list and the event form's title. Jump straight to what you want.
Labeled controls
Icon-only buttons have spoken labels, so they don't read as just "button."
Spoken status
Sync progress, going offline, a failed save, a sign-in error. KashCal announces each change as it happens.
Event status, out loud
A cancelled event says "cancelled," a declined one says "declined," and a past one says "past event." You hear an event's status, not only see it.
Which view you are in
The drawer tells you which view is selected, not only highlights it.
Actions, not gestures
Delete a subscription from the TalkBack actions menu instead of a swipe a screen reader can't reach.

Status doesn't rely on color​

If you're 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 agenda, week and upcoming widgets. A declined event is crossed out in the app. 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 checks itself against it.

The app's tests check that event colors, the app's color schemes for every accent color (light and dark) and widget themes meet WCAG AA contrast. Before a release, the main screens go through Google's accessibility checks, the same engine behind Accessibility Scanner, on a real device. It's a standing part of how the app is 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.