Accessibility statement

EN 301 549, the harmonised European standard, currently refers to WCAG 2.1 level AA. We test against the newer WCAG 2.2 level AA, because that is the higher bar: 2.2 contains every criterion in 2.1 and adds six more (2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7 and 3.3.8). Criterion 4.1.1 (Parsing) was removed in 2.2.

In practice: what this page says about 2.2 also covers the 2.1 requirement your organisation has to meet. If you test against 2.1, you can simply leave the six extra criteria out.

This is a supplier statement. Slotr is a product of Boost Productions, not a public body. The official accessibility statement in a national register is published by the public organisation itself, about its own website or app. If your organisation uses Slotr, you can use this document as supporting evidence for your own statement and in a procurement check.

This document is not an independent audit. No external assessment by a certified party has taken place yet. See below for what we did and did not examine.

Slotr partially complies with WCAG 2.2 level AA. In the areas examined, no remaining issues were found against the A and AA criteria, including the six criteria that WCAG 2.2 adds. Because 2.2 contains all of 2.1, the 2.1 requirement in EN 301 549 is covered as well.

We deliberately do not claim full compliance. That would require an independent assessment and a test with real assistive technology. What was not examined is listed below.

Examined on 16 July 2026, on the live production environment. Everything you use as a customer:

• For attendees: the public event page with the sign-up form, time slots and custom questions
• Access: signing in, creating an account, creating an organiser account, forgotten password and password reset
• For organisers: creating and editing an event, the attendee overview with the add and edit dialogs, the date poll, sending a notification, and personal settings
• For organisation admins: creating an organisation, organisation settings (branding, logo, own domain), teams, and managing members and roles

The only thing outside this scope is Slotr's own internal admin console, which is for our staff only and not reachable by customers.

Measured in the screens examined. Criteria marked (2.2) are new in WCAG 2.2.

• 1.3.1 / 3.3.2 / 4.1.2 Every input has a programmatically associated label. Placeholder text is not relied on.
• 1.4.3 No contrast failures found (measured on computed colours, not estimated).
• 1.4.10 Reflow: at a width of 320 pixels no horizontal scrollbar appears.
• 2.1.1 All functionality can be operated with the keyboard: choosing time slots, showing or hiding a password, and uploading an image or logo. Full time slots stay focusable and are announced as unavailable.
• 2.4.7 A visible focus indicator is present.
• 2.4.11 (2.2) Focus not obscured: no element disappears entirely behind a sticky bar when it receives focus.
• 2.5.7 (2.2) Dragging movements: anything draggable (uploading an image or logo) can also be done with a single click or the keyboard.
• 2.5.8 (2.2) Target size: controls are at least 24 by 24 pixels.
• 3.1.1 The language of the page is set correctly.
• 3.2.6 (2.2) Consistent help: not applicable, there is no help mechanism that moves between pages.
• 3.3.1 Error messages are announced through a live region.
• 3.3.7 (2.2) Redundant entry: not applicable, signing up happens in one step without repetition.
• 3.3.8 (2.2) Accessible authentication: signing in works with a password manager (autocomplete is set correctly) and there is no CAPTCHA or puzzle.
• 4.1.2 / 2.1.2 / 2.4.3 Dialogs have a dialog role with an accessible name, close with Escape, trap focus, and return focus to the element that opened them.

At this moment there are no open issues known against the A and AA criteria within the scope examined. That does not mean there is nothing left to find: see below for what we could not examine.

• No test with real assistive technology was carried out (such as NVDA, JAWS or VoiceOver). The assessment looked at the accessibility tree and computed styles, not at how a screen reader speaks it.
• No independent audit by a certified party has been carried out.
• The mobile apps (iOS and Android) were not examined.

• Carry out a test with a real screen reader and process the findings here.
• Have an independent assessment carried out. We are happy to follow the assessment method your organisation uses.
• Test new screens on delivery, so this statement stays current.

Run into an accessibility problem, or unable to do something because of a barrier? Report it at hallo@slotr.nl. We respond within five working days and look for a solution together, also when the problem cannot be fixed straight away.

Slotr is provided by Boost Productions, Stationstraat 293, Nuth, the Netherlands.