Accessibility

repeatGROWTH wants this site to be usable by as many people as possible, including people who use screen readers, keyboard navigation, magnification or other assistive technology.

1. The standard we work to

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. These guidelines explain how to make web content easier to use for people with disabilities.

We do not claim full conformance. Parts of this site have not been independently audited, and some content added over time may fall short of the standard.

2. What we have done

• Text and background colors are chosen to meet contrast requirements
• The site can be navigated by keyboard, and focus is visible as you move through it
• Headings follow a logical order, so screen readers can move through a page by structure
• Images that carry meaning have text alternatives, and decorative graphics are hidden from screen readers
• Charts and diagrams include a text description of what they show
• Layouts reflow for small screens and for zoom up to 200 percent
• Motion is kept minimal and respects the reduced motion setting in your operating system

3. Known limitations

• Some articles imported from our previous site may have images without text alternatives. We are correcting these as we review each article.
• Third-party content, such as embedded forms, is not fully under our control. We choose providers with accessibility support, but we cannot guarantee their output.
• Older documents linked from the site may not meet the same standard as the site itself.

4. Tell us about a barrier

If something on this site prevents you from doing what you came to do, tell us and we will fix it. Email support@repeatgrowth.com with the page address and a short description of the problem.

We aim to reply within 5 business days. If a fix will take longer than that, we will tell you what we are doing and when to expect it.

If you need information from this site in another format, ask and we will provide it.

5. How we test

We check pages with keyboard navigation, browser zoom, automated accessibility tooling and a screen reader. Accessibility is part of the review when we build or change a template, not a separate pass afterward.