Conformance status
Architecture Platform is partially conformant with the Web Content Accessibility Guidelines (WCAG) 2.1 level AA, because of the non-conformities listed below and of a temporary exemption while Phase 3 of our action plan is being completed.
The WCAG 2.1 AA target covers EAA conformance (B2C) by construction, meets enterprise requirements (RFPs from banks, insurers and the public sector) and prepares for the RGAA 4.1 deadline (France) should arch-platform sign a central government body, a healthcare institution or a regional mutual insurer.
Conformance documentation
The detailed, criterion-by-criterion report is published in the VPAT® 2.5 INT format — the template expected both by North American procurement departments (Section 508) and by European public buyers (EN 301 549).
This document is a self-assessment, not an audit signed off by a third party. So that you can judge its exact scope, it states itself which version it was drawn up against (v0.12.2, report dated 17 September 2026), what has been reviewed since, and the known limitations — including the fact that the authenticated surface of the product is not yet covered by the automated checking described below. A re-assessment against the current version is required.
Scope of this statement
- Public pages —
/landing,/wiki+ articles,/legal/*,/changelog,/security,/help,/contact,/signup,/activate. - Sign-in page — Keycloak flow (
auth.arch-platform.com) with a custom theme that preserves the native tab order. - Authenticated application — sessions, notices, recommendations, architecture dossiers (DAS), administration, settings. Its conformance rests on a manual review: the automated checking described below does not yet cover it.
Results of the latest evaluation
- Date: 17 September 2026 (VPAT self-assessment, published above).
- Automated tooling: axe-core 4.11 via Playwright, integrated into our continuous integration pipeline. The audit is triggered on every frontend change, with a blocking threshold of 0 critical or serious violations across 15 reference public pages (landing, signup, changelog, security, help, contact, wiki + 3 articles, and 5 legal pages).
- Lighthouse score: the Lighthouse accessibility score is measured on every pull request for the entry pages (landing, signup). Internal target: ≥ 90/100.
- Static analysis: manual review of the design tokens (palette, contrast ratios), of the HTML landmarks, of the ARIA labels and of the tab order.
- Certified external audit: targeted for Q3 2026 with a RGAA-qualified firm (Tanaguru, Atalan or Access42). That deadline was not met. Our plan defers it to Phase 3 (Q4 2026); as of today, no firm engagement has been contracted. The signed report will be published on this page once available.
Known non-conformities
The following gaps remain open after the delivery of Phase 2. They fall under Phase 3 (documentation and external audit), dated Q4 2026. None of them blocks the main use of the service, but each may lead to a degraded experience depending on the assistive technologies used.
- Audit signed off by a certified firm (Tanaguru / Atalan / Access42): the internal audit, run through reproducible test scripts (VoiceOver on macOS, NVDA on Windows) over the 3 key journeys, is documented and executable. The audit signed off by an RGAA firm, which will serve as evidence for B2B buyers (banks, insurers, public sector), was targeted for Q3 2026; that deadline was not met and is still to be rescheduled.
- Visual QA at 200 % resize (WCAG 1.4.10 Reflow): automated detection of horizontal overflow at a 320 px viewport is in place in continuous integration. The visual review of internal overlaps (sidebar, KPI cards, tables) still has to be carried out page by page across the dashboard scope.
Remediation plan
The internal action plan is structured in three phases. Progress to date:
- Phase 1 (quick wins) — delivered with release v0.1.20 of 16 May 2026: recalibration of the text palette (WCAG 2.1 AA), removal of the positive
tabindexvalues inherited from the Keycloak theme, addition of skip links and semantic landmarks, axe-core safeguard in continuous integration. - Phase 2 (systematic conformance) — delivered with release v0.1.20: focus trap on modals and dropdowns, generic ARIA validation of forms (auth + DAS + Notice + team invitations + dashboard), semantic Notice stepper (
aria-current="step"+aria-labelper step),prefers-reduced-motionon animations, touch targets raised to 44×44, heading hierarchy fixed, screen-reader audit scripts written (3 key journeys), extended CI safeguard (axe-core across 15 public pages, Reflow at 320 px, Lighthouse a11y). - Phase 3 (documentation + external audit) — Q4 2026: annual audit by a certified firm, user testing with users of assistive technologies.
Reporting mechanism
If you come across an accessibility barrier not listed above, or if one of the non-conformities prevents you from using the service, contact us at support@arch-platform.com. Please state the page concerned, the assistive technology used and the nature of the barrier. We undertake to:
- Acknowledge receipt within 5 business days.
- Offer an immediate workaround where one exists.
- Communicate a remediation timeline within 15 business days.
Enforcement procedure
If you consider that you have not received a satisfactory response from us within a reasonable time, you may:
- Refer the matter to the Défenseur des droits — the French independent rights-defence and anti-discrimination authority — through its online form formulaire.defenseurdesdroits.fr.
- Contact a délégué du Défenseur des droits — one of that authority's local representatives — in your French department (list of délégués).
Normative references and method
- WCAG 2.1 level AA — W3C Web Content Accessibility Guidelines 2.1, the baseline adopted for the platform.
- EN 301 549 v3.2.1 — the European digital accessibility standard referenced by the EAA directive.
- RGAA 4.1 — Référentiel général d'amélioration de l'accessibilité, the French public accessibility framework, whose evaluation methodology is applied for manual audits.