Accessibility Statement

Visual Sentinel aims to be usable by the widest possible audience, including people with visual, hearing, motor, or cognitive impairments. We target the WCAG 2.1 Level AA success criteria across both our marketing site and the authenticated dashboard.

We design and build with these practices in mind:

• Semantic HTML for landmarks, headings, lists, and forms.
• All interactive controls reachable by keyboard, with visible focus indicators.
• Sufficient color contrast on text, icons, and UI chrome (dark mode included).
• Alt text on informative images. Decorative images use empty alt attributes.
• ARIA labels on icon-only buttons, and aria-live regions for toasts and alerts.
• Support for system-level prefers-reduced-motion and prefers-color-scheme.
• Screen reader-friendly date, time, and number formatting localized to your organization timezone.

We are actively working on the following areas where conformance is partial:

• Some legacy form inputs on the /contact page are missing programmatic label associations. Tracked in our backlog and being fixed.
• Interactive charts on analytics dashboards render via canvas; we are adding data-table fallbacks for screen-reader access to underlying numbers.
• The embedded API documentation is rendered by a third-party component (Scalar). We follow their accessibility releases and upgrade when fixes ship.

We combine automated and manual testing. Automated: axe-core, Lighthouse accessibility audits, and ESLint jsx-a11y rules enforced in CI. Manual: periodic keyboard-only and screen-reader (VoiceOver, NVDA) walkthroughs on signup, monitor creation, incident response, and settings flows.

If you encounter an accessibility barrier, please tell us. We aim to acknowledge reports within one business day and to fix or publish a workaround within two weeks for most issues.

Email accessibility@visualsentinel.com with the page URL, a short description of the barrier, and which assistive technology you are using (if any). Screenshots or recordings are welcome but not required.

This statement is prepared with reference to WCAG 2.1 AA and the European Accessibility Act (EU 2019/882), which entered into force for private-sector digital services on 28 June 2025.