Accessibility
Accessibility statement
This statement covers this website and the MagiCastor application that opens inside Moodle. It says what we have done, what we have not tested, and what remains your call as the teacher publishing the material.
It is not a conformance claim. No independent accessibility audit has been carried out yet, and we would rather say so than publish a badge we cannot stand behind.
Last updated October 2026
1. The standard we work to
We build against WCAG 2.2 level AA, which is the level EN 301 549 and the Dutch Tijdelijk besluit digitale toegankelijkheid require of public bodies. We aim to meet it; we have not been audited against it.
2. What is in place
Across this site and the application:
- every interactive control is a real button, link or form field, reachable and operable from the keyboard
- headings describe the structure of the page rather than its styling, and each page has exactly one first-level heading
- text and interface colours are chosen against the WCAG AA contrast ratios, on both the light and the dark surface
- the animated demonstration on the home page can be paused, is not required in order to understand anything, and does not play at all for a visitor whose system asks for reduced motion
- form fields have visible labels, and an error says what is wrong in words rather than only in colour
- the pages of this website work at 200% zoom and at 320px wide without horizontal scrolling
3. What we know is not covered
No independent audit, and no testing with a formal screen-reader test matrix. Our checks are keyboard, zoom, contrast and reduced motion, carried out by the people who build the product.
The application opens inside your Moodle, framed by your theme. Where your theme’s own chrome is inaccessible, we do not fix it from the inside.
Documents you upload are not made accessible by being read. An inaccessible PDF going in does not become an accessible one coming out.
4. Accessibility of generated material
The activities the product builds are ordinary Moodle activities, so they inherit the accessibility of your site and its theme in exactly the way hand-built activities do.
What the product writes, it writes as structured text: real headings, real lists, and plain language rather than layout tricks. What it cannot do is judge whether a description is adequate for a learner who cannot see the image beside it, or whether a question is answerable with a screen reader.
Generated material is a draft. Reviewing it for accessibility before you publish is part of reviewing it, and the plan step exists so that there is a point at which you do.
5. Telling us about a problem
If something here is not usable for you, write to [email protected] and say what you were trying to do and what got in the way. A person who works on the product reads every message and answers by email.
If you have raised something with us and are not satisfied with the answer, you can escalate it to the Autoriteit Persoonsgegevens where it concerns data protection, or to the relevant supervisory body for digital accessibility in your country.
Ldesign Media · Vissershavenweg 65 - III, 2583 DL The Hague, Netherlands · KvK 86167979 · VAT NL863882894B01