Enovari
Log in Download →
Accessibility

What we have tested, and what we have not.

Section 1

The commitment

Accessibility at Enovari.

Enovari is a memory system for AI assistants. This statement is about this website — the pages you read, the forms you fill in, and the account pages behind the log‑in. It does not cover the desktop application, which has not been assessed.

We want this site to work for you whatever you read it with. Where it does not, the sections below name the problem.

Section 2

The standard

WCAG 2.1 Level AA, assessed by us.

This site is built to the Web Content Accessibility Guidelines 2.1 at Level AA. We do not call it compliant, conforming or certified: nobody independent has checked it, and those three words mean somebody did.

Behind it is our own work: a keyboard walk of every page a signed‑out reader can open, static checks that run on every build, and the readings in section 4. No third‑party audit has been commissioned, and no assistive technology has ever been run against this site. Section 5 lists those two absences first, because they are the largest gaps here.

Section 3

What we’ve built in

Accessibility is engineering, not a statement.

This site is built to WCAG 2.1 AA practices as engineering, and we state only what we have actually done:

  • Semantic landmarks and a skip-to-content link on every page
  • A logical heading order, one h1 per page
  • Keyboard operability for every control, including the header menu, which closes on Escape
  • Visible keyboard focus outlines on every control — never switched off, and never invisible
  • Labelled form fields, with the label tied to its input
  • AA colour contrast, computed against the ground each element actually sits on
  • Alt text on every image
  • Reduced-motion support that stops every animation, canvas and transition when your system asks for it
  • No third-party script, and no font or asset fetched from another domain

What we have not done: a paid third-party audit. We test with keyboard-only navigation and automated checks on every change, and the section below measures this page live — but none of that is an independent audit, and we will not describe it as one until there is one.

If anything on this site is hard for you to use, that's a bug to us. We do not promise a fix we have not made — section six of this page traces exactly what happens to what you send, and names a phone number as well as our support form.

Section 4

Measured here

This page, read in front of you.

Nine readings, computed from this page in your browser as it loads. They are arithmetic about markup and pixels — none of them says what a screen reader announces. They need JavaScript; nothing else here does.

  • Landmark elements

    —

    needs JavaScript

  • Heading order

    —

    needs JavaScript

  • Images without alt text

    —

    needs JavaScript

  • Tightest text contrast

    —

    needs JavaScript

  • Text elements measured

    —

    needs JavaScript

  • Things in motion right now

    —

    needs JavaScript

  • Keyboard stops on this page

    —

    needs JavaScript

  • Files fetched from another domain

    —

    needs JavaScript

  • Time these readings took

    —

    needs JavaScript

Tab through these three and the readout follows your focus.

Known limitations Report a barrier Back to the readings

Focus is on nothing yet

Section 5

Known limitations

Six things this site does not do yet.

Each one names the file it was read from and the day it was read.

  1. No assistive technology has been run against this site

    Not a screen reader, not a magnifier, not a switch device, not voice control — by us or by anyone else. If one of them reads this site wrongly, we will not know until you tell us.

    Stated 2026‑09‑22.

  2. Two pages have never been walked with a keyboard

    The account page and the downloads page send a signed‑out reader to the log‑in page, so our own walk has never reached them. Every other page has been walked.

    Read from the script that guards them, 2026‑09‑22.

  3. The support form cannot send without JavaScript

    The form carries no action, so with scripting off the browser posts the page back to itself and your message goes nowhere. Use the phone number in section 6.

    Read from the built support page, 2026‑09‑22.

  4. “Message sent” is not a receipt

    That confirmation appears as soon as the server accepts the message. Nothing here tells you whether it was stored or whether a person read it, and there is no reference number.

    Read from the script that submits the form, 2026‑09‑22.

  5. Escape closes the header menu and drops your place

    Escape does close it, but nothing returns focus to the button that opened it, so the next Tab resumes below the header. The fix is not made yet.

    Read from the shared header script, 2026‑09‑22.

  6. One focus ring fades in instead of appearing

    On the privacy and terms pages, the button in the closing band inherits a transition with a duration and no property list, so its focus ring animates in instead of being drawn at once. It is there after a beat. The same button on this page is corrected.

    Read from the inherited stylesheet, 2026‑09‑22.

When one is fixed it comes off this list.

Section 6

Feedback

Telling us it is broken, and what happens then.

Tell us the page, what you were trying to do, and what happened instead. That is the report we most want.

Those are the only two routes: there is no email address, issue tracker, chat or postal address anywhere on this site. We do not publish a reply time.

What happens to what you send

  1. You fill in four boxes: your name, your email address, your message, and a phone number if you want to give one.
  2. A fifth box sits with them, invisible and skipped by the keyboard, to catch automated senders.
  3. The script checks the three required boxes before anything leaves your browser.
  4. It posts what you typed to an endpoint on this site. Nothing here sends anything anywhere else.
  5. The send button is disabled while the request is out.
  6. If the server accepts it, the form is replaced by “Message sent.” See limitation four.
  7. If it does not, the reason appears in a paragraph marked as a live region and you can try again.

Read from the built support page and the script that submits it, 2026‑09‑22.

Section 7

Preparation

How this statement was prepared.

This statement was prepared on 2026‑09‑22 by self‑evaluation. Every claim on it was re‑checked that day against the files this site is built from — all 25 published pages and their stylesheets. Anything that could not be checked was removed. It replaces a much longer statement whose counts had gone stale. We review it whenever the site changes.

Questions

Ask us anything about your data.

A person reads it, not a queue.

Contact us