Accessibility Statement
Last updated: 28 October 2026
This website and the Special Virtual Academy are made for young people with intellectual disabilities. Being usable is not a feature here; it is the whole point.
The standard we follow
We aim at the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.
For everything a learner reads, we also follow the European Easy-to-Read rules written by Inclusion Europe together with people with intellectual disabilities: short sentences, one idea per sentence, everyday words, no abbreviations and a picture next to the text.
What we have done
- Large text. The base size is 18 pixels and everything grows from there.
- Large buttons, at least 48 pixels high, with space around them.
- The same layout on every lesson screen: Back, Next and Listen are always in the same place.
- One idea per screen, and one main action per screen.
- A Listen button that reads the text out loud in the language of the page.
- Full keyboard use, with a thick focus ring that stays visible on every background.
- No dragging anywhere. Every game works by tapping, with a finger, a mouse or the keyboard.
- No time limits, no scores that go down and no red crosses. A wrong answer gives a hint and a new try.
- Movement is reduced automatically for anyone whose device asks for less motion.
- Text alternatives for every picture that carries meaning; decorative drawings are hidden from screen readers.
- Colours chosen for contrast, and never colour alone to carry a meaning.
- The site works down to a 375 pixel wide screen without sideways scrolling.
What is not perfect yet
- The Listen button uses the voices built into the browser. On some devices a voice for Bulgarian or Turkish is missing, and then the button does not appear.
- The project documents are offered as PDF files. They are not yet fully tagged for screen readers.
- The Turkish version was translated by the project team and is waiting to be read by our Turkish partner.
- The contact form is not connected yet, so a message can only be sent by email for now.
How we check
The project team checks the pages by hand, with the keyboard and on a phone, and reviews the wording against the Easy-to-Read rules.
On top of that, an automatic accessibility test runs over the key pages every time the website changes, so a problem is caught before it reaches anyone.
Tell us about a problem
If a page is hard to use, we want to know. Write to us through the Contact page and say which page it was and what happened. We will answer and we will fix what we can.
