Accessibility statement

Configuration · Accessibility statement

Displays the product’s accessibility declaration as an embedded PDF (assets/images/declaracion_accesibilidad.pdf).

Area	Configuration
Routes	configuration.accesibility · configuration.accesibility.index
Centre modules	always available
Staff levels	all authenticated
Models	—
UI label	title.header.configuration.accessibility / menu.navbar.accessibility
Coverage	2 use cases · 1 happy · 2 failure

Known issues (1)

• 🔵 Low — Accessibility statement has no PDF fallback

How it works

A static compliance page: a single <embed> at 80vh with the PDF toolbar hidden. Note the route and URL are spelled accesibility (one ‘s’) while the translation keys use accessibility, so the two spellings must be kept in mind when searching. Because it is a raw embed there is no fallback for browsers or viewers that cannot render PDFs inline. The menu entry is only offered to root, admin, manager, crmoperator, crmmanager, weboperator and content_creator — store-level, owner, sales and services users cannot reach the accessibility statement from the menu.

Use cases

Why someone opens this (2)

• Meeting the legal obligation to publish an accessibility statement.
• Pointing an auditor at the declaration from inside the product.

Path map

flowchart LR
    F(["Accessibility statement"]):::feat
    F --> H1["Statement displayed"]:::ok
    F -.-> X1["No inline PDF support"]:::bad
    F -.-> X2["Asset missing"]:::bad
    classDef feat fill:#566066,stroke:#566066,color:#ffffff,font-weight:bold
    classDef ok fill:#e3f1ea,stroke:#0d6b42,color:#0d4a2e
    classDef bad fill:#f7e6e2,stroke:#9a2d1c,color:#6e1f13

Happy paths

Statement displayed

1. User opens Configuration → Accessibility.
2. The bundled PDF renders inline at 80% of the viewport height.

Failure paths

No inline PDF support

Cause — Browser or platform cannot render PDFs in an <embed>.

What happens — No fallback content or download link is provided — the area simply appears blank, which is itself an accessibility problem on an accessibility page.

Asset missing

Cause — The PDF is absent from the build.

What happens — Unhandled; the embed renders empty.

QA checklist

Tick these off while regression-testing this feature. The boxes are plain Markdown, so progress is visible in git diffs.

• ✅ Statement displayed
• ⛔ No inline PDF support
• ⛔ Asset missing

Implementation

• app/routes/configuration/accesibility.js
• app/templates/configuration/accesibility.hbs

Translation keys (2)

Key	English
title.header.configuration.accessibility	Accessibility
menu.navbar.accessibility	Accessibility

Related

• Same area — Centre list & export · Centre editor (modules, app config, integrations) · Staff member list, deletion & restore · Staff member editor (levels, scope, API token) · Channels · Extra attributes · Email template preview & test send · Dashboard configuration · Influence zones · Server incidents · Server command runner (CLI) · Mobile app configuration · Customer login methods (Google, Facebook) · Third-party integrations & connectors · Social wifi & location services

---

Generated from doc/feature-inventory.json · id config-accessibility · commit 276788ca6