Accessibility Statement

Last updated: September 11, 2026
Applies to: omniweb.tech (this website).

Scope. This statement covers omniweb.tech itself. Invoy, PistonDesk, Nexus, and LetsNow are separate applications with their own interfaces; accessibility issues in those products should be reported through the product itself.

OmniWeb LLC wants everyone — including people using a screen reader, keyboard navigation, voice control, or a magnifier — to be able to use this site. This page describes what we've done and how to tell us if something isn't working.

Our target

We aim to meet WCAG 2.1 Level AA, the standard most commonly used to define web accessibility. This is an ongoing effort rather than a one-time certification — we review and fix issues as we find them.

What we've done

  • A skip-to-content link so keyboard and screen-reader users can bypass the navigation menu.
  • Full keyboard support for the navigation, including the Products menu (opens and closes with Enter/Space, closes with Escape, and returns focus sensibly).
  • Visible focus indicators on every interactive element.
  • Semantic HTML — landmarks, headings in order, and native elements like <details> for the FAQ accordion — instead of custom widgets that need extra ARIA work to behave correctly.
  • Labeled form fields on the contact form, with error and success messages announced to screen readers.
  • Meaningful alt text on informative images (like project screenshots) and empty alt text on purely decorative ones, so screen readers don't announce noise.
  • Color choices checked for contrast against WCAG AA thresholds, in both light and dark mode.
  • Respect for reduced-motion preferences — scroll animations and transitions are turned off if your system asks for them.
  • A responsive layout that reflows for zoomed text and small screens rather than requiring horizontal scrolling.

Known limitations

We haven't run a full third-party audit. Some embedded third-party tools (like the contact form's submission service) are outside our direct control, though we've reviewed the parts we render ourselves. If you hit a specific problem, we want to know about it — see below.

Reporting an issue

If you have trouble using any part of this site, emailsupport@omniweb.tech with the page URL and what happened. We'll do our best to respond within a few business days and fix genuine barriers promptly.