Short answer
GCC Now™ wants everyone to be able to use gccnow.ai. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and we test every page against that standard before it goes live.
Last reviewed Nov 3, 2026
Draft for legal review. Items in [brackets] are placeholders to be completed by counsel before launch.
Last updated: Nov 3, 2026.
What we've done
- Semantic structure, with one main heading per page and labelled landmarks.
- Keyboard access to every link, menu, form and tool, with a visible focus indicator.
- Text contrast of at least 4.5:1, and type that resizes to 200% without loss.
- Labels and error messages on every form field.
- Respect for reduced-motion settings.
- Automated accessibility checks on every page in our release tests.
Known limitations
- Some partner badges are images supplied by third parties; each has a text alternative.
- Linked third-party sites and documents may not meet the same standard.
- [Other limitations found in the pre-launch audit.]
Report a barrier
If something doesn't work for you, tell us at [accessibility@gccnow.ai] with the page address and what happened. We aim to reply within [5 business days] and will offer the information in another format if we can't fix the barrier quickly.
Assessment
This statement is based on [self-assessment and an external audit by an auditor, on a date]. We review it at least once a year.