Accessibility statement

What this covers

This statement is about the Tikit website that buyers use: browsing events, event pages, checkout, your order and your tickets, finding your tickets, the help pages and the emails we send. It does not yet say anything about the phone app.

Our target

We aim for WCAG 2.2 level AA on the buyer pages. This is a self-assessment: no outside body has audited Tikit, and we do not claim full conformance.

How we check

Our key buyer pages are checked by automated tests (axe-core, against the WCAG 2.0, 2.1 and 2.2 level A and AA rules). We start them by hand before a release, in every language we offer; they do not yet run on their own whenever the code changes. A separate test measures the contrast of our theme colours. Automated tools find only part of the problems real people meet, so passing them does not prove that a page works for you.

What is in place

• A “Skip to content” link is the first thing you reach with the Tab key on the pages buyers use, including an organiser’s own event site. The small ticket widget that organisers can put on another website does not have one.
• Form fields and outlined buttons show a clear outline when you reach them with a keyboard. The focus outline on filled buttons is fainter than WCAG asks for (see below).
• If your device is set to reduce motion, Tikit stops its animations and transitions.
• Each page declares its language, and you can switch between English, Afrikaans, isiZulu and isiXhosa where those are offered.
• Form fields have labels.
• Organisers can list step-free access, hearing loops, accessible toilets and other access details on their event page. Where an organiser allows it, you can ask for support and a free companion ticket.

What we know falls short

These are the gaps we know about today.

• In light mode, the green status text on its pale green background (the “Paid” and “Valid” badges) and the red status text on its pale red background (“Failed” and “Cancelled”) have less contrast than level AA asks for. So does the red text on the pale red buttons that cancel or delete something, such as “Cancel my plan” and “Delete my data”. The colours are part of our theme and will change with it.
• The focus outline on filled buttons (such as the main “Continue” and “Pay” buttons) is below the 3:1 contrast WCAG 2.2 asks for: only a faint glow shows when you reach one with a keyboard. It is part of our theme and will change with it.
• The venue seat map is built for touch and mouse first. A seat list is offered only where one already exists, so choosing exact seats with a keyboard alone can be hard. Contact support and we will help you choose seats.
• Event titles, descriptions, questions and ticket notes are written by organisers. Tikit does not translate them or check their accessibility.
• The scanner that event staff use at the door is in English only.
• PDF tickets are not tagged for screen readers. The ticket page shows the same details as text.
• Some payment, refund and privacy wording stays in English on a page in another language until a reviewer has signed off a translation. Only this statement, and the privacy note on the access-support form, mark that wording as English; on other pages a screen reader may read it with the wrong accent, which WCAG 3.1.2 (language of parts) asks us to avoid.
• The Afrikaans, isiZulu and isiXhosa pages are drafts that no native speaker has reviewed yet, so some wording may be wrong.

Tell us about a barrier

If something on Tikit is hard or impossible for you to use, tell us. Say which page it was, what you were trying to do and what you use (a screen reader, magnification, a keyboard or switch, voice control…). We will look into it and tell you what we can do.