DRAFT — this statement describes only what our evidence ledger shows today. Its acknowledgement wording is a default that has not yet been approved by the founder; the commitments and known limitations are accurate as written.
Accessibility statement
Published 2026-09-19 · last technical evaluation 2026-09-19 · next review 2026-12-19
Our commitment
GrowthBerry aims to be usable by people with disabilities across every public page and the customer workspace. We treat accessibility as an engineering law with executable checks, not as a badge.
Standard and scope
WCAG 2.2 Level AA is the engineering target.
In scope: growthberry.ai (every URL our sitemap declares), the customer workspace (scanned through a fixture harness in CI), and the email, CSV and rendered-guide output families. Crosswalks: WCAG 2.1 AA and Section 508 through our conformance report.
What we actually do
- A colour-contrast law on the design tokens, pinned by executable tests — meaningful text meets 4.5:1 and control boundaries meet 3:1.
- One form contract (real labels, required and invalid states, described errors) enforced by a census that fails the build on any unnamed control.
- A status law: every asynchronous outcome — audit runs, saves, sends, sign-in errors — is announced once through a live region and results receive focus.
- Keyboard laws: a skip link as the first Tab stop, scroll padding under the sticky header, a modal-dialog contract (focus trap, Escape, focus restore) and keyboard-operable pause controls on anything that auto-advances.
- Verbatim captions and a transcript on the launch film.
- An axe-core census in CI over every sitemap URL, the interaction states and the workspace fixture harness — blocking, with an empty suppression list by design — plus a weekly sweep of the live site.
- Plain-text transactional email; no accessibility overlay widgets, ever (our content-security policy blocks them).
How we test
- axe-core in continuous integration over the site census and the workspace harness.
- Automated keyboard journeys (sign-in, the free audit, the skills dialog, the mobile menu).
- Reflow at 320 CSS px, text-spacing overrides and forced-colours checks on the main templates.
- Contrast mathematics on the token palette, and inspection of the email, CSV and guide outputs.
- Screen-reader sessions with real users have not yet been run — see Known limitations.
Known limitations
The honest list, in the words our engineering ledger uses. An item leaves it only when its fix is verified on the live site.
- The film's narration says "sixteen checks"; the engine runs seventeen. Captions and the transcript are verbatim to the recorded audio, and a visible correction note carries the accurate count. This leaves the list when the narration is re-recorded.
- Coverage — automation is now blocking (P5). Automated checks reach every sitemap URL, the interaction states, the visual-adaptation criteria and the nine authenticated workspace surfaces, and currently measure zero violations of any severity. What remains for humans, not automation, is assistive-technology testing.
- Human testing. No screen-reader session or disabled-user testing has been run yet. We record this as not run, with an owner and a date — never as a pass.
- Statement & channel — DRAFT. This statement and its feedback form went live on 2026-09-19. The acknowledgement wording is a default pending founder approval, and this page stays marked DRAFT until then.
Outside our control, with the accessible path named:
- Square's hosted checkout page is operated by Square; Square's accessibility statement applies. Our hand-off and return pages are in scope and tested.
- Tenant destination sites — the customer domains our guides link out to — are their owners' properties.
- AI-generated guide text is validator-governed and rendered with real semantics; the wording itself is adjudicated against those validators, not guaranteed plain-language.
Tell us what got in the way
If something on this site or in the workspace is hard or impossible to use with your assistive technology or settings, tell us here. We will not ask you for a diagnosis. While we investigate we will offer an alternative way to get what you came for, and we aim to acknowledge every report within 2 business days.
Reports are stored so we can act on them and are covered by our Privacy Policy.
Compatibility
Evergreen browsers on desktop and mobile. The workspace and the free tools are keyboard-operable; system dark mode and reduced-motion preferences are honoured.
History
- Statement published 2026-09-19 (draft wording, see the banner).
- Last technical evaluation 2026-09-19: the CI census and the weekly production sweep both green.
- Next scheduled review 2026-12-19; reviews are quarterly.