Skip to main content

Accessibility Statement

This wiki is a platform on which several organisations each run their own wiki: reading, writing and co-editing pages, commenting, searching and administration. We measure against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, and the European standard EN 301 549. This statement covers the platform itself — not the content an organisation publishes in its own wiki.

Conformance status

This service is partially conformant with WCAG 2.2 Level AA. We know of one deviation, on the error page for an unknown address. Some things also cannot be machine-tested and have not yet been walked with real assistive technology. All of it is set out below.

What already works

  • Automated testing covers sign-in, page view, search, history, the editor, the new-page form, notifications, an organisation's home page and every settings page. Apart from the contrast failures named below it reports no deviations. No rule is disabled and no region is excluded.
  • At 400% zoom — roughly 320 pixels wide — content stays readable in a single column with no sideways scrolling; the page tree moves into a collapsible drawer. Verified at 320, 390, 768 and 1440 pixels.
  • The platform's colours come from a shared design kit whose contrast ratios are checked before every release. Buttons darken on hover rather than turning translucent — translucent overlays had previously pushed contrast below the threshold unnoticed.
  • Keyboard operation, labelling and heading structure are additionally checked automatically on every change.
  • An organisation can set its own primary colour for its wiki. The colour is only accepted, and only applied, if button labels, links and highlighted entries still reach a contrast of at least 4.5:1. The check runs when the colour is saved and again whenever a page is shown, so a colour stored before the check existed is ignored rather than used.

Non-accessible content

We know of one deviation:

  • When an address does not belong to an active wiki, an error page appears. That page does not declare its language, so a screen reader may pronounce it incorrectly. This affects WCAG 3.1.1 (Level A). The cause is the Next.js framework: it renders error pages in an internal shell of its own and discards the language attribute. We deliberately chose not to work around it, because the only available fix would replace the 404 error code with a false success code. The page is therefore written bilingually, and the legal links are present on it. We are waiting for the framework fix.

Not yet assessed

Four things cannot be machine-tested and have not yet been walked with real assistive technology:

  • The editor toolbar: a full keyboard walkthrough, and how well a screen reader announces the state of its buttons.
  • The page tree and the user menu: a keyboard walkthrough, and a judgement on whether the focus ring is visible enough everywhere.
  • Comments: whether the result of submitting a reply is announced by a screen reader.
  • The suggestion list that appears when mentioning someone with “@”: how well a screen reader announces it.

Beyond that there has been no full screen-reader pass and no external audit.

How we tested

This statement is based on an internal self-assessment. Automated testing uses axe-core and Playwright, last run on 17 September 2026 against the running application, with no deviations reported. The two contrast failures named in the previous version of this statement — the active sidebar item and the “current” marker in the version history — were fixed when the wiki moved onto the shared supodo interface components; the tinted surfaces behind them no longer exist. The automated check does not yet run as part of our release pipeline. This is supplemented by static code analysis that runs on every change.

What we are doing next

We are switching on the automated check in our release pipeline, so that a regression cannot go unnoticed again. And we will carry out the four assessments listed above with real assistive technology. We will update this page as the situation changes.

Feedback and contact

Have you found a barrier that is not listed here? Or do you need content in a different form? Let us know. We reply within two weeks.

accessibility@supodo.com

Competent market surveillance authority

If you are not satisfied with our reply, or receive no reply at all, you can contact the competent market surveillance authority:

Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen – Anstalt öffentlichen Rechts (MLBF AöR)

Carl-Miller-Straße 6, 39112 Magdeburg

mlbf-barrierefrei.de

This statement was last reviewed on 17 September 2026