1. Scope of this statement
StartOrbit sp. z o.o., the owner of the RobimyWeb brand, is committed to making its website accessible in line with the WCAG 2.2 guidelines at level AA. This statement covers the robimyweb.pl website, including its language versions and the “Tips” blog.
As a micro-entrepreneur, I am not legally required to publish this statement. I publish it voluntarily, because accessible websites are part of my work, and I apply the same principles in projects for my clients.
2. Compliance status
The website is partially compliant with WCAG 2.2 at level AA. The automated audit found no errors on any subpage, but some of the content described in section 4 does not yet meet all requirements.
3. What makes the website easier to use
- Full keyboard support, with a visible focus indicator on the active element
- A “Skip to content” link at the top of every page
- Text contrast of at least 4.5:1, and at least 3:1 for large text
- Alternative text for photos and screenshots
- Pop-up windows (projects, AI chat) labelled for screen readers, with Escape key support
- The mobile menu closes with the Escape key and keeps focus from slipping to the page underneath
- Animations turn off when you enable reduced motion in your system settings
- Zoom up to 200% and 320 px screens without loss of content
- Form fields with labels and error messages
- The language of every page marked in the code (PL, EN, DE, FR, RU)
- No “accessibility” overlays, which often get in the way of screen readers
- Fonts and scripts served from my own server, so the website loads quickly even on a slow connection
4. Known limitations
- Video about the Haloskop app (Projects)The narrated video doesn’t have captions or a transcript yet. I plan to add them. Until then, a description of the app is available as text in the same window.
- Booking a call via Cal.comThe calendar runs on the external Cal.com service, and I have no control over its accessibility. Instead, you can call me, send an email or use the contact form.
- AI assistant responsesThe assistant on the website uses a language model and can make mistakes. For important matters, write to me or call me directly.
- Language versionsThe English, German, French and Russian translations were created with the help of AI and may contain inaccuracies. In case of doubt, the Polish version prevails.
- Client websites in ProjectsThe “Open website” links lead to my clients’ websites, which have their own accessibility statements or are not subject to these requirements.
5. How I test accessibility
I prepared this statement based on a self-assessment. I automatically check every subpage in its mobile version with Lighthouse (axe-core engine), and I manually test keyboard navigation, contrast, zoom and layout on screens from 320 to 1440 px. I repeat the audit after every major change to the website and review this statement at least once a year.
6. Report an accessibility problem
If something on the website is difficult or inaccessible for you, email me at or call: . Describe which subpage the problem concerns and tell me how to contact you. You can also ask me to send the content in another format, e.g. as plain text in an email.
I reply within 7 days at the latest. If I can’t fulfil your request in that time, I’ll tell you when I will, and what alternative I can offer right away.
7. Dates
Website published: 7 October 2026. Statement prepared and last audit carried out: 8 October 2026.
