---

Accemic Technologies GmbH provides its products and services exclusively to business customers. This public website is not offered as an e-commerce service aimed at concluding consumer contracts and, on the basis of its current scope, is therefore not subject to the accessibility information requirements of the German Accessibility Strengthening Act (BFSG).

We nevertheless treat accessibility as an engineering requirement and publish the technical status below voluntarily.

What we did

Color is never the only signal. Every status - in coverage tables, in the target matrix, in the documentation - carries a glyph or a word in addition to its color. You can read this site in grayscale.

A color-vision-aware palette. Status colors are based on a color-vision-aware palette (Okabe-Ito) and are never the sole carrier of meaning - every status also has a word, glyph, pattern or shape. Where a pass/fail distinction is needed we use blue and vermillion rather than green and red.

You can check that claim yourself: the coverage demo has a color vision simulation built in. Switch it to deuteranopia and see whether the report still works. Then switch the palette to the classic red/green scheme and see what happens.

Measured contrast. Text, controls and status indicators are checked against the applicable WCAG contrast criteria; the measured ratios are recorded alongside the color definitions in the site’s stylesheet. In the current release, body text measured 10.0:1 in the dark theme and 12.6:1 in the light theme; the lowest-contrast text measured 4.6:1 against the WCAG 2.1 AA minimum of 4.5:1. We deliberately sit below maximum contrast - a very light text on a very dark ground is technically excellent and tiring to read.

Both themes. Light and dark, following your system preference, with a manual toggle that is remembered.

Keyboard and structure. Visible focus indicators, a skip-to-content link, one h1 per page, proper table headers on data tables, and a language attribute on every page. Two-column signpost tables carry no header row at all - deliberately, so screen readers do not announce empty column headers.

Nothing loaded from a third party in the render path. Besides the privacy benefit, this is what keeps the site usable on a slow or filtered connection.

What is still missing

This technical statement is not a claim of complete WCAG conformance. It records implemented measures and known gaps for the named website release.

• Reduced motion. The site respects prefers-reduced-motion for CSS animation and scrolling, but the animated graphics on the home page and on the CEDARtools.Forge page do not: they run their own timers inside a shadow root, where the site-wide rule does not reach. If you have asked your system for reduced motion, those animations keep moving.
• Testing with real users. A simulation shows whether a distinction survives a transform. It does not tell you whether the page is pleasant to use with a screen reader, and we have not done that testing.
• The older material. Documents and images inherited from the previous site have not all been checked. Where an image is missing its alt text, it is on the list, not overlooked.

Found something

Accessibility problems are bugs. Tell us and we will fix them.