Accessibility Statement
Our commitment to an accessible site, the standard we build against, and how to tell us when we fall short.
- Last Updated
- August 5, 2026
- Effective Date
- To be confirmed upon formal review
- Version
- 1.0 (Draft)
This statement describes an ongoing accessibility program, assessed internally against WCAG 2.2 Level AA. It has not yet been through independent, formal accessibility certification or legal review, and should not be read as a compliance guarantee — see Known Limitations below for the specific gaps we're already tracking.
Built to work for everyone who needs to use it.
AfriGRC builds governance, risk, and compliance software for organizations across Africa and beyond — which means the people using it include compliance officers, auditors, executives, and procurement teams with a wide range of abilities, devices, and assistive technologies. We want every one of them to be able to find, read, and act on what this site tells them.
This statement describes the accessibility standard we build against, the concrete steps we've taken to meet it, and where we know we still have work to do. It is a working statement, published in good faith and updated as our practices mature — not a certification, and not legal or regulatory advice.
Substantially conformant with WCAG 2.2 Level AA.
Assessed against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the enterprise standard this site is built and audited against. 'Substantially conformant' means most content meets the standard, with the specific, known exceptions listed under Known Limitations below.
| Principle | Status | Notes |
|---|---|---|
| Perceivable | Substantially conformant | Text alternatives, captioned illustrations, and body-text contrast were audited and remediated site-wide. |
| Operable | Substantially conformant | Keyboard access, visible focus, and a skip link are in place across every page; a small number of refinements remain (see Known Limitations). |
| Understandable | Substantially conformant | Consistent navigation, labeled form fields, and programmatically associated error messages are in place site-wide. |
| Robust | Substantially conformant | Semantic HTML landmarks, heading structure, and ARIA usage were audited against WCAG 2.2 AA. |
What changed in this site's accessibility audit.
One header, one main, one footer, and a single, logically-nested heading per page, audited across all 17 marketing pages.
Every interactive component — navigation, accordions, tabs, carousels, forms — is reachable and operable without a mouse.
A consistent focus ring sitewide, plus a focus trap, Escape-to-close, and focus return on the mobile navigation drawer.
A visible-on-focus skip link at the top of every page moves keyboard and screen-reader users straight past repeated navigation.
Text-colour tokens site-wide were checked against WCAG 2.2 AA's 4.5:1 (body text) and 3:1 (large text/UI) thresholds and corrected where they fell short.
Every field carries a real label, required fields and errors are announced to assistive technology, and autocomplete is wired for common profile fields.
Every animation collapses to a simple fade (or disables entirely) when a visitor's system requests reduced motion.
Layouts were checked at 200% and 400% browser zoom without loss of content or function.
Touch targets, spacing, and layout were reviewed across desktop, tablet, and mobile viewports.
Decorative illustrations and icons are hidden from screen readers; meaningful diagrams carry a text equivalent.
Where we know there's more work to do.
Named specifically, not glossed over — an honest limitations list is more useful to you than a claim of perfection.
The desktop navigation's dropdown panels are reachable and operable by keyboard, but their position in the page's tab order doesn't yet sit immediately after each trigger — a refinement planned for a future navigation update.
Resource Library items requested as PDF exports are not yet independently verified against PDF/UA — see Technical Specifications below.
Where a future page embeds third-party content (a scheduling widget, a payment provider), that content's accessibility is governed by its own provider, not this statement.
New pages, articles, and resources are checked against this same standard as they publish, but a rolling content library means isolated gaps may still be found and corrected between review cycles.
Standards this site is built and tested against.
- Standards used: WCAG 2.2 (Level AA), WAI-ARIA 1.2.
- Built with semantic HTML5, ARIA only where semantic HTML alone was insufficient, and standard CSS/JavaScript — no reliance on plugins or technology assistive tools can't reach.
Browsers and assistive technology we build for.
Designed to standard web accessibility conventions (semantic HTML, ARIA authoring practices) expected to work with common assistive technology — screen readers, screen magnification, speech recognition, and switch access. Built and tested against current versions of Chrome, Firefox, Safari, and Edge, on both desktop and mobile operating systems; a formal assistive-technology test matrix has not yet been published.
Hit a barrier? Tell us.
We aim to acknowledge accessibility feedback within our standard support response time and to give you a plan for addressing it — not just a ticket number.
Report an Accessibility Issue
Found a barrier using this site? Tell us the page, what happened, and the assistive technology or browser you were using.
Contact UsRequest an Alternative Format
Need a page or document in a different format? Reach out and we'll work with you on an alternative.
Contact UsGeneral Feedback
Any other feedback on how AfriGRC's marketing site could be more accessible.
Contact UsHow this statement has changed.
- Established the Motion Design System's reduced-motion behaviour as the sitewide standard.
- Extended the brand palette with text-safe muted-colour tokens (bone-600, amber-700).
- Added keyboard focus management to the mobile navigation drawer.
Found something that doesn't work for you?
Tell us what happened and we'll work with you directly — or explore how AfriGRC's platform itself is built for enterprise-grade usability.