Accessibility and help
I aim to make this website usable for everyone and use WCAG 2.2 AA as a design target.
The site uses semantic headings, navigation landmarks, a skip link, labelled forms, visible focus styles and reduced-motion preferences. These measures support accessibility but still need testing with different users and assistive technologies.
Published automated test results
The homepage and the side-project launch guide each scored 100/100 for automated accessibility in Google Lighthouse mobile and desktop reports captured on 26 October 2026 at 23:43–23:44 UTC (27 October in Belgrade). These results apply to those two English pages and the versions tested, not every page, language, device or future update.
View the reports:
A score of 100 means the scored automated checks passed in those runs. Lighthouse does not include manual checks in its score. It is not a certification of full WCAG compliance or a guarantee that no accessibility barriers exist. Full screen-reader testing, manual mobile/tablet checks and end-to-end form and booking testing remain outstanding. PDF accessibility has not been fully verified; readable HTML guides are available.
Performance is measured separately
In the same reports, homepage performance scored 99/100 on mobile and 100/100 on desktop; the guide scored 100/100 on both. Performance checks such as caching, layout stability, JavaScript work and image dimensions are separate from accessibility. Scores and timings vary by page, connection and test run; no real-user Core Web Vitals data was available.
16 passed performance audits in the linked homepage desktop report
Historical results for that page and run. “INP breakdown” in this list does not establish a real-user INP measurement.
- Use efficient cache lifetimes
- Document request latency
- Duplicated JavaScript
- Font display
- INP breakdown
- LCP request discovery
- Legacy JavaScript
- 3rd parties
- Optimize viewport for mobile
- Reduce unused JavaScript
- Avoids enormous network payloads
- User Timing marks and measures
- JavaScript execution time
- Minimizes main-thread work
- Avoid non-composited animations
- Image elements have explicit width and height
Known limits and third-party services
Cal.com booking, Vimeo video, Google Maps, Google Meet and payment services have their own interfaces, which I cannot directly change. The Google map is optional and loads only when you open it. If an external service creates a barrier, contact me so we can discuss another way to access coaching.
Accessibility and help
If you encounter a barrier, contact me using the form or WhatsApp or Telegram. Please share the page URL, what you were trying to do and what happened. Browser or assistive-technology details can help but are optional; you do not need to disclose a diagnosis. I aim to acknowledge messages within two business days and agree on a practical next step, such as help booking or an alternative format. This is a response target, not a promise that every issue can be fixed within that time.
You can report a problem without giving up any legal rights. Contacting me first is welcome, but is not a condition for exercising your rights or making a complaint. This statement does not exclude any obligation or liability that applicable law does not allow me to exclude.