Accessibility statement
We build a tool for accessible documents. It would be hard to explain if our own website were not accessible — so here is exactly where we stand, including what is not perfect.
What we aim for
This website is intended to conform to WCAG 2.1 level AA. Concretely, that means among other things:
- semantic HTML with a proper heading structure and page regions, so screen readers and browser reader modes can navigate it;
- full keyboard operation, with a clearly visible focus indicator that we never remove, and a skip link to the main content;
- text contrast above the required thresholds in both the light and the dark colour scheme;
- no information conveyed by colour alone — status is always carried by text or a symbol as well;
- text that reflows without loss of content when zoomed to 200 % and on small screens;
- animation reduced automatically when your system asks for reduced motion;
- the FAQ built on native
<details>elements, so it works fully without JavaScript.
What we know is not perfect
We would rather name limitations than claim perfection:
- The illustration on the home page is a decorative rendering of the plugin interface. It has a text alternative describing what it shows, but it is not a substitute for using the product.
- This site has been tested by us with keyboard, with browser zoom and with a screen reader, and checked with automated tooling. It has not yet been audited by an independent accessibility expert or by users with disabilities.
- The site is available in the same eleven languages as the plugin. The translations were made with care and cross-checked against the terminology used in InDesign and in the official WCAG translations, but they have not been reviewed by native-speaker professionals. The English version is the reference; if a translated page reads oddly, please tell us.
Legal status of this statement
We publish this statement voluntarily. This is a private website and, at the time of writing, we are not aware of a statutory obligation for us to provide a formal declaration under the Barrierefreie-Informationstechnik-Verordnung (BITV) or § 12b BGG, which apply to public bodies. We follow the same substance because it is the right thing to do for a product like this.
Report a barrier
If something on this site does not work for you, please tell us — that is genuinely useful feedback, and we will fix it.
Accessibility of the plugin itself
The TagAlly Pro panel runs inside Adobe InDesign, and how accessible a panel can be is partly determined by InDesign’s own extension environment. Within that, we keep the panel keyboard-operable and legible, avoid conveying status by colour alone, and write plain, jargon-free text. If you use assistive technology with InDesign and hit a barrier in our panel, we want to hear about it — the same address applies.
Statement last reviewed: 1 August 2026