Fiatside

Legal document

Accessibility statement

An accessibility statement that lists no defect is a statement that was never tested. This one names the known non-conformities and how they are tracked.

Version
1.0.0
Effective from
15 September 2026
Last updated
2 September 2026

This document is a template and must be reviewed by legal counsel before going to production

The text below was drafted from the obligations applicable to a digital asset service provider, but it has not yet been validated by a lawyer in the jurisdiction of establishment. It is therefore not enforceable as it stands and must not be treated as a final contractual commitment.

Document contents
  1. 01Commitment and target level
  2. 02Conformance status
  3. 03Known non-conformities
  4. 04Evaluation method
  5. 05Report a barrier
01

Commitment and target level

We target level AA of the Web Content Accessibility Guidelines, version 2.2, which is the level adopted by the European standard applicable to digital services. This document says where we actually stand, including what does not conform.

An accessibility statement announcing full conformance without listing a single defect has not been tested. We prefer a partial and accurate statement to a complete and false one — the same rule as everywhere else on this site.

02

Conformance status

Partial conformance. The foundations hold across the public site; specific points remain non-conformant and are listed below with their consequence for the user.

What holds on every public page

  • A single level-one heading per page and a heading hierarchy with no skipped level, which makes heading navigation usable with a screen reader.
  • A skip link at the top of the page, leading straight to the main content.
  • Text contrast meeting level AA in both themes, light and dark, including on secondary labels.
  • Visible focus on every interactive element, not removed by styling: keyboard navigation stays legible everywhere.
  • No content reachable only on hover: whatever appears on hover is also reachable by keyboard.
  • Wide tables scroll inside their own container; the page itself never scrolls horizontally.
  • Decorative icons are hidden from assistive technology; buttons without text carry an accessible label.
  • Motion is disabled when the system signals a reduced-motion preference.
  • The page language is declared and genuinely changes between the French and English versions.
03

Known non-conformities

The following points are identified and tracked. We publish them before fixing them, because someone affected needs to know what to expect today, not next quarter.

ItemConsequence for the userStatus
No external audit has been carried out yetThe claims on this page rest on internal self-assessment: they may miss a defect a third-party audit would catch.Audit planned before go-live
Wide comparison tablesOn a small screen, reading requires horizontal scrolling inside the table, which stays awkward with a screen reader despite the column headers.A stacked list view is under consideration
Explanatory diagramsFlow diagrams do not yet have an equivalent long description: their content is summarised but not fully described.Long descriptions being written
Legal documentsNo plain-language version is offered. The texts stay long and technical, which in practice excludes part of the readership.Per-section summaries under consideration
Testing with assistive technologyJourneys have been checked by keyboard, but not yet end to end with a mobile screen reader.Test campaign scheduled
04

Evaluation method

  • Manual keyboard verification of every public journey: navigation, tab order, focus return, exiting collapsible components.
  • Contrast verification on both themes from the design system’s colour variables rather than page by page: a conformant token makes everything that uses it conformant.
  • Review of semantic structure: heading levels, lists, tables with headers, landmarks.
  • No automatic remediation tool is installed. Accessibility overlays generally degrade the experience of people already using assistive technology, and hide defects instead of fixing them.
05

Report a barrier

If a page prevents you from completing an action, describe the barrier: the page address, what you were trying to do, and the hardware or software you use. A precise report is worth more than a generic audit.

Report an accessibility problem

Subject “Accessibility”. Answer within 5 business days with a clear position: fix planned, fix impossible and why, or an immediate workaround.

[email protected]

If our answer does not satisfy you, you can refer the matter to the competent digital accessibility authority in your country. That right is open independently of our internal procedure.

06

Version history

VersionLast updatedNature of the change
1.0.02 September 2026First publication of the document.

Stable anchors: every section carries an identifier that will not change. You can cite a clause by its direct link.