Accessibility statement
Our conformance status against WCAG 2.2 AA, the known gaps, and how to report a barrier.
Last updated:
Our commitment
Nordvec designs its website, product and documentation to work with a keyboard, a screen reader and other assistive technologies. This applies to an individual account and to a workspace in the same way.
Standard we measure against
We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA and with EN 301 549 v4.1.1, the European accessibility standard whose web requirements follow WCAG 2.2. We do not claim a presumption of conformity under the European Accessibility Act (Directive 2019/882): no version of EN 301 549 is yet cited under that Directive in the Official Journal, so we work to its accessibility requirements directly. These cover keyboard operation, colour contrast, focus visibility, semantic structure, and compatibility with screen readers and other assistive technologies.
The service
Nordvec is an assistant that answers questions from your own documents. You connect the sources you already use or upload files; Nordvec indexes them in the EU and answers in a conversation, citing the passages each answer is drawn from so you can open and check them. You use it in a web browser, in the desktop application or in the browser extension, with the same account, and it works the same way for an individual account and for a workspace.
Conformance status
Nordvec is partially conformant with WCAG 2.2 AA. Partially conformant means that some parts of the experience fully meet the standard while others do not yet. Our product documentation, the public website and the signed-in application are audited automatically against WCAG 2.2 AA; the manual assistive-technology review of the application and of the embedded API reference has not yet been completed.
Scope of this statement
This statement covers the public Nordvec website and product documentation at nordvec.com, including the marketing pages, the product guides and the API reference; the Nordvec web application you use after signing in; the Nordvec desktop application, which shows the same web application in its own window; the Nordvec browser extension, which shows it in the browser's side panel; and the emails Nordvec sends you. It does not cover third-party content or services that we link to but do not control.
How the service meets the accessibility requirements
The service is built to be operated from the keyboard alone, and its keyboard shortcuts are listed in the application under Keyboard shortcuts. Each page of the website, the product guides and the signed-in application starts with a link that skips to its main content. A screen reader is told when an answer starts, when it is complete and when it failed, and each answer names its speaker, so a conversation can be followed without looking at it. Focus moves to a new answer when you ask for one again and returns to the message field when an answer ends. The message field is described by the notice that you are interacting with an AI system, so a screen reader reads the notice when you reach the field. Sign-in fields work with password managers and accept pasting, and no step asks you to solve a puzzle. Animation is reduced when your system asks for reduced motion. Information about the service and support for it are available in the formats described in the feedback section.
How we test
Every code change is checked by a static accessibility lint that refuses the defects it can prove, such as an image without a text alternative, a control that cannot be operated from the keyboard, or invalid ARIA markup. Before every change ships, the documentation and website pages it can reach are rendered in a real browser and audited against WCAG 2.2 AA rules with axe-core, together with their keyboard order. Every rendered page, the signed-in application included, is also audited in full in a scheduled weekly run and on demand. We add manual keyboard-only and screen-reader passes, which are not yet complete.
Known limitations
Known gaps: the signed-in application and parts of the marketing site have not completed a manual assistive-technology review, automated checks find only part of what a person using assistive technology meets, and the interactive API reference is a self-hosted third-party component whose conformance we are still verifying. The invoices and credit notes we issue as PDF carry a document title and language but not yet the structure tags a screen reader uses to navigate a document; the number, date, amount and status of each one are also listed on the billing page in the application. The page where you enter card or bank details is operated by our payment provider and its accessibility is stated by them. The activity digest and the notification emails are in English only; the other emails we send are in the language you use Nordvec in. The desktop application's own window controls, menus and notifications have not yet been assessed; the application inside the window is the web application this statement covers. Where a barrier prevents you from completing a task, contact us and we will provide the information in an accessible alternative without undue delay.
Feedback and how to reach us
If you encounter a barrier or need content in a different format, email us at accessibility@nordvec.com. Tell us the page, what went wrong, and the assistive technology you were using if relevant. If you would rather hear this statement or any other information about the service than read it, ask in the email and we will go through it with you on a phone or video call. We aim to acknowledge accessibility feedback within five working days and to offer an accessible alternative for the content you needed.
Enforcement procedure
If you contact us about an accessibility barrier and are not satisfied with our response, you can escalate to the accessibility enforcement body in your EU member state. Each member state designates an authority responsible for the European Accessibility Act; your national consumer-protection or accessibility authority can direct you to the correct contact.
How this statement was prepared
This statement was prepared on July 13, 2026 and last reviewed on September 18, 2026. It is a self-assessment: automated WCAG 2.2 AA testing of the documentation, the website and the signed-in application, and a manual review that is not yet complete. We review it at least once a year and after any change that could affect accessibility.