Evaluated on 14 September 2026
Accessibility statement
We build Emisar APP to EN 301 549 v3.2.1, which for web content points to WCAG 2.1, level AA.
Status: partially conformant
Emisar APP is partially conformant with EN 301 549 v3.2.1 / WCAG 2.1 AA: most requirements are met, and the two known non-conformities are below. The evaluation so far has been automated; testing with assistive technologies is still to come.
Known non-conformities
Two, which we are fixing:
Decorative text below the contrast threshold, on the home page
The cards that present our features contain product mock-ups — panels showing what an agenda or a registration list looks like. The “later” rows are faded to suggest depth, and that fading drops their contrast below the required threshold: six elements on the light theme, three on the dark one. The text inside is invented and carries no information — the function is explained by the card’s title and description.
A keyboard shortcut that cannot be turned off
In the organiser console, the “/” key moves focus to the search field. It cannot be disabled, cannot be remapped, and is active across the whole page rather than only when search has focus. In practice: a speech-input device that utters “slash” moves focus unintentionally, and the person has no way to switch it off.
What we have not checked yet
Automated evaluation does not cover everything. The following are still to come:
- walking the main flows using the keyboard only: registration, check-in, meetings;
- testing with a real screen reader (NVDA, VoiceOver);
- contrast of field borders, focus states, and icons that carry meaning;
- tooltips and menus that appear on hover or focus;
- the door staff screens (scanning, kiosk, stand), which have their own contrast checks but were not part of this evaluation;
- language, error messages, and the cognitive load of forms;
- areas with gradients or decorative elements on top, where contrast is checked by eye.
How we evaluated
Automated evaluation on the public site, last run on 14 September 2026: 76 scans (38 pages × two themes) with the complete WCAG 2.1 A and AA rule set, colour contrast read from rendered pixels, and a check that content reflows at 320 px width. The palette colours pass the strictest threshold (7:1) on both themes, and the only exceptions are the two non-conformities above, where the contrast drops from fading rather than from the colour itself. Reflow at 320 px: eight pages, no horizontal scrolling.
What the tool could not decide
An automated tool does not only answer “yes” or “no”: for some elements it reports that it cannot decide — text over a gradient, over an image, or under a semi-transparent layer, where the colour behind cannot be determined from the code. In the 14 September 2026 scan there were 1,277 such nodes (622 on the light theme, 655 on the dark one), across two rules: colour contrast, and an ARIA attribute used where it is not allowed. Most of them are on a demo event page (116 per theme) and on the pricing page (65 per theme).
We write this down because “could not decide” does not mean “conforms”. These are exactly the places left to check by eye, in the manual testing listed above — not a list of defects, but not a list of things that are fine either.
If you hit a barrier
Write to us at salut@emisar.ro. We reply within 1–48 working hours (Mon–Fri, 10:00–16:00, Romanian time). That reply may be a request for clarification; we tell you the resolution time in it, and it ranges from an hour to seven days depending on what needs doing. Tell us which page, what you were trying to do and, if you can, which assistive technology — with those details we fix it far faster.
If our answer does not satisfy you
If you receive no reply within the deadline above, or the solution is not satisfactory, you can write to us again at salut@emisar.ro asking for a review. Our legal classification under the European accessibility rules is still being established; until that is clarified, we hold ourselves to the standard above whether or not we are required to.