01 What this statement covers
The statement covers this website in both language versions: content, navigation, the contact form, the booking link and the legal documents in the footer. It describes the site as of the last review date shown at the top of the page.
undernapse.com is an informational website for our company. We do not sell through it: there is no cart, no payment and no user accounts. We do not control the interfaces of external services we link to (for example the booking calendar); they have their own accessibility policies.
This statement is voluntary. We are not a public body, so we are not required by law to publish one. We publish it because accessibility is a standard for us, not an extra.
02 Conformance target
Our target is WCAG 2.2 level AA. We apply that level to new and changed parts of the site: text contrast, keyboard operation, visible focus, heading structure, motion and content available without JavaScript.
We hold no accessibility certificate and no result from an external audit. Below we describe what we checked ourselves, how, and where we see limitations.
03 What we checked
We check accessibility on the built site in a browser, not only in code. The last review took place on 10 November 2026 and covered the areas below.
- Contrast
- Muted text (#a1a1aa) has a contrast ratio of 4.70:1 on the graphite surface and 8.19:1 on black. The accent (#ff5757) is 6.75:1 on black; for small text on graphite we use a lighter tint (#ff8a8a) at 5.31:1. The ratios were computed from the colours the site actually uses, not from the design file.
- Keyboard
- The whole site works with a keyboard: from the “Skip to content” link, through the navigation and the services menu, to the content and the footer. The dropdown opens and closes, Escape closes the mobile menu and focus returns to the toggle that opened it.
- Visible focus
- Every interactive element has a visible focus indicator — an outline on links and a ring on buttons.
- Heading structure
- Every page in the Polish and English versions has one h1, and heading levels do not skip. We checked this on every page of the built site and by hand on the home page, the work page and the contact page.
- Reduced motion
- With the system “reduce motion” preference, entrance animations, backgrounds and the menu are turned off. Content is visible immediately, without waiting for an animation.
- Content without JavaScript
- The content is visible without JavaScript. The header then falls back to a plain list of all links, and submitting the form returns to the page instead of a raw JSON response.
- Script security
- Page scripts are inlined in the HTML and allowed by hashes in the Content-Security-Policy, without “unsafe-inline”. We do not load third-party script libraries in the interface.
04 Known limitations
Accessibility is a process, not a state. Here is what we have not done yet — without glossing over it.
- We have no external accessibility audit and no WCAG certificate. The checks above were carried out by us.
- We have not yet tested with people who use assistive technology every day: screen readers, voice control, magnification or switch access. That is the most reliable accessibility test and our next step.
- Without JavaScript the site is simpler: the mobile menu becomes a plain list of links, and after submitting the form we return to the contact page without a confirmation message. Content and the form still work, but the experience differs from the JavaScript version.
- The interfaces of external services (the booking calendar, LinkedIn, GitHub) are outside our control. We cannot guarantee their accessibility.
05 Reporting an accessibility problem
If something is inaccessible — you cannot reach it with a keyboard, read it with a screen reader, enlarge it or understand it — write to us. Tell us which page the problem is on and what happens; if you can, include the browser and assistive technology you use. You do not need to know WCAG — a plain description is enough.
- hello@undernapse.com
Accessibility contact is by email only. We do not publish a phone number — deliberately, so that we do not offer a channel we do not staff.
Accessibility reports are taken into account in the next reviews of the site. Thank you — they tell us what to fix first.
06 Statement review
We review this statement at least once a year and after any significant change to the site: a new template, a new feature, a change to the colour palette or a new third-party widget. Last reviewed: 10 November 2026. Next review due: 10 November 2027.
The Polish version is the binding version. The English version is a translation for people who do not read Polish.
This statement is not a certificate. It describes the state we checked and the limitations we know about. Changes are published in the same place with a new review date.