This site is built to be usable with a keyboard, with screen magnification and with a screen reader. This statement is published voluntarily, based on a self-assessment, and is updated together with the site.
How far the site conforms
The target is WCAG 2.1 level AA and the European standard EN 301 549. At the last review the site largely meets those requirements: the core criteria are in place, and the known exceptions are listed below.
What has been done
- Semantic markup: one first-level heading per page, a heading hierarchy with no skipped levels, and page landmarks — header, main content, footer, navigation — marked up and labelled so they can be told apart in a landmark list.
- Everything works from the keyboard, and the focus indicator is always visible.
- Text contrast against the background is at least 4.5:1, and at least 3:1 for large text. Every colour pair was checked by calculation, not by eye.
- Links and buttons have a target area of at least 44 × 44 pixels.
- Animation is switched off when the operating system asks for reduced motion.
- Fonts and scripts are served from this site, with no external delivery networks: the page keeps working and does not depend on someone else’s servers.
- Images are given text descriptions.
- Accessibility overlays are not used. They do not fix the problem, they hide it, and they often get in the way of people who arrive with their own assistive technology.
Known limitations
- Some images in the blog are still temporary; final text descriptions will follow once the final artwork is in place.
- The booking calendar and the chat assistant are third-party components. Their accessibility is the vendor’s responsibility. If they get in your way, write to me and I will offer another route: email, phone or messenger.
- Video testimonials are published without captions. A text transcript is available on request.
How to report a problem
If something on this site cannot be read or activated, write to [hello@sergey-raevsky.com](mailto:hello@sergey-raevsky.com). I reply within one working day. Tell me what you are using — browser and assistive technology — and which page the problem is on, and I will fix it faster. The content of any page is available in an accessible format on request.
How this statement was prepared
The method is self-assessment. It covered markup and page landmarks, calculated contrast for every colour pair, a keyboard-only pass through the pages, and layout checks at screen widths from 320 pixels.
Prepared on 26 July 2026.