Accessibility statement
We want everyone to be able to use pleyner.com, including people who use a screen reader, a keyboard, screen magnification or other assistive technology. This statement describes the site as it is today.
Our target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The European standard for accessible products and services, EN 301 549, is built on WCAG.
Where we are
The site was built with these guidelines in mind, but it has not yet been fully tested or audited by an independent expert, so we do not yet claim full conformance. We will update this statement after an audit.
What we have done
- The page is prerendered HTML, so its text can be read without JavaScript.
- We use standard HTML controls, so that buttons, links and the waitlist form work with a keyboard and with screen readers. Dialogs close with the Escape key, and focus returns to the button that opened them.
- If you turn on reduced motion in your system settings, nothing on the page moves. With increased contrast, the site switches to a high-contrast theme. With reduced transparency, see-through surfaces become solid.
- Every page states its language and writing direction, so screen readers use the right pronunciation, and the Arabic and Urdu pages read from right to left.
Known limitations
- The interactive 3D demo is decorative. What it shows is also described in text, and it can be controlled with a keyboard, so people who cannot see or play it do not miss any information.
- Translations other than English were produced with the help of AI and are waiting for review by native speakers. They may contain mistakes. The English version is the reference.
- The legal pages are available only in English and Romanian.
Feedback and contact
If something is hard to use, or you need any content in another format, write to pleyner.ai@gmail.com and tell us the page and the problem. We aim to reply within 10 working days.
Technical details
The site relies on HTML, CSS and JavaScript, and the 3D demo uses WebGL. It is designed for current versions of the major browsers.
About this statement
This statement was prepared on 27 October 2026. We review it at least once a year and whenever the site changes significantly.