Bienarothe system for salons and wellness

Accessibility statement

A business’s booking website, the “My appointments” portal and the administration should work for people who cannot see, do not use a mouse or enlarge the text. Here you’ll find what we have achieved, what not yet and where to write when something is out of reach.

Version 1.0, effective from 5 October 2026. The manual review took place on 18 September 2026 and the decision on control borders dates from 19 September 2026; areas added later we check only automatically for now. We will publish any changes on this page.

What the goal is

We aim for the WCAG 2.1 level AA standard — the benchmark referred to by the European standard EN 301 549 and by the European Accessibility Act (EU Directive 2019/882, in Czechia Act No. 424/2023 Coll., effective from 28 June 2025).

The Act exempts microenterprises from the obligations of service providers. Toucan Labs s.r.o., which develops Bienaro, is a microenterprise, so the AA target is our own commitment. That does not automatically apply to the businesses that use Bienaro: whether the obligation applies to a business depends on its size and is assessed for each one separately. Our description below is supporting material, not a substitute for such an assessment.

What is done

  • The whole booking works from the keyboard — from choosing a service through the calendar and time to submitting. The calendar can be navigated with the arrow keys and every day in it carries a name (“Saturday 19 September – free slots”, “Sunday 20 September – closed”), so a screen reader announces the date and status, not just a number.
  • You can see where you are. Focus has a visible ring everywhere it can stop; after a booking is submitted it moves to the confirmation, not to the top of the page.
  • Tap targets are finger-sized. Buttons and links aim for 44 × 44 px. Where that is not possible – the switch pills in the administration header and the rows with a checkbox in settings – it is a deliberate decision and it is documented.
  • Colours have enough contrast. All 5 palettes a business can choose have normal text at 4.5:1 or more — including on tinted price list rows and in the inverted bands of premium templates.
  • The edges of fields and buttons are visible. The borders of controls in the booking — fields, calendar days, times, service tiles — have 3:1 or more against the background, as WCAG 1.4.11 requires, and this holds for all 5 palettes. Until 19 September 2026 they were fainter than the standard allows; now it is calculated, not estimated.
  • Texts have a language. Every page carries the correct lang, so a screen reader does not read Czech with an English pronunciation.
  • No cookie consent bar for a business that does not measure. We have nothing to hide behind a wall the keyboard would have to skip over.
  • If you turn off animations in your system (prefers-reduced-motion), you get the page without them.
  • Booking works without JavaScript where possible — confirming a cancellation is a plain disclosure element, not a dialog that does nothing without a script.

What is not there yet

We know about these and we don’t hide them:

  • Disabled days in the calendar are quiet. A day that cannot be booked has no strong border — on purpose: the standard does not target inactive elements, and a harder outline would suggest it can be tapped. Why a day is unavailable is said by the legend in words, not by colour.
  • A manual pass with a real screen reader is missing. We have not yet gone through the booking with NVDA or VoiceOver. Instead we read the tree of roles and names that the browser passes to the screen reader. It is a close substitute, not the same thing – a manual pass is planned.
  • The business writes the texts. The heading structure, photo captions and clarity of its own sentences are up to the business. The editor helps (it always asks for a caption for a photo), but we do not check the content for it.
  • Third-party elements. Bot protection (Cloudflare Turnstile) is a third-party component and is part of submitting a booking; we do not control its accessibility. If the verification doesn’t go through for you, write to us at info@toucan-labs.cz or book directly with the business. Payment is made on site; if a business offers payment in advance, the payment form is also a third-party component.
  • We do not promise level AAA. We aim for AA.

How we verify it

Automatically in automated tests: on the pages people actually open — the Bienaro home page, a business website, booking, the entry to “My appointments” on a business website, sign-in, sign-up and the administration — axe-core runs against the WCAG 2.1 AA rules, at laptop and phone widths. The client account at bienaro.com/moje and a business’s verification profile are not in this set yet. On top of that we measure the size of tap targets, focus visibility and whether the page language matches the text language, and we calculate the contrast of all palettes separately. A finding of “critical” or “serious” severity fails the test.

In a browser walkthrough on 18 September 2026 we went through the booking with the keyboard – partly with real keys, partly by simulating key presses in the page – and re-measured the contrast of the palettes. Still missing is a complete manual pass by a person with a real keyboard and the NVDA or VoiceOver screen reader (see above).

Automated checks catch only some problems; they are no guarantee that the website meets every WCAG criterion. That is why we also write here what is missing.

When something is out of reach

Write to us at info@toucan-labs.cz — just say what didn’t work and on what (phone, screen reader, browser). We usually reply by the second working day. A fix that can be done quickly we do right away.

If it is about a specific booking or appointment, the business is quicker: its contact is in the legal information on its website. Right in the booking there is also a link “Booking not working? Write to us”: that message goes only to us, the operator of Bienaro, not to the business – so the business will help with the appointment itself.

Because we are not an obligated entity under Act No. 424/2023 Coll., there is no official appeal or supervisory authority we could refer you to. We handle complaints ourselves and directly.

privacy policy · AI transparency · contact · back to the home page