Accessibility
Accessibility
A map is a visual thing, and that makes accessibility a real question for Grownhome rather than a box to tick. This page says plainly where the app stands, including what has not been tested yet.
Where the app stands today
Grownhome has not been through an accessibility audit, so this page does not claim it works well with a screen reader. We have not tested it properly with VoiceOver on iOS or TalkBack on Android, and saying it works when nobody has checked would be worse than admitting it has not been checked. If you rely on assistive technology, treat the app as unproven for now.
The app has not been released yet, which is the right time to fix this rather than the wrong time to mention it. What we are committing to before release:
- testing the app with VoiceOver and TalkBack actually switched on, on a real device, rather than assuming the default components behave;
- giving every control a meaningful accessible label — a map pin should announce the farm it marks and what it sells, not “button”;
- checking the app at large text sizes, so nothing is clipped or unreachable when system text is turned up;
- checking colour contrast against text and controls, not only against the map;
- making sure every touch target is big enough to hit reliably.
When those are done, this page will say what passed and what did not, with dates. Until then it stays as it is.
The list, not just the map
One thing that is already true and worth knowing: the app is not only a map. Under the map there is a Near you list, and each entry is ordinary text — the name of the place, the town it is in, how far away it is, and what it sells. A farm can be read as a line of text rather than found as a pin on a map.
That list is the most promising route to a genuinely non-visual experience, and it is where our accessibility work starts.
Your device’s accessibility features
iOS and Android both provide screen readers, text scaling, zoom, high-contrast modes and reduced-motion settings, and they work across apps. They are on your device already, whatever Grownhome does.
We are being deliberately careful here: listing these is not a claim that Grownhome works correctly with each of them. An app has to be built and tested to support them properly, and ours has not been verified yet. This section will say which ones the app genuinely supports once each has been tested.
This website
The site you are reading now is a different matter — it was built to be accessible and the following was checked directly:
- it works without JavaScript, and there is no client-side interactivity to get stuck in;
- proper page structure — real landmarks, one main heading per page, and headings in order, so a screen reader can navigate by them;
- everything reachable by keyboard, in a sensible order, with a focus outline you can actually see;
- text and controls meet WCAG AA contrast against their backgrounds;
- it reflows without horizontal scrolling down to a 320 px screen, and survives zooming to 200% and beyond;
- images carry text alternatives, and decorative ones are hidden from screen readers;
- nothing is revealed only on hover, nothing flashes, nothing plays automatically;
- the one animation on the site is a short fade on load, and it is switched off entirely if your system asks for reduced motion.
This has not been independently audited, and self-assessment is not certification. If something here fails for you, that is a bug and we want to hear about it.
Tell us what does not work
If any part of Grownhome or this website is difficult or impossible to use, email grownhome.team@gmail.com. Accessibility reports are not a nuisance; they are the fastest way for us to find out what is actually broken.
What helps us reproduce it, if you can include it:
- what you were trying to do;
- the assistive technology you use, and your device — for example VoiceOver on iPhone;
- where it went wrong, and what you expected instead.
A person reads every message. If you would rather not write out the detail, say so and describe it however suits you — we would rather have a short report than none.
What we are working towards
The target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AAfor this website, and Apple’s and Google’s own platform accessibility guidance for the app, since those are what iOS and Android users actually depend on.
We are a small operation and this is a statement of intent backed by specific work, not a certification. It will be updated as things are tested — including when something fails.
This statement was last reviewed on 30 July 2026. It describes the app before its first release; expect it to change.
Related: Support · Privacy Policy · Terms of Service