Accessibility Statement

Version: VERSION · Statement date: EFFECTIVE DATE App version assessed: APP VERSION AND BUILD Published by: LEGAL ENTITY NAME, REGISTERED ADDRESS

Last reviewed against the code: 2026-09-20. Owner action before launch: publish this at a public URL, put the address in lib/legalDocuments.ts, fill in the feedback address and the date, and re-check the "Known gaps" list. It must be true on the day it is published, not on the day it was written.

Our commitment

ZMacros should be usable by everyone who wants to track what they eat, including people who use a screen reader, need large text, cannot see colour differences, or find movement on screen uncomfortable.

Standard we measure against

ZMacros aims to meet WCAG 2.2 level AA, applied to native mobile apps. That goes beyond the WCAG 2.1 AA level used by the European harmonised standard EN 301 549, which is how conformity with the European Accessibility Act is presumed.

Conformance status

ZMacros is partially conformant with WCAG 2.2 level AA: most of the standard is met, and the gaps below are known and being worked on. We say partially because a stronger claim would need testing we have not finished, and an accessibility statement that overstates is worse than one that admits a gap.

What is in place

• Everything is a named control. Every button reports itself as a button, and every icon-only button has a spoken name. A test fails the build if one appears without one.
• The numbers are read out, not just drawn. The calorie and macro rings, the steps ring and the weight trend chart each have a spoken description that says the value, the target and what is left — "Calories, 1,420 of 2,100 kcal, 680 left". A value that was never recorded is announced as not recorded, never as zero.
• Nothing is information by colour alone. Every ring, bar and status has a label or a shape as well as a colour.
• Contrast. Every text colour in every theme, every accent and every custom background is measured against WCAG's 4.5:1 for text, in a test, on every run. Colours that failed have been changed rather than excused.
• Large text. The app follows the system text size, including the accessibility sizes, and layouts grow rather than clip.
• Tap targets are at least 44×44 points, or have enough extra touch area to reach that.
• Reduce Motion. The two continuous animations — the drifting sheen on glass cards and the wobble in Edit mode — stop when Reduce Motion is on.
• Haptics can be turned off entirely.
• No time limits. Nothing in the app expires, counts down or has to be done at a pace.

Known gaps

1. A full VoiceOver pass is not complete. Individual screens have been checked; a screen-by-screen pass on a physical device has not been. This is the largest remaining item.
2. TalkBack on Android is untested, because the Android build has not shipped yet (#138).
3. Two macro fill colours — the fat orange and the fiber green — are below the 3:1 graphical-object threshold against the light background. No information depends on them alone (every ring has a label and a spoken description), and the fix is a design decision between darker fills and an outline. It is open.
4. Background photos. A photo behind the Today screen is dimmed to keep text readable, but a photo is arbitrary, so contrast over one cannot be guaranteed the way a theme colour can. Choosing a plain background colour avoids this entirely.
5. Charts are described in words but are not individually navigable point by point.
6. Some screens and messages are English only, including the safeguard and support copy, the privacy-rights screen and some settings screens. A screen reader in another language will read those sentences in English (#387, #336, #338).
7. The subscription purchase and cancellation steps happen in Apple's and Google's own screens, whose accessibility we do not control.

How we tested

• Automated contrast measurement against WCAG 2.2 AA for every palette the app can build, in the test suite.
• Automated checks for unnamed controls, small tap targets, Reduce Motion handling and text-alternative coverage.
• Manual checks with VoiceOver and the accessibility text sizes on iOS, screen by screen but not yet exhaustively.

Feedback and alternative formats

If something in ZMacros is hard or impossible for you to use, please tell us — it is treated as a defect, not a suggestion. Contact: SUPPORT CONTACT EMAIL. We aim to reply within five working days. If you need this statement or any of our legal documents in another format, ask at the same address.

Enforcement

If you are in the EU and are not satisfied with our response, you may contact the authority responsible for enforcing the European Accessibility Act in your country. In the UK, the Equality Advisory and Support Service can advise.