Skip to main content

Last reviewed:

Accessibility Statement

Pentrova aims to make this website usable for every visitor. This statement describes the standard we hold it to, how that is checked, the gaps we know about, and how to get in touch when something is not working.

Scope. This statement covers pentrova.ai. The authenticated product console at app.pentrova.ai is built and released separately and is not covered here — we would rather say that than assert a conformance level for a surface this statement does not test.

1. Conformance target

Pentrova targets WCAG 2.2 Level AA for this website, and aligns with the European harmonised standard EN 301 549 v3.2.1 for the chapters that apply to web content.

This is a target we test against, not an audited certification. We have not commissioned an independent accessibility audit, and the known gaps in section 3 are the ones we are aware of rather than a guarantee that there are no others.

2. Assessment method

Listing only the checks that actually run, because a method section that describes intentions is worse than a short one:

  • Lighthouse CI runs on the built site and fails on an accessibility category below 100, with every axe-equivalent audit — color-contrast, the aria-* family, label, link-name — set to fail on any violation.
  • Contrast is gated at build time. Every token pair the design system can render is checked against its role threshold in both themes; the build stops if one fails.
  • Icon-only controls are gated at build time. Every page is scanned for links and buttons whose only content is an icon, and the build stops if any lacks an accessible name.
  • Manual keyboard-only walk-throughs of the primary flows — navigation, demo booking, and contact — when those flows change.

What is not yet in place, stated so you can weigh it: a per-route axe-core sweep exists in the test suite but is not wired into continuous integration, and we have not established a regular screen-reader testing cadence. Both are open work, not claims.

3. Known limitations

We are honest about where we fall short. The following gaps are tracked and being addressed:

  • Interactive diagrams in the Attack Chain showcase use motion-linked scroll annotations. A keyboard-only reader can see the final state but the intermediate annotations do not yet expose a synchronised caption track.
  • A small number of MDX-authored blog posts use inline colour-only state cues. We are rewriting those posts to add shape + text cues alongside colour.
  • The scheduler embedded on /demo is a third-party iframe. Its styling and its behaviour under prefers-contrast: more are the vendor’s, not ours, and we do not currently offer an in-house alternative to it. If it blocks you, email us at the address below and we will arrange the booking directly.

4. Feedback

If you hit a barrier on the site — a keyboard trap, a missing label, an unreadable contrast combination, a broken skip-link flow — please tell us. We read every message.

We aim to acknowledge every accessibility report within two business days and follow up with a triage decision inside ten business days.

5. Enforcement procedure

If Pentrova's response is not satisfactory, you can contact your local enforcement body. In the EU this is the national authority responsible for the transposition of Directive (EU) 2016/2102. In the United States you can contact the Department of Justice through ada.gov .

6. Review schedule

This statement was last reviewed on . We review the statement every six months and every time we ship a major change to the public site.

Site search

↑↓ navigateEnter openEsc close