Plain-English Summary
This summary is provided for convenience only. It does not replace or override the full statement below.
- We aim to make our website and product usable by everyone, including people using screen readers, keyboard-only navigation, or magnification.
- We test against the WCAG 2.1 AA standard, both automatically on every code change and manually on key flows.
- We are not perfect yet — known gaps are documented and being fixed, and our conformance report is public.
- If something on the site is hard for you to use, email us with the page URL and we will help and prioritize a fix.
HelloGrowthCRM works to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for web experiences we control — our marketing website and the HelloGrowthCRM application.
1. Conformance status
The WCAG define requirements at three levels: A, AA, and AAA. Based on our most recent audit, HelloGrowthCRM is partially conformantwith WCAG 2.1 Level AA. “Partially conformant” means that most of the content meets the standard, while some content has known, documented exceptions that we are actively remediating.
Our conformance is documented in detail in our Accessibility Conformance Report (ACR), prepared using the Voluntary Product Accessibility Template (VPAT® 2.5). It records our support level for each applicable Level A and Level AA Success Criterion, along with any known limitations. You can read our current Accessibility Conformance Report directly, or email sales@hellogrowthcrm.com for a copy in another format.
2. How we test and prevent regressions
- Automated testing in continuous integration.Every code change is scanned with axe-core (WCAG 2.0/2.1 A & AA rulesets) and Google Lighthouse across representative pages. Builds that introduce critical or serious violations — missing form labels, unnamed controls, insufficient color contrast, invalid ARIA, or a missing page language — are blocked from release.
- Manual review with keyboard-only navigation, screen readers, and browser zoom on key flows.
- Semantic HTML, a skip-to-content link, visible keyboard focus, and predictable focus order sitewide.
- Text alternatives for informative images and icons, and support for reduced-motion preferences.
- Our last full audit was completed on July 7, 2026; we re-audit as we ship significant updates.
3. Known limitations
Despite our efforts, some content may not yet be fully accessible. Known limitations are tracked in our ACR and remediation backlog and are being addressed. If you encounter a barrier that is not listed, please tell us (see “Feedback and assistance” below) — real-world reports are the fastest way for us to prioritize a fix.
4. Third-party content
Some pages may embed third-party widgets (for example chat, analytics, or scheduling). Those vendors control their own accessibility characteristics. If you encounter a barrier tied to embedded content, tell us and we will investigate alternatives or workarounds where feasible.
5. Feedback and assistance
If you have difficulty using any part of our site or product, or need information in a different format, contact us at sales@hellogrowthcrm.com. Include the page URL, what you were trying to do, and your preferred contact method. We take accessibility feedback seriously and will respond as promptly as we can.
6. What these terms mean
Accessibility documentation uses some specialist vocabulary. In plain terms:
- WCAG (Web Content Accessibility Guidelines): the internationally recognized standard for accessible web content, published by the W3C. Version 2.1 is the edition we test against.
- Levels A, AA, and AAA: WCAG's three tiers of strictness. Level A covers the most basic requirements, AA is the widely adopted target for commercial sites (and ours), and AAA is the most demanding.
- Success Criterion: an individual testable requirement within WCAG — for example, that text has sufficient color contrast, or that every form field has a label.
- VPAT / ACR: a Voluntary Product Accessibility Template is the standard form vendors use to report conformance; the completed document is called an Accessibility Conformance Report.
- Screen reader: assistive software that reads interface content aloud or renders it as braille, used by people who are blind or have low vision.
- ARIA: a set of HTML attributes that describe interface controls to assistive technologies when plain HTML cannot — invalid ARIA can make a page harder to use, which is why our automated checks block it.
7. Related policies
For data handling and privacy practices, see our Privacy Policy. For security reporting, see Vulnerability disclosure. Security and compliance documentation is collected in our Trust Center.