Accessibility

What has been tested, what has not, and how to tell us when something does not work for you.

What has been tested

Each of these is verified in the codebase or on every build, not claimed from memory.

Visible focus, everywhere
Every interactive control shows a focus ring when you reach it with a keyboard, and no stylesheet removes one.
Reduced motion is honoured globally
If your system asks for reduced motion, animation is switched off across the product rather than per-component — so a screen we add later cannot forget.
Tap targets of at least 44px
WCAG 2.2's target-size guidance, applied to controls throughout. This one matters most on a phone, which is where most study happens.
Stage identity is never colour alone
Learn, Recall, Practise and Revisit each carry a word and a shape as well as a colour, so nothing depends on distinguishing two hues.
AA text contrast, computed in CI
Body text meets 4.5:1 and large text 3:1 on every surface, in both themes. This is calculated on every build rather than checked by eye — an earlier review by eye had approved text that sat below the threshold.

What has not been tested

Stated plainly, because a list of successes with the gaps left out would tell you less than nothing.

So we do not claim conformance with WCAG 2.1 or 2.2 at any level. Some of the individual criteria above are met and we have said which; the overall conformance claim needs an audit that has not happened.

If something does not work

Email support@kematra.com and describe what happened — what you were trying to do, and what got in the way. You do not need to name a standard or use particular words. A specific report from one person is worth more to us than another round of self-assessment, and it is the fastest route to a fix.