Accessibility statement for venturuseam.com

The target is WCAG 2.2 at level AA

Version 2.2 of the Web Content Accessibility Guidelines, at level AA, is the target for every page on venturuseam.com.

What this site does to meet it

• All content is ordinary HTML. Every page reads completely with scripts turned off. 3D scenes and motion are added on top of the text and never replace it, and anything a scene shows is also written next to it as ordinary text.
• Keyboard-reachable navigation and forms. The menus, the search palette, the forms and the footer links can all be reached and operated with a keyboard, and a skip link at the top of every page jumps straight to the content.
• Visible focus. Every link, button and field shows a clear focus ring when it is reached from the keyboard.
• A still alternative for every animation. When your system asks for reduced motion, animations and smooth scrolling are replaced by a static version of the same content.
• Text alternatives. Images that carry meaning have text alternatives, and purely decorative visuals are hidden from assistive technology.
• Color contrast on the brand palette. Text and controls are checked for AA contrast against the surfaces they sit on.
• Structure you can navigate. One first-level heading per page, headings in order, landmarks for the header, navigation, main content and footer, breadcrumbs, and form fields tied to their labels with required fields marked in text and errors announced.
• Forms that work without scripts. Every form on the site is a plain HTML form that submits without JavaScript.

Tell us what got in your way

Write to sales@venturuseam.com. Include the page address, what you were trying to do, and the browser and any assistive technology you use. A person replies within one business day, and problems reported this way go to the front of the queue for the next release.

Accessibility in the product itself

VenturusEAM, the product, runs an automated accessibility audit on every change, in the build pipeline against a recorded baseline. A change that adds a new problem fails the build and does not merge.

When this statement was written and when it changes

Written on September 30, 2026, from how the site is built, and updated whenever the site changes in a way that affects it.