Accessibility statement
We sell accessibility audits, so we audited our own site first. This page reports what we found, what we fixed and what is still open, and tells you how to reach us if something on aigrow.gg stops you.
Last updated 28 October 2026.
In short
- We test aigrow.gg against WCAG 2.2 Level AA. The site is partially conformant: the pages we tested pass every automated check, and some checks that need a person are still open.
- On 28 October 2026 we ran axe-core on six pages, in English and Italian, at desktop and phone widths: 24 runs in all.
- One rule failed, on one page: the step numbers on the shop accessibility audit page had too little contrast. We fixed it the same day.
- What is still open is listed below, each item with a target date of 31 December 2026.
- If anything on the site stops you, write to hello@aigrow.gg.
This summary helps you read the statement; the full text below is what applies.
1. The standard we measure against
We use the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the W3C. Its latest version is dated 12 December 2024.
In the European Union, the harmonised standard EN 301 549 V3.2.1 refers to WCAG 2.1 Level AA for web content. WCAG 2.2 adds new success criteria to those of WCAG 2.1, and we test against the newer version.
Status: partially conformant. The pages we tested pass every automated check we ran. Some content still has to be checked by a person, and some parts of the site were outside this test, as listed under what is still open.
2. How we tested
On 28 October 2026 we loaded each page on the live site in a Chromium browser and ran axe-core 4.11.0 with its WCAG 2.0, 2.1 and 2.2 rules at Levels A and AA. Each page ran at 1280 pixels wide and at 390 pixels wide, the width of a phone, in English and in Italian.
The six pages are the home page, the plans page, the free scan, one service page, one free tool and the sign-in page, where buying a plan starts for a visitor without an account. The sign-in page exists in English only, so we tested it in English.
We then checked by hand what axe cannot decide on its own:
- Reflow (WCAG 1.4.10): at 320 pixels wide, none of the 11 addresses we tested scrolls sideways.
- Keyboard focus (WCAG 2.4.7): we pressed Tab through the first 40 controls on each page, and every control of ours showed where the focus was. The first stop is the cookie banner, when it shows.
- Page language (WCAG 3.1.1): each page declares the language it is written in.
This is our own test, run with public tools. It is not a certification by an independent body.
3. What we found
The table counts the axe rules that applied to each page and passed, in the order English desktop, English phone, Italian desktop, Italian phone.
| Page | Address | Rules passed | Rules failed |
|---|---|---|---|
| Home page | / | 36, 34, 34, 34 | None |
| Plans | /plans | 32, 32, 33, 33 | None |
| Free scan | /get-started | 33, 33, 33, 33 | None |
| Shop accessibility audit | /ecommerce-accessibility-audit | 29, 29, 29, 29 | Color contrast, fixed on 28 October 2026 |
| Color contrast checker | /tools/color-contrast-checker | 36, 36, 36, 36 | None |
| Sign-in | /auth/login | 24, 24 (English only) | None |
The failure we fixed
The five step numbers, 01 to 05, on the shop accessibility audit page measured 1.78:1 against the background, in both languages and at both widths. Large text needs 3:1 (WCAG 1.4.3). We raised their color to clear 3:1 on every background the site uses, and gave the same color to the two other numbered lists that shared it.
Alongside the audit we added a line above the free scan conversation saying that an AI system writes the replies, so a screen reader reads it before the conversation starts.
4. What is still open
We aim to close each of these by 31 December 2026 and will update this page as we do:
- Text over images and gradients. axe could not measure the contrast of text placed over a gradient, an image or another element, and marked it for a person to check: up to 42 elements on the home page, up to 40 on the plans page and up to 11 on each of the other pages. We will check each one by hand and fix what falls short.
- A skip link. Pages are divided into landmarks that screen readers can jump between, and axe’s bypass check passes. A keyboard user without a screen reader still tabs through the menu first, so we will add a link that skips to the content.
- Screen readers. We have not yet completed a purchase from start to finish with a screen reader. We will test one with NVDA on Windows and VoiceOver on an iPhone.
- The signed-in dashboard. This test covered public pages only. We will test the dashboard with the same method.
5. Content run by others
Some steps open services that other companies run: Stripe’s checkout page for payments, the hCaptcha check on some forms and Google’s sign-in page. Their accessibility is in their hands. If one of them stops you, write to us and we will help you finish what you started.
6. Report a barrier
If something on aigrow.gg is hard or impossible for you to use, write to hello@aigrow.gg or use the contact page. Tell us the page address, what you were trying to do and what got in the way. We answer every report, and while we fix the page we send you the information or help you place the order another way.
We prepared this statement on 28 October 2026 from the test described above. We will run the test again and update this statement by 31 December 2026. If you want the same audit for your own shop, see our shop accessibility audit.