Accessibility statement
Agonist Development AB (Sweden, org.nr 559452-5726) commits to making the ariada.org website accessible per the European Accessibility Act 2025, EN 301 549 v3.2.1, WCAG 2.2 Level AA, and the Swedish Lag (2018:1937) om tillgänglighet till digital offentlig service (DOS-lagen).
Conformance status
This website is partially conformant with WCAG 2.2 Level AA. The reasons for the partial conformance are listed below under non-conformance items. We disclose these honestly because we publish accessibility tooling and believe public self-disclosure is the Commons-friendly default.
Methodology
- Scanner:
@ariada-org/wcag-rules-extended v0.1.0-pre— our own open-source rule pack (EUPL-1.2). Source repository is live atgithub.com/ariada-org/ariada. - Cross-tool baseline: in addition to our own rule pack, every release-candidate build runs against the upstream axe-core baseline and the pa11y command-line tool. We compare results so a regression in one tool surfaces against the others.
- Standards covered: WCAG 2.2 AA, EN 301 549 v3.2.1, EAA Annex I, and EN 301 549 art. 7 accessibility-statement compliance.
- Scan cadence: on every production build,
pre-deploy. Raw self-cert artefacts land under
audits/self-cert/2026-05-15-ariada-org-*.jsonin the source tree and are intentionally not gated behind any credential wall. - Last evaluation: . Next scheduled review: rolling, with every release.
- Procedural constraint — scanner injection:
the site Content-Security-Policy declares
script-src 'self'as a security hardening, which means in-browser evaluators cannot inject axe-core directly from DevTools. To independently re-verify, clonegithub.com/ariada-org/ariadaand runpnpm test:distagainst this site, or install@axe-core/clilocally and point it athttps://ariada.org. This is a procedural limitation, not a WCAG failing.
Non-conformance items (current)
The following items were detected by the most-recent self-cert scan and are tracked publicly for remediation:
- ariada/banking/lang-matches-locale — WCAG 3.1.1.
Status: known scanner gap, fix queued for v0.2.0.
The selector fires on this page because the rule's
body.textContentscan does not yet honour inline<span lang="...">markers. The page declares<html lang="en">as its primary language and wraps every Swedish proper noun and legal reference (e.g. «Lag (2018:1937) om tillgänglighet till digital offentlig service», «Myndigheten för digital förvaltning») in<span lang="sv">per WCAG 3.1.2 Language of Parts. The rule should respect those markers and re-scan only un-wrapped text. That enhancement is queued for rule-pack v0.2.0. The page itself is conformant; the rule produces a false positive on the specific Language-of-Parts pattern. - ariada/statement/last-revision-date — EN 301 549 art. 7.
Status: resolved 2026-05-15.
The earlier first-match-only regex returned an in-page quote of
the phrase «last reviewed» rather than the actual revision date
further down in the Provenance section. Fixed by switching to
matchAllover every occurrence; the rule now passes when any occurrence has a date in its 80-char window. - CSP scanner-injection constraint — procedural, not a WCAG failing.
Status: documented, not a defect.
Our site
Content-Security-Policysetsscript-src 'self'as a security hardening. As a side effect, third-party accessibility evaluators cannot inject axe-core directly from browser DevTools. To independently verify, see the procedure in the Methodology section above. We document this rather than weaken the CSP.
For each item we provide the WCAG success-criterion mapping, an EN 301 549 paragraph cross-reference, and the remediation track in the public issue tracker. If a regression appears in a future build, it shows up here.
Feedback
If you encounter an accessibility barrier on ariada.org, or if you believe we have understated our non-conformance, please contact us at hello@ariada.org with the page URL and a description of the issue. We aim to acknowledge reports within 5 business days and to publish a remediation track within 14 business days.
Enforcement procedure
If you are not satisfied with our response to your accessibility feedback, you can escalate to the Swedish enforcement authority for digital accessibility:
- Myndigheten för digital förvaltning (DIGG) — https://www.digg.se/digital-tillganglighet.
- EU citizens outside Sweden: contact your national digital-accessibility enforcement body. We will cooperate with cross-border requests under the European Accessibility Act framework.
Standards referenced
- WCAG 2.2 Level AA — W3C Web Content Accessibility Guidelines
- EN 301 549 v3.2.1 — harmonised European standard for ICT accessibility (canonical PDF on etsi.org)
- Directive (EU) 2019/882 — European Accessibility Act
- Lag (2018:1937) — Swedish DOS-lagen on digital accessibility
Provenance
- Statement published:
- Last reviewed: by Alexander Brichkin (Agonist Development AB)
- Generated by:
@ariada-org/wcag-rules-extended v0.1.0-preDelta 6 statement generator.