Last updated: 2026-07-29
This is not a conformance declaration. We are not claiming WCAG 2.2 AA compliance, and we are not filing an accessibility statement under the European Accessibility Act — as a one-person Dutch business we fall under the microenterprise exemption for services.
We are building for accessibility anyway, because Omoikane is a job-search tool for career-switchers, people re-entering the market, and neurodivergent job seekers. Those are the people most likely to be failed by a badly built interface, and they are who this product is for.
So this page says what we actually do, what we have measured, and what is still missing. Where something is not done, it says so.
What we have built
Colour contrast is measured, not eyeballed. Every foreground/background pair our stylesheets set together is checked against the 4.5:1 ratio WCAG requires for body text. The check runs in our build and fails it — so a colour change that breaks contrast cannot ship. We hold everything to 4.5:1, including large text that would be allowed 3:1, because our tooling cannot tell which colours are only ever used at large sizes and guessing in the permissive direction is how body text slips through.
Motion is opt-in. If your system is set to reduce motion, our animations and transitions do not run — and the timers that drive the ambient movement on our landing page do not start at all. Not just slowed: not started.
You can skip the navigation. The first thing a keyboard or screen-reader user reaches on any page is a link straight to the content.
Keyboard focus is always visible. Every interactive element shows where you are. We never remove the focus outline without replacing it with something at least as clear.
Structure is real. Headings are properly nested, form fields have labels, and images that carry meaning have alternative text. Decorative images are marked as decorative so your screen reader skips them. Tables in the app have captions and column headers; the tables on this site have column headers but no captions yet.
The interface does not rush you. No countdowns, no auto-advancing steps, no session timeouts that lose your work. Progress is shown categorically rather than as a percentage, and we do not celebrate transitions with animation. This is a deliberate design position, not an accessibility setting you have to find and switch on.
Sensitive fields are off by default. Anything about your health, background or personal circumstances is collapsed and optional, never pre-filled and never required.
What is not done
We have not completed a manual screen-reader pass. Automated checks catch a minority of real accessibility problems. Until a person has worked through our launch surfaces with NVDA, VoiceOver and Orca, we cannot tell you those surfaces are usable — only that they pass the checks we can automate. That work is scheduled and not finished.
PDF exports are not yet verified as accessible. Our Europass exports produce tagged PDFs with accessibility structure, aiming at PDF/UA — but we have not validated them independently. Our regular CV and letter exports are not yet tagged at all. Treat an exported PDF as less accessible than the same content on screen. If you need a document in a different format, ask us.
Dutch and Greek translation is incomplete. The interface chrome is translated. Longer body copy on some pages is still English only. If a page is not available in your language, that is a gap we are working through, not a decision.
We have not tested with every assistive technology. Our checks cover the mainstream screen readers and keyboard navigation. Braille displays, switch access, eye tracking and voice control are untested.
If something does not work for you
Email hello@omoikane.coach and describe what happened. Tell us the page, what you were trying to do, and what assistive technology you use if you are comfortable sharing it.
We will reply within five working days. If it is a barrier that stops you using the product, we will tell you either when it will be fixed or that we cannot fix it — not that we are looking into it.
You do not need to explain or justify your access needs to us to get a reply.
Why the exemption is in this page
We could have left the microenterprise exemption unmentioned and let this read as a compliance document. That would imply a conformance claim we have not earned, and a claim like that is worse than silence: a screen-reader user who trusts it and hits a barrier has been misled by us.
If Omoikane grows past the microenterprise threshold, or an investor takes a stake of 25% or more, the exemption stops applying and this page becomes a legal obligation with a different standard of proof. We would rather already be doing the work by then.