In brief
- We work to WCAG 2.2 level AA on the site, the Host dashboard, the Scheduling Pages and the host apps.
- We assess our own product and describe the known limitations instead of claiming full compliance.
- Accessibility reports go to support@kallenda.app with the subject “Accessibility” and we answer within 14 days.
- If our answer does not resolve the problem, you may complain to the market surveillance authority.
Scope of this statement
This statement covers the public site at kallenda.app, the Host dashboard, the Scheduling Pages that Hosts publish, and the host apps for iOS and Android. It is published by Undernapse Sp. z o.o., ul. Hoża 86 lok. 410, 00-682 Warsaw, Poland, the operator of Kallenda. It describes the service we operate, not a Host’s own content, a Host’s connected tools or a third-party checkout page.
Kallenda is an e-commerce service within the meaning of the European Accessibility Act. In Poland the Act was implemented by the act of 26 April 2024 on ensuring that certain products and services meet accessibility requirements (Dz.U. 2024 poz. 731), in force since 28 June 2025, and it covers e-commerce services. The act provides a microenterprise exemption in Article 4(1); this statement does not rely on that exemption, it describes the standard we apply.
Standard
The legal benchmark is EN 301 549, which for websites and mobile applications points to WCAG 2.1 level AA. We build to WCAG 2.2 level AA as our own, higher target: where the 2.2 criteria go beyond 2.1, the 2.2 success criteria are the acceptance level for every screen we design and build.
- Perceivable: text alternatives for meaningful images and icons, captions and transcripts for media we publish, and contrast at or above the AA thresholds.
- Operable: every function available from a keyboard, a visible focus indicator, no keyboard trap, and enough time to complete a task without a session ending mid-booking.
- Understandable: consistent navigation and labels, error messages that say what went wrong and how to fix it, and persistent form labels rather than placeholders alone.
- Robust: semantic HTML, correct heading order, status messages announced to assistive technology, and compatibility with current screen readers and browser zoom at 200 per cent.
We respect the operating system’s reduced-motion setting, keep touch targets usable on the mobile web and in the host apps, and test the booking flow with a keyboard only and with a screen reader before a release that changes it.
Compliance status
We assess our own product. There is no external certification and no audit mark, and we do not claim full conformance, because we have not commissioned a third-party audit and we will not claim more than we can show.
On our own assessment, the site, the dashboard and the Scheduling Pages meet WCAG 2.2 AA for the core journeys: creating an account, connecting a calendar, publishing an Event Type, taking a Booking and managing an existing Booking. We treat the service as partially compliant because the limitations in section 4 are real and not yet closed.
Known limitations
These limitations are known to us as at 10 November 2026. We list them because a statement that hides them does not help the person who meets one.
- Third-party checkout and sign-in. Subscription payment runs through a Stripe-hosted checkout, and Google and Microsoft provide their own sign-in and consent screens. Their accessibility is governed by their statements, not this one. Report a barrier there to us and we will raise it with the provider and, where possible, offer another route.
- Documents from payment and invoicing providers. Invoices, corrections and fiscal receipts are PDFs generated by our providers and are not tagged for assistive technology in every case. Write to support@kallenda.app and we will give you the same information in the body of an email.
- Embedded Scheduling Pages. When a Host embeds a Scheduling Page in their own website, the surrounding page is the Host’s and its accessibility is the Host’s responsibility. The embedded scheduling interface follows this statement.
- Older emails and recordings. A client that strips styles can render a transactional email poorly; we keep those emails single-column for that reason. Where a recording has no captions, the same instruction is available as text in our help pages.
Accessibility features
- Keyboard operation throughout the dashboard and the booking flow, a visible focus ring and a skip link to the main content.
- Semantic landmarks and a logical heading order, so a screen reader can navigate by region and by heading.
- Form controls with real labels, format hints and error messages tied to the field they concern.
- Text that reflows without horizontal scrolling at 320 CSS pixels and remains usable at 200 per cent zoom.
- Contrast at or above the AA threshold, and no information carried by colour alone.
- Status messages — a Booking confirmed, a payment declined, a save completed — announced politely to assistive technology.
- The page language declared correctly, so Polish and English content is pronounced with the right voice.
The booking flow works without an account, which removes a login barrier for Invitees, and the confirmation email repeats every detail shown on screen.
Reporting a problem and review route
Write to support@kallenda.app with the subject “Accessibility” (in Polish: „Dostępność”). Tell us the page or screen, what you were trying to do and what happened; if you can, add the browser, device and assistive technology. A plain description of the barrier is enough.
We confirm receipt and answer within 14 days with what we found, what we will change and when, or why we consider the behaviour correct. If you are not satisfied, ask for a review: a person who was not the first reviewer looks at the case again and answers within 14 days. This internal route is free and does not require an account.
If the internal route does not resolve the matter, you may complain to the market surveillance authority. For e-commerce services under the Polish accessibility act that authority is the minister responsible for digital affairs (minister właściwy do spraw informatyzacji), whose tasks include complaints about e-commerce services that do not meet the accessibility requirements. You may also use the general consumer-protection routes, including a complaint to the President of UOKiK about practices that harm collective consumer interests.
Review date and version
This statement was prepared on 10 November 2026 and applies from that date. We review it at least once every 12 months, and earlier when a material change to the interface, the standard or the law makes an earlier review necessary. The next scheduled review is November 2027.
| Item | Value |
|---|---|
| Version | 1.0 |
| Date of the statement | 10 November 2026 |
| Method | Self-assessment against WCAG 2.2 AA and EN 301 549 |
| Next review | November 2027 |
Service operator
Undernapse Sp. z o.o.
UNDERNAPSE SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ
ul. Hoża 86 lok. 410, 00-682 Warsaw, Poland
- KRS
- 0001037160
- Register court
- Regional Court for the Capital City of Warsaw in Warsaw, 12th Commercial Division of the National Court Register
- NIP
- 7011145585
- REGON
- 525353982
- Share capital
- PLN 5,400.00
Contact