legal / accessibility

Accessibility.

Last updated: August 5, 2026

Nurvtronix LLC wants everyone to be able to use nurvtronix.com, builtbynurv.com, and nurvos.ai, including people who browse with a screen reader, a keyboard only, magnification, or reduced motion enabled. This statement describes the standard we hold ourselves to, how we verify it, and how to tell us when we get it wrong.

1. Conformance target

We target WCAG 2.2 Level AA across every page of every site. WCAG 2.1 Level AA is the benchmark the US Department of Justice adopted in its 2024 web accessibility rule and the standard US courts most often apply under the Americans with Disabilities Act; WCAG 2.2 AA is its superset, so meeting it satisfies both.

2. How we verify it

Accessibility here is enforced by a build gate, not by good intentions. Every deploy of every site is blocked unless an automated audit passes with zero findings across all pages, at both desktop and mobile widths. That audit checks colour contrast against the 4.5:1 (and 3:1 large-text) thresholds, minimum 24×24 target sizes, a visible keyboard focus indicator on every interactive control, a programmatic label on every form field, a skip-to-content link, honouring of prefers-reduced-motion, and the presence of a page heading. We additionally run axe-core against the WCAG 2.2 AA rule set, and we test by keyboard and screen reader by hand, because automated tools cannot catch everything.

3. Measures we have taken

  • Every text colour meets or exceeds the WCAG AA contrast minimum against our background.
  • A "Skip to content" link is the first stop on every page.
  • Every link, button, and form control shows a visible focus ring when reached by keyboard.
  • Every form field has a programmatic label; placeholders are never used as the only label.
  • Animation, including the custom cursor and scroll reveals, stops when your system requests reduced motion.
  • Pages reflow to a 320px viewport with no horizontal scrolling.
  • We do not use an accessibility overlay widget. Overlays do not fix the underlying page; we fix the source.

4. Known limitations

We are not aware of any outstanding WCAG 2.2 AA failure at the date above. Some content is presented in a deliberately terminal-like visual style; if any part of it is hard for you to read or operate, that is a defect we want to hear about, not a design choice we will defend.

5. Tell us about a barrier

If any part of these sites is difficult or impossible for you to use, email [email protected] with the page address and what went wrong. We aim to acknowledge within 3 business days and to fix confirmed barriers as a priority. If you need information from a page in a different format, ask and we will provide it.

6. Enforcement

This statement is provided in the spirit of the Americans with Disabilities Act and the European Accessibility Act. It does not waive any right you have, and it is not a substitute for your ability to raise a complaint with a regulator.

← cd ~