Accessibility Statement

Neivan Technology Holdings, LLC ("Neivan") wants everyone to be able to use Synapse, including people who navigate with a keyboard, use a screen reader or a screen magnifier, need larger text or stronger contrast, or prefer less motion on screen. This page says what we aim for, where we actually are today, and how to tell us when we get it wrong.

We would rather publish an honest account of an unfinished job than a claim we cannot support.

1. The standard we work to

We work to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium. It is the benchmark most accessibility laws and procurement processes refer to, including Section 508 in the United States and EN 301 549 in Europe.

2. Where we are today: partially conformant

Synapse is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means most of the standard is met, and some parts are not. The parts that are not are listed in section 4, rather than left for you to discover.

This page covers:

• the Neivan website at https://neivan.ai;
• the Synapse platform at https://os-synapse.ai;
• our internal operations console, which only Neivan staff use. It is included because our own colleagues deserve the same standard, and because saying so keeps us honest about it.

3. What is in place

• Keyboard. Every page begins with a "skip to main content" link. Buttons, links, form fields, menus and dialogs can be reached and operated with the keyboard alone, and the element you are on shows a visible focus outline. Dialogs keep the keyboard inside them while open and return you to where you were when they close.
• Screen readers. Pages use real headings and landmarks; images carry text alternatives, or are marked decorative when they carry no meaning; buttons that show only an icon still have a name; form fields are joined to their labels, and to their hint and error text, in the page code rather than only by position on screen. Replies from an agent, saved changes and error messages are announced as they arrive, instead of appearing silently.
• Colour and contrast. Body text is checked against its background to at least the 4.5:1 ratio the standard requires, in both our light and dark themes. Colour is not the only way we indicate status: a colour is always paired with a word or a shape.
• Motion. If your device is set to reduce motion, animations and looping effects are switched off.
• Language and titles. Each page declares its language and carries a title describing that page, so you can tell where you are.

Some of this is enforced automatically: accessibility rules run against our code on every change, and a test recalculates our text contrast ratios and fails the build if any fall below the standard.

4. Known problems

These are the gaps we know about. We are working on them.

• We have not yet completed a full manual screen-reader review. Our checks so far are automated ones plus keyboard testing by hand. Automated tools catch roughly a third of accessibility problems; only a person listening to a page catches the rest. This review, and automated checks against every page rather than individual components, are our current priority.
• Some text on our public website has too little contrast, particularly faint grey body text and the placeholder text inside some form fields.
• A few status indicators on our public website are small coloured dots with no accompanying word, so their meaning depends on seeing the colour.
• Two decorative animated graphics on our website respond to a mouse but not to a keyboard. Nothing is only available through them.
• Sessions end after a period of inactivity without warning you first, and without offering to extend. The standard asks for a warning and a way to continue.
• Some controls are smaller than the 24-by-24-pixel minimum target size, which makes them harder to hit accurately on a touchscreen or with an imprecise pointer.
• Dialogs in our internal operations console do not yet keep the keyboard inside them while open, as the customer-facing ones do.
• We have not commissioned an independent accessibility audit, and we have not published a Voluntary Product Accessibility Template. Our assessment is our own.

5. How we assess this

We self-evaluate, continuously rather than once. Accessibility rules run in our automated checks whenever code changes, so a new problem of a kind we already understand is caught before it reaches you. Beyond that, we test by keyboard by hand, and we measure colour contrast by calculation rather than by eye. An independent audit is something we intend to commission; we have not yet done so.

6. Tell us when something does not work

If any part of Synapse or our website is difficult or impossible for you to use, please email [email protected] with "Accessibility" in the subject line.

It helps if you can tell us:

• the page or the address where you hit the problem;
• what you were trying to do;
• what happened instead;
• the browser, device and any assistive technology you were using, if you know.

We aim to acknowledge every accessibility report within 5 business days, and to tell you what we are going to do about it and roughly when. If something is blocking you from work, say so and we will look for a way around it while we fix the underlying problem.

If you are not satisfied with our response, write to [email protected] and it will be looked at again by someone else.

7. Buying Synapse for your organization

If your procurement process needs an accessibility conformance report, a completed Voluntary Product Accessibility Template, or answers to a specific questionnaire, email [email protected]. We do not have a completed report today; we will answer your questions directly and honestly in the meantime, and we will tell you plainly what has been verified and what has not.

8. How current this page is

We review this page whenever accessibility work ships, and at least every six months. If something here no longer matches what you experience, that is a problem with this page as much as with the product, and section 6 is the way to tell us.