Accessibility Statement

Neo Security, Inc. (“Neo,” “we,” or “us”) is committed to making its web surfaces accessible to the widest possible audience, regardless of ability or technology. We treat accessibility as a build requirement rather than a remediation phase: the people who design and build Neo are responsible for its accessibility, in the same change that ships the work.

Scope

This statement covers:

• the Neo website at https://www.neo.ai;
• the Neo application at https://app.neo.security, including the customer dashboard for inventory, policies and activity, and the sign-in flow; and
• Neo customer documentation.

These surfaces are covered in both light and dark themes. The content assessed is English-only, and the dashboard is designed for desktop use.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

Neo supports WCAG 2.2 Level A and Level AA. Within the scope and reporting basis described in this statement, every applicable success criterion is recorded as “Supports” — meaning the functionality has at least one method that meets the criterion without known defects, or meets it with equivalent facilitation. Conformance is scoped for full pages and complete processes, as set out in the WCAG 2 Conformance Requirements.

Neo maintains an Accessibility Conformance Report (ACR) covering this assessment, prepared on the Voluntary Product Accessibility Template (VPAT®) version 2.5Rev, WCAG Edition. Customers and prospective customers can request the current report from accessibilitysupport@neo.ai.

Measures We Take

Accessibility requirements are written into the engineering standard Neo is built to, and are reviewed as part of the work rather than after it. In practice that means:

• Native semantics first. Interfaces are built from real HTML landmarks, headings, buttons, and links. Controls expose accessible names, roles, values and states; inputs use explicit labels and error associations. ARIA is added only where a native element cannot express the behaviour, because incorrect ARIA is worse than none.
• Keyboard operability. Navigation, search, policy controls, authentication and documentation can be operated by keyboard alone, with a visible focus indicator and a logical focus order. Dialogs and panels can be entered and left with standard keyboard controls, and closing one returns focus to the invoking control or a logical fallback. Focus is never dropped, and is not obscured by overlays or fixed navigation.
• Pointer alternatives. Functionality can be completed with ordinary single-pointer interactions, without multi-point or path-based gestures. Where dragging is offered, an equivalent single-pointer control is provided alongside it.
• Reduced motion. Animation is gated behind the prefers-reduced-motion setting. Readers who ask their operating system to reduce motion receive a version with the motion removed, not merely shortened.
• Contrast and target size. Text meets a minimum contrast ratio of 4.5:1, and 3:1 for qualifying large text. Control boundaries, focus indicators and meaningful graphics meet 3:1. Pointer targets meet the minimum target-size requirement or an applicable spacing exception. Each threshold is checked in both themes.
• Reflow, resize and text spacing. Content remains usable at 320 CSS pixels or equivalent zoom without horizontal page scrolling, and text can be resized to 200% without loss of content or functionality. Text-spacing overrides can be applied in both themes without clipping. Wide data tables may scroll within their own containers where a two-dimensional presentation is necessary.
• Meaningful alternatives. Meaningful images, icons and charts have text alternatives or equivalent text and data presentations. Decorative imagery is hidden from assistive technology so it does not add noise. No information is available only as text embedded in an image.
• Status and errors. Search results, required-field feedback and form errors are announced through appropriate status or alert semantics, without requiring users to find the message manually. Correctable errors provide guidance, and destructive actions request confirmation and offer a cancel action.

Assessment Approach

Neo assesses accessibility by internal automated and manual evaluation, carried out by our engineering and product teams.

Methods include automated accessibility test suites, AI-assisted checks, and manual keyboard and VoiceOver evaluation of major flows, together with targeted checks for text resize, reflow, text spacing, contrast, focus behaviour, target size and authentication. Every shipped change receives automated checks, supplemented by manual testing of major flows.

The manual testing environment is Google Chrome on macOS with the built-in VoiceOver screen reader. Additional automated coverage in Safari and Edge is confirmed. Other screen-reader and browser combinations are not individually represented in our testing, and this assessment is an internal evaluation rather than an audit by an independent third party.

Third-Party Content

Some components embedded in our website are provided and controlled by third parties, including HubSpot forms, Google reCAPTCHA, and Google Tag Manager. We do not control the markup these services inject, and their accessibility is governed by those providers, so they fall outside the scope of the conformance status above.

If a third-party form or control prevents you from reaching us, contact us directly at the address below and we will take your request by email instead. Job listings are likewise synced from Greenhouse; the source text is authored in that system, though we render it in our own markup.

Compatibility With Browsers and Assistive Technology

Neo is designed to be compatible with current versions of major browsers — Chrome, Safari, Firefox, and Edge — used together with the assistive technologies that are standard on those platforms, including screen readers, voice control, browser zoom, and operating-system contrast and motion preferences.

Neo may not display or behave as intended on browsers more than two major versions out of date, or with assistive technology that does not support the web standards listed below.

Technical Specifications

Accessibility of Neo relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer: HTML, CSS, SVG, and JavaScript. These technologies are relied upon for conformance with the accessibility standard described above.

Feedback and Reporting a Barrier

We welcome your feedback on the accessibility of Neo. If you encounter a barrier, or need information in a different format, please tell us:

Email: accessibilitysupport@neo.ai

When you contact us, it helps if you can describe the page you were on, what you were trying to do, and the browser and assistive technology you were using — but please do not let missing details stop you from writing to us. We aim to acknowledge accessibility feedback within five business days, and we will tell you what we intend to do about the issue and when.

If you are not satisfied with our response, you may ask that your report be escalated within Neo by replying to our acknowledgement and asking for escalation. We will route the matter to a member of our leadership team.

Changes to This Statement

We review this statement as Neo changes, and revise it when our conformance status, scope, or contact arrangements change.

This statement was prepared on 17 September 2026, and reflects our assessment as at that date.