Accessibility Declaration

Published 20 August 2026 · Last reviewed 20 August 2026 · Next review due 20 February 2027

Hyperion Consulting is committed to making this site usable by everyone, including people who use assistive technology. This declaration is issued under Directive (EU) 2019/882 (the European Accessibility Act), transposed into French law by Ordinance No. 2023-859 of 6 September 2023 and applicable since 28 June 2025, and under Article 47 of French Law No. 2005-102 of 11 February 2005. It applies to hyperion-consulting.io in all published languages. Hyperion is a private practice, not a public-sector body, so the public-sector accessibility directive does not apply to it and no exemption under that directive is claimed here.

0. Applicable standards

This site is measured against the following standards. The conformance target is WCAG 2.2 Level AA.

  • WCAG 2.2 Level AA (W3C) — the target this site is built and tested against.
  • EN 301 549 (European harmonised accessibility standard), which incorporates WCAG.
  • RGAA 4.1.2 — the French assessment methodology, used as the review checklist.
  • Directive (EU) 2019/882 (European Accessibility Act), as transposed into French law.

1. Conformance status

Partially conformant with WCAG 2.2 Level AA

"Partially conformant" means parts of the site do not yet fully meet the standard. This status rests on an internal self-assessment supported by automated testing, described in section 3. No third-party audit has been commissioned and none is claimed. Manual validation with screen readers has not yet been carried out, so this declaration states what has been verified, what is known to fall short, and what has not been checked at all — rather than presenting an automated result as conformance.

2. Non-accessible content

Automated testing can detect only part of the WCAG success criteria — roughly a third — so a clean automated result is evidence, not proof. The known shortfalls are listed below. Anything not listed has not necessarily been verified.

Known limitations (verified and open)

  • Many horizontally scrollable areas — wide tables and diagrams — can be scrolled with a pointer but not reached with a keyboard, particularly at narrow widths and under text zoom (SC 2.1.1). A keyboard-reachable scroll region has been introduced and is being applied across the remaining cases.
  • Text inputs and similar controls have a clear focus indicator, but their unfocused borders and fills do not reach the 3:1 non-text contrast ratio (SC 1.4.11), so an empty field is harder to perceive than it should be.
  • The JARVIS assistant panel streams its replies into a live region, which can cause a screen reader to re-announce text as it arrives, and its animated face does not yet honour a reduced-motion preference.
  • Some interface strings and accessible names — in the site search, the language switcher and parts of the footer — remain in English in every language (SC 3.1.2).
  • Automated checking covers the English routes and two French routes and fails a release only on serious and critical findings. Dutch, the right-to-left Arabic layout, and moderate-severity findings are not yet part of that gate.
  • Interaction states — the open mobile menu, the search dialogue, the cookie preferences panel, the assistant panel — are not yet covered by automated checking. Their status is unverified rather than known to be good.
  • Reflow has been checked at 375 and 390 CSS pixels but not yet at 320 (SC 1.4.10).

Disproportionate burden

Not applicable. No exception is claimed on the basis of disproportionate burden.

Third-party content outside our control

  • The Calendly scheduling widget on the booking page is a third-party embed rendered inside an iframe. Its internals are excluded from our automated checks and we cannot correct them. It loads only if you choose to load it, and the same page offers a plain email alternative, so nothing depends on it.
  • Content on external sites we link to is outside our editorial control.

2.bis Remediation plan

The limitations above are worked in the order below. Deliberately, no target date is attached to an item whose date could not be honoured; instead this declaration carries a fixed review date (section 3) and the list is republished with it.

  • 1Apply the keyboard-reachable scroll region to the remaining scrollable tables and diagrams.
  • 2Raise the unfocused contrast of form-control borders and fills to at least 3:1.
  • 3Extend automated checking to Dutch, to the right-to-left layout, and to the open state of the menu, search, cookie panel and assistant panel.
  • 4Carry out manual validation with a screen reader on Windows, macOS and Android, and publish what it finds — including anything it contradicts in this declaration.
  • 5Re-enable the accessibility rules in the code linter so that regressions are caught before review.
  • 6Add a 320-pixel reflow check to the automated suite.

3. Preparation of this declaration

This declaration was prepared on 20 August 2026 by internal self-assessment. Precisely what that assessment consisted of: an automated axe-core audit driven through a headless browser across roughly 150 English routes plus French routes, at desktop and mobile widths, which runs again in continuous integration and blocks a release on any serious or critical finding; Lighthouse accessibility audits against the live site; and a review of the code against the standards in section 0. Automated tooling reaches only part of WCAG, so this is evidence of the absence of a class of defect, not of conformance. No third-party audit has been commissioned, and no screen-reader testing session has been carried out. An earlier version of this declaration described such a session and named the assistive technologies used; that was not accurate and has been removed.

Published 20 August 2026. Last reviewed 20 August 2026. Next review due by 20 February 2027, or sooner if the site changes significantly.

4. Feedback and contact

If you cannot reach a piece of content or use a service on this site, tell us. We will provide the content in another form or point you to an accessible alternative, and your report goes onto the list in section 2.

Contact methods

We aim to respond within 2 business days.

5. Enforcement procedure

Use this procedure if you have told us about an accessibility defect that prevents you from reaching content or using a service on this site, and you have not had a satisfactory answer.

  1. 1Write a message to the Défenseur des droits (French Ombudsman).
  2. 2Contact the Défenseur des droits delegate in your region.
  3. 3Send a letter by post (free of charge, do not put a stamp on the envelope).

Défenseur des droits

www.defenseurdesdroits.fr

6. Technical information about this site's accessibility

Technologies this site relies on

HTML5CSSJavaScriptReact / Next.jsWAI-ARIA

Test environment

The results above were produced in the environment below. It contains no assistive-technology session: manual screen-reader validation is still outstanding and is item 4 of the remediation plan.

  • axe-core, driven by Playwright, on Chromium at a desktop viewport
  • axe-core, driven by Playwright, on an emulated mobile viewport
  • Lighthouse accessibility audits against the production site
  • Not yet performed: any session with NVDA, JAWS, VoiceOver or TalkBack
Accessibility Declaration | Hyperion Consulting