Accessibility statement
Affinira is built to target WCAG 2.2 level AA. A product built around meeting people has no business excluding any of them. This statement describes what that target means in practice today: which screens and conditions are covered, what has not been verified yet, and how to tell us when something is in your way.
What is checked today
Accessibility here is a design constraint. What these checks reach is below, and what they do not reach is named in the next section rather than left to be assumed.
An automated accessibility check
An automated accessibility check for WCAG A and AA violations covers a named list of screens. The whole of that list is checked in a mobile configuration, and a representative subset of it again under responsive stress — at the narrowest width still worth supporting, at 200% browser zoom on desktop, and in landscape — where reflow, target size and focus order are what actually change. Alongside it, desktop, tablet, mobile, dark theme and reduced motion are covered.
Keyboard operation
On the public profile, every interactive control is reachable by keyboard alone and focus is visibly indicated. Elsewhere, keyboard behaviour is checked where it is specified: sheets close on Escape, and focus lands somewhere deliberate after an action removes the control that had it. An exhaustive keyboard walk of every screen has not been done.
Reduced motion respected
When your system asks for reduced motion, animation steps aside. The Affinity Ring — the motif that shows the state of a relationship — carries its meaning statically, so nothing in the product is understandable only through movement.
Contrast checked in the design tokens
Text and surface colours come from a shared set of design tokens, and every text-on-surface pairing in that set is checked against the WCAG AA contrast ratio in both themes. Colours written directly into a page — an occasional graphic or link preview — are outside that check.
Two further practices are worth naming. The served demo profile is a static page that works without JavaScript, which supports access when scripting is unavailable. And the product demonstrations on this site remain understandable with animation switched off; movement is always an enhancement, never the message.
Known limitations
An honest statement includes what has not been done. These are the current gaps we know about.
Automated checks cover selected WCAG 2.0 and 2.1 rules
Our automated checks cover the WCAG 2.0 and 2.1 A and AA rule sets. They do not establish conformance. Coverage of the additional WCAG 2.2 criteria has not been established.
The checks cover a named list of screens, not every screen
The automated checks run against a named list of screens. Screens outside that list — newer transactional and administrative states among them — have not been through them. The list is where coverage is decided, and this page will not claim more coverage than the list holds.
No manual screen-reader audit yet
Automated checks catch structural problems — missing labels, contrast failures — but they do not experience a page the way a screen-reader user does. A manual audit with assistive technology has not been performed yet, and we say so rather than imply otherwise.
WebKit — the iOS Safari engine — is not covered by automation
Our automated checks cover mobile viewports, but the browser engine underneath them is not the one real iOS Safari uses. Behaviour specific to WebKit — sheet opening and closing, dynamic viewport height, safe-area insets — is therefore unverified: it is not covered by automation, and no manual pass on a real iPhone has been done either. This is the largest single gap in what we can tell you, and we would rather name it than describe it as informally handled.
This is a statement, not a certificate
WCAG 2.2 AA is our design target. We do not claim conformance, and no external certification exists. As the product matures, this page will track what has actually been verified.
Tell us what is in your way
If any part of this site or the Affinira product is difficult or impossible for you to use, we want to know — a specific report from a real person is worth more than any automated sweep. Write to hello@affinira.com and describe what you were trying to do, what happened, and the assistive technology or browser you were using if you can. Accessibility problems are treated as defects, not as suggestions.