Omkin works toward WCAG 2.2 AA across public content, onboarding, matching, checkout, dashboards, and session entry—with clear alternatives when a barrier remains.
Designed for different ways of seeing, hearing, moving, understanding, and connecting.
KeyboardZoomCaptionsPlain language
WCAG 2.2AA target
No diagnosisneeded for an alternative
Every flowpublic pages through session entry
What this means in practice
Access is considered across the whole journey.
Our target covers more than public pages. It includes the moments where people make choices, correct mistakes, pay, communicate, and enter care.
01⌨
A standard across the whole journey
The WCAG 2.2 AA target covers public information, authentication, onboarding, matching, professional profiles, booking, checkout, dashboards, messages, and session entry. It applies beyond the marketing pages.
Keyboard operation and visible focus
Semantic structure and useful accessible names
Text resizing, reflow, and responsive touch targets
Sufficient color contrast and reduced-motion support
02Aa
Language, cognition, and error recovery
Clear headings, consistent controls, plain-language boundaries, progress indicators, review screens, and recoverable validation help people understand what is being asked and correct a mistake without losing their work.
Instructions do not rely on color or position alone.
Important consent and service terms can be reviewed before action.
Timeouts and destructive actions require appropriate warning.
Translated previews never hide the controlling service boundary.
03◉
Media, meetings, and alternatives
Meeting controls are labeled and keyboard reachable, connection status is communicated in more than one way, and text alternatives or captions are provided where the supported service can offer them.
04✓
Known limitations stay visible
An unresolved barrier is documented with its affected flow, impact, available workaround, accountable owner, and expected resolution window. High-impact barriers can block a public release.
Automated checks in the delivery workflow
Keyboard and screen-reader review of critical paths
Responsive testing at text zoom and narrow widths
Manual review for meaning, order, and error handling
05↗
Tell us what blocks you
Accessibility feedback has a dedicated route and response target. Describe the page, task, device or assistive technology if you are comfortable, and the format or alternative that would help.
Help us remove a barrier
Tell us what stopped you, not why you need access.
Share the page or task, your device or assistive technology if useful, and the alternative that would help. Keep diagnosis, therapy notes, and identity documents out of a general message.