Accessibility statement

1.What we aim for

Kiket aims to meet the Web Content Accessibility Guidelines, WCAG 2.1, at level AA: on the public pages, in the catalogue and booking, and in the account and organizer tools; in every language Kiket offers; on a phone as well as a desktop; with a keyboard as well as a mouse.

This statement says what is checked and what we know is still missing. It describes our practice; it is not a certification.

2.What every change is checked for

Before a change is accepted, automated browser tests run through the public pages and the product flows in both languages, at a desktop width and at the width of a small phone. They apply the axe-core rules for WCAG 2.0 and 2.1 levels A and AA and fail on any violation. The tests also prove that:

• Every page works with a keyboard alone. Menus, dialogs, forms, the booking steps and the language switch are reached in reading order, the focused element shows a square red ring, and a closed dialog returns focus to where it opened.
• Links, buttons and controls are at least 44 pixels high, the pins on the catalogue map included.
• Text has a contrast of at least 4.5:1 against its background and the large red numerals at least 3:1. Meaning is never carried by colour alone: a status is always a word.
• Pages fit a small phone screen without horizontal scrolling, and transitions stop when the system asks for reduced motion.
• Each page declares its language, so a screen reader pronounces it correctly.

3.Known limitations

• Kiket has not yet been tested with people who use a screen reader. Automated rules and our own review catch many barriers, not all of them.
• The automated rules cover WCAG 2.0 and 2.1. The criteria added in WCAG 2.2 are not yet part of the checks.
• The catalogue map is moved with a pointer. Everything on the map is also in the list beside it, under the same filters.
• Course descriptions and organizer logos are written and chosen by each organizer. A logo is decorative; the organizer's name always stands beside it in text.

4.Report a barrier

If something on Kiket is hard or impossible for you to use, write to [email protected]. Tell us the page address, what you were trying to do, and the browser or assistive technology you use.

We answer from the same mailbox and say what we will change.