Which pages this covers
- Event pages and the ticket checkout
- The ticket page a buyer receives by email
- A club's terms and imprint pages
- The membership application form, also when it is embedded on a club's own website
- The member portal: sign-in, tickets, invoices, directory and sharing
- Club websites on a getflok.app address or on a club's own domain
It does not cover the administration area clubs use to run Flok, nor Flok's own marketing website.
Standard and status
We build and test these pages against the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, which includes the WCAG 2.1 AA requirements referenced by the European standard EN 301 549.
These pages meet WCAG 2.2 AA. A few known issues we are still fixing are listed below.
What is not yet accessible, and the alternative
- Content a club writes itself. Event descriptions, images and documents a club publishes are the club's own. Flok gives clubs the tools — a description field for every event image, labelled questions in the checkout, real lists and links in the text editor — but cannot check that each club uses them. If something a club published is not accessible to you, tell the club, or tell us and we will pass it on.
- The PDF ticket is not a tagged PDF, so a screen reader may read it poorly. The ticket page linked in the confirmation email carries the same information, including the QR code, as an accessible web page.
- Payment happens on the hosted pages of Stripe or Payrexx, which Flok does not build. Their accessibility is their responsibility; the button that takes you there says which provider it opens.
- Wallet passes and calendar files (Google Wallet, .ics) are generated in the formats those platforms define.
How we checked
Self-assessment, last carried out on 19 October 2026. No external audit has been carried out yet.
- Every page and state listed above was checked automatically with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rules — in German, English, French and Dutch, in light and dark mode, including a checkout showing its error messages. No violations were found.
- A ticket purchase was completed with the keyboard only, from the first page to the confirmation.
- The checkout was also used with the VoiceOver screen reader on macOS and iOS, from the event page to the booking confirmation.
- These checks run again before every release, together with a contrast check of every colour pair Flok uses and tests of the checkout's labels, error messages and page language.
Feedback and contact
If something on these pages is hard or impossible for you to use, write to hello@getflok.app. Tell us the page and what went wrong. We reply within 14 days and, where we cannot fix it quickly, send you the information in a form you can use.
Enforcement
If you are not satisfied with our answer, you can contact the Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF AöR), Carl-Miller-Straße 6, 39112 Magdeburg, Germany — mlbf-barrierefrei.de, which also takes reports of barriers directly.