Accessibility statement
Last reviewed: 16 September 2026
What this covers
This statement applies to this website and to the amana web application. It describes how accessible both are today — and where they are not yet.
We write it because an association should not shut out anybody who wants to help run it. Someone working from the keyboard rather than the mouse, reading at a large magnification, or listening through a screen reader has to be able to audit the books like everybody else.
Conformance status
Both surfaces are partially accessible. We work towards the WCAG 2.2 level AA success criteria and EN 301 549.
That assessment is our own. No independent body has audited either surface so far, and until one has, this status is a statement about our own work rather than an audit result.
What is in place
Measured, not claimed:
- Every operable element shows a visible focus ring the moment the keyboard reaches it. A mouse click does not raise it — the ring is there for the keyboard.
- Menu rows and tabs are at least 44 pixels tall.
- Control borders sit at 3:1 or better against their ground, and muted text at 4.7:1.
- The interface is available in German, English, Turkish and Arabic; Arabic runs fully right to left.
- A required field is not only marked with an asterisk — it is named as required to a screen reader too.
- Messages carry their meaning in the wording, not in the colour alone. An error message does not vanish on a timer; it stays until it is dismissed.
- The line for hints and errors is reserved from the start, so text that appears does not shift the page out from under the pointer.
- Every page opens with a skip link straight to the content.
- This website loads no third-party fonts, scripts or content, and everything needed to read it works without JavaScript.
What is not accessible yet
We know about these:
- The web application paints its interface onto a canvas rather than as HTML. It does report its structure to assistive technology, but how well that lands depends more on the particular tool than it would on a conventional web page, and we have not worked through every common combination.
- Wide tables scroll horizontally. Whether that region is announced everywhere as its own scrollable area has not been checked through.
- PDF documents amana produces — statements, reports, notices — carry no structure tags, which makes them less accessible than the interface itself.
- A few charts still carry their point graphically only, without an equivalent in text.
- There is no video or audio content at present. As soon as there is, it will need captions and a transcript.
How we assessed this
The points above rest on a self-assessment: contrast values are measured, target sizes and focus behaviour are held in place by the automated test suite, and all four language versions are fully translated.
An external audit and a session with people who use assistive technology are still outstanding. Both are planned before the site goes into public production, and this statement will be updated with the result.
If something does not work
If you run into a barrier, write to us. Please say where it happened and what you were working with — browser, operating system, assistive tool. That is the fastest route to fixing it.
We answer as quickly as we can. If our answer does not help, you can turn to the German market surveillance authority for the accessibility of products and services. We will add its full details here before the site goes into public production.
Feedback and contact: redouane.dali@outlook.com