Adra · Accessibility
Accessible by design.
Adra is built for everyone who wants to track what they eat. Accessibility is not an extra. It is part of how the app is made.
Why this matters
Everyone meets friction at some point. Bright sunlight on a screen. One hand holding a child. A bandaged wrist. Tired eyes at 22:00. A screen reader that is the only way to use a phone.
Some barriers last a minute. Some last a lifetime. An app that works for more people is simply a better app for everyone.
What Adra does
-
TalkBack support.
Buttons, labels, and results carry proper labels, and TalkBack announces them. Controls are not a mystery to a screen reader. A screen reader user should be able to log a meal without guessing what any control does.
-
Your device's language.
Since version 1.1.42, TalkBack reads buttons and labels in the device language, not only English. A person who uses their phone in German should hear German, not a translation of an English interface.
-
Contrast that reads.
Text follows WCAG AA contrast on the dark theme, and an automated test checks the contrast guidelines. Contrast is not a matter of taste here. It is a number a test can hold the design to.
-
Never color alone.
Macros always carry text labels. Meaning never depends on color vision. This is a brand rule, not an afterthought. A value that reads only as red or green is a value some people cannot read at all.
-
Semantic traversal tests.
The app's widget labels are verified by dedicated automated tests, not by memory. A label that is correct today can break in a later change, and the test is what catches that.
-
Verified on real devices.
Accessibility behavior is checked on actual hardware during development, the same way every other feature is. A screen reader behaves differently on a real phone than in a test harness, so both are used.
Tested, not assumed
Accessibility runs through the same pipeline as every feature in Adra. It has tests, and those tests run before a release goes out. When something breaks, it breaks loudly before it reaches you.
Adra is built by one person, so there is no separate compliance team to hand accessibility to. It lives in the same pipeline as everything else, which means it is checked on every change rather than audited once and forgotten.
This site too
This site is keyboard-navigable and screen-reader friendly. It has no cookies, no ads, and no third-party scripts, and it passes automated WCAG 2.2 AA checks. The same standard the app is held to applies to the page describing it.
If a claim about accessibility is worth making, it is worth making on a page that is itself accessible. Every page here is built to be read by keyboard and by screen reader, not only by sight.
FAQ
Does Adra work with TalkBack?
Yes. Buttons, labels, and results are announced by TalkBack in your device's language.
What accessibility standard does Adra aim for?
WCAG AA contrast on text, labeled controls throughout, and meaning that never depends on color alone. The project checks these in automated tests.
Accessibility is ongoing work, and no list on a page can cover every situation a person meets. If something in Adra is hard to use, write to adra@matz.works. The person who reads it builds the app.