Accessibility Statement

Our target

Greenslope — the marketing site, the documentation site, and the product UI — targets WCAG 2.1 Level AA. We adopt WCAG 2.2 as tooling defaults move; it is not a blocker today. AAA contains criteria (sign-language interpretation, 7:1 contrast) that are impractical at our current scale.

How we test

• Design-time.Every UI component includes accessibility specs: focus order, ARIA role, keyboard interaction, contrast tokens. We don’t do an “accessibility pass at the end”.
• Automated. axe-core and @axe-core/playwright run on every CI build. Any new violation fails the build. Existing violations are allow-listed individually with a linked remediation ticket.
• Manual. At least one full keyboard-only review per significant UI ship. Screen-reader spot-check (VoiceOver / NVDA) quarterly.
• External audit.V1 is self-audit. We’ll commission an external audit when the first customer requests a VPAT, or as part of the pre-SOC-2 penetration test — whichever comes first.

Known gaps

These are current, known limitations. We list them proudly rather than quietly.

• No VPAT (Voluntary Product Accessibility Template) yet. Will be produced alongside our first external audit.
• Mobile product UI is desktop-first with responsive fallback. Functional on small screens, not fully optimised. Marketing and docs are mobile-first from day one.
• Some chart visualisations don’t yet expose values to screen readers. We surface tabular alternatives alongside most charts; a complete data-table fallback for every chart is in progress.
• Dark-mode contrast has some near-AA pairs. Our design-token palette is being tightened to clear AA across all paired combinations; tracking ticket internal.
• Focus-visible rings on some custom-composed widgets are thinner than we’d like. Applies mostly to in-product dropdowns; being brought in line with the button / link ring.

Browser support

Evergreen browsers only: latest two major versions of Chrome (desktop & Android), Firefox (desktop), Safari (macOS & iOS/iPadOS 15+), and Chromium-based Edge.

Unsupported: Internet Explorer, legacy non-Chromium Edge. Chromium forks (Opera, Brave, Vivaldi, Arc) work on a best-effort basis.

Report an issue

If you hit an accessibility barrier — on the marketing site, the docs, or inside the product — please email accessibility@greenslope.io. We aim to respond within 3 UK working days.

Customer-reported accessibility issues are sev-3 minimum, higher if the gap excludes a user from a core task. We will not treat them as cosmetic.

Scope of this statement

This statement covers greenslope.io, docs.greenslope.io, and the signed-in Greenslope product at app.greenslope.io. It was last reviewed on the date at the top of this page.