How this site is built
Accessibility
A site about making learning reachable has no business being hard to use. Here is what we have actually done, what we know is not finished, and how to tell us when something gets in your way.
Our target
We build this site to meet WCAG 2.2 Level AA. That is the standard we measure ourselves against, and we treat a failure against it as a bug rather than a nice-to-have.
A target is not a certificate. We have not been through a third-party audit, and we are not going to describe ourselves as fully conformant when nobody independent has checked. What follows is a plain account of the work.
What has been done
Structure and semantics
Pages are built from real HTML elements — headings, lists, landmarks, buttons, and labelled form fields — rather than styled div soup. Each page has oneh1 and a heading order that does not skip levels, so a screen reader's heading list reads as an outline of the page. Sections are labelled by their own headings, and every page starts with a "skip to main content" link.
Keyboard operation
Everything on this site can be operated with a keyboard alone. There are no custom widgets that trap focus, no menus that require a hover, and no controls that only respond to a mouse. Focus order follows the visual order of the page.
Visible focus
Every focusable element shows a clear focus outline. We never remove focus styling to tidy up a design, because for a keyboard user that outline is the cursor.
Contrast and text
Colors are chosen to meet the AA contrast ratios for text and for interface elements. Body text is never smaller than 18 pixels, and the smaller size is reserved for captions and legal notes. Text scales when you zoom or raise your browser's default font size, and the layout reflows rather than breaking.
Never color alone
Program status, form errors, and every other piece of meaning carried by color is also carried by words. A badge says "Active now" or "Planned" in text, not just in a shade of green.
Reduced motion
The site respects the "reduce motion" setting in your operating system. If you have it on, transitions and movement are switched off rather than merely made shorter.
No carousels, no autoplay
Nothing on this site slides, rotates, or starts playing on its own. There is no audio or video that begins without you asking for it, and no content that moves out from under you while you read.
No cookie banner
There is no consent pop-up, because there is nothing to consent to. We do not use advertising or tracking cookies. Nothing covers the page you came to read.
Forms
Every field has a visible label that is properly associated with its input, required fields are marked in text as well as with an asterisk, and hints sit next to the field they describe. When a form is submitted, the result — success or failure — is announced to screen reader users through a live region, and error messages name the field and move focus to it. Forms work without JavaScript.
Images and links
Meaningful images carry real alt text that describes what matters about them. Purely decorative images are hidden from assistive technology instead of being read aloud. Link text describes where the link goes, so a list of links read out of context still makes sense.
Known limitations
We would rather list these than let you discover them.
- No independent audit yet. Testing so far has been done by us, using keyboard navigation, screen readers, zoom, and automated checks. That catches a great deal and it is not the same as an expert review by a person who uses assistive technology daily.
- Limited assistive technology coverage. We have not tested against every combination of screen reader, browser, and operating system. Older or less common combinations may behave differently.
- The form spam check is a third-party widget. Where a challenge is used to keep out automated submissions, its behavior is not entirely under our control. If it blocks you, email us and we will take your information directly — no challenge, no form.
- Off-site pages are not ours. Links to other organizations, including the sister sites in this mission, lead to pages we do not build and cannot promise anything about.
- Downloadable documents. We do not publish PDFs today. When governance documents are eventually posted, tagged and readable versions are the standard we will hold ourselves to, and we will say so on the page.
- Plain-language work is ongoing. Cognitive accessibility is not only a technical matter. If a page here is harder to follow than it needs to be, that is a real accessibility problem and we want to hear about it.
Tell us when something blocks you
If any part of this site is difficult or impossible for you to use, emailhello@igrowthfoundation.org and put "Accessibility" in the subject line. It helps if you can tell us the page, what you were trying to do, and what happened instead, plus the browser and any assistive technology you were using. Even a one-line message is worth sending.
We read these ourselves and we aim to reply within a few days. We are a small operation, so a fix may take longer than the reply does — but we will tell you honestly whether we can fix it and roughly when.
And if the site is what is standing between you and getting help, do not fight with it. Email us and we will handle the whole thing by email or arrange a phone call. Nobody misses out on training because of a web page.
Scope of this statement
This statement covers the pages published at https://igrowthfoundation.org. It does not cover other organizations' websites we link to, or third-party services such as the email provider used for the newsletter.
We will revise this page as the site changes and as we learn where it falls short. See also our privacy notice andterms of use.