Accessibility statement · written October 16, 2026
Accessibility statement
Ekimeet should work for everyone who comes to an event: on a phone or a computer, with a keyboard, a screen reader, zoom or voice control. This page says how far we have got, what still falls short, and how to tell us.
How accessible Ekimeet is
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. Norwegian rules on universal design ask for at least WCAG 2.0 AA; 2.1 goes further and is what the European Accessibility Act builds on. Ekimeet partly meets WCAG 2.1 AA: every screen passes our automated checks, and the problems we know about are listed below.
How we checked
On October 16, 2026 we went through the whole web app, signed out and signed in, as an attendee, an organizer, a door volunteer and a moderator:
- Automated checks with axe-core against WCAG 2.0 and 2.1, levels A and AA, on 89 screens, each at phone width and computer width, in light and dark mode.
- A keyboard-only pass through the core tasks: signing in with an email code, joining an event by code, today's people, sending a message, scanning or typing a code, checking a guest in at the door, writing a post and choosing who sees it, and notification settings.
- Every screen on a 320 px wide screen (the same as 400 % zoom on a computer), without sideways scrolling or lost content.
- Not yet done: a test together with people who use a screen reader every day. It is planned before the next review.
What you can expect
- Every attendee step works in a phone browser, with no app to install.
- Everything can be done with a keyboard, with a visible focus ring in light and dark mode. “Skip to content” jumps past the menus.
- Today's people never needs a swipe: Pass, Later and Connect are buttons.
- Nothing needs the camera: an event code can be typed in, and the door team can find guests by name.
- Text and controls meet contrast level AA in both light and dark mode, and pages can be zoomed.
- If your device asks for less motion, animations are switched off.
- Japanese words in the app are marked as Japanese, so screen readers pronounce them correctly.
Known problems
These are the problems we know about. We are working on them.
- We have not yet tested with VoiceOver (iPhone) and TalkBack (Android) on real phones. Something may read in an odd order or be missing until we do.
- Photos in posts have a description only when the person who posted them wrote one. We ask for it, but it is not required.
- Text people write themselves (names, posts, messages) is not marked with its language, so a screen reader may read a Japanese name with English pronunciation.
- A sign-in code works for a limited time. If it runs out, ask for a new one with one tap; nothing you typed is lost.
- The venue screen (a departures board for a TV at the event) is made to be looked at, not used: it changes on its own and has no controls. The same programme is in the app.
- Printed name badges and printed cards are made for paper. Their QR codes also work as links in the app.
- Emails from Ekimeet (sign-in codes, digests) were not part of this check.
Tell us about a problem
If something on Ekimeet is hard or impossible for you to use, tell us what you were trying to do, on which page, and with which device or assistive technology. Write to:
hello@ekimeet.com
Report an accessibility problemYou can also ask us for something in another form, for example the text of a page you cannot read.
When you will hear from us
We answer within 10 working days. If a fix takes longer, we tell you when to expect it and help you another way in the meantime.
If you are not happy with our answer
In Norway, the Authority for Universal Design of ICT (Uutilsynet) makes sure that websites and apps follow the rules on universal design. You can tell them about a problem you found on Ekimeet:
About this statement
This statement was written on October 16, 2026. We review it at least once a year, next by October 16, 2027, and whenever we change Ekimeet in a way that affects accessibility.