Accessibility and operation without JavaScript

The core function of every tool runs without JavaScript. The forms are server-rendered and submittable, and so are the results. JavaScript adds convenience — and in three places rather more than that.

What is unavailable without JavaScript

Not available	What stands in instead
Drag and drop, the file list, the size check in the browser	choose the file through the file field; the server checks the size as well
Adding or removing rows in the create form	the server-rendered rows (one line item in an empty form); the step wizard falls away and all six sections sit one below the other
The PDF preview in the review step of “PDF to e-invoice”	a note on the page: “JavaScript is required for the PDF preview. You can check the recognised values on the right without it.”

Without JavaScript the create form is submittable in one go

Instead of the step wizard, all six sections sit one below the other. The server-side mandatory check runs unchanged and collects all shortcomings at once.

The standard

WCAG 2.1 level AA and EN 301 549. The accessibility statement at /en/accessibility — reachable from the footer of every page — states the current position and the known limitations.

Two stated limitations

Validation messages without a translation appear in German and are marked as such, so that a screen reader switches language correctly. Rule IDs and BT references are language-neutral.

Generated PDF files are only tagged as PDF/UA if the installation has that switched on — the default is off.

Your own Word templates cannot deliver an accessible PDF

This is not a matter of configuration but a property of the route: the DOCX-to-PDF conversion writes an empty structure tree and not a single tagged content element. Only the natively drawn layouts of the in-house invoice renderer can be tagged. Anyone who needs an accessible PDF does not choose their own template. See Your own Word templates.

How confidence is indicated

In the review step of “PDF to e-invoice”, highlights and field borders are colour-coded by recognition confidence. Because colour alone must not carry information, every field also carries the same value as a hidden label — such as “Recognition: check” — for screen readers.