Legal

Accessibility Statement

Vertical Edge AI is committed to keeping verticaledgeai.ai usable by everyone, including people who rely on assistive technology. This page describes the standards we target, what we have implemented, what we are still working on, and how to reach us if something is not working for you. Last updated: 2026-08-26.

1. Commitment

The Site is designed against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We treat accessibility as part of the design system rather than an afterthought; the regulated-industries buyers we serve include people inside those organizations who use assistive technology.

2. Standards we target

3. What is implemented

  • Semantic HTML5 landmarks are part of the shared site template: <header>, <nav>, <main id="main-content">, <footer>.
  • Skip-to-content link is part of the shared template; it is off-screen until focused, then becomes visible.
  • ARIA wiring on interactive widgets: FAQ accordion (aria-expanded, aria-controls, aria-labelledby, role="region") and mobile navigation toggle (aria-expanded, aria-controls).
  • Contact access uses the intake form on the contact page. Every visitor-facing field carries a visible <label> bound by for / id; required fields are marked in the label text as well as with the required attribute; the required-data acknowledgment is a labelled checkbox, not a colour cue; validation and submission messages are written into a role="status" aria-live="polite" region so they are announced rather than only shown; and the fields follow document order, so keyboard and screen-reader users reach the submit control last.
  • Color contrast. Primary text (Prussian Blue #0D1B2A) on white surfaces is approximately 13:1 (WCAG AAA). Secondary text (Steel Slate #5C6B7A) on white is approximately 6.2:1 (AA). Burnished Gold (#C4A35A) is reserved for headings, eyebrows, and interactive accents only, never body text (~3.2:1 on white, AA for large text and UI components).
  • Focus indicators via :focus-visible — 2px solid gold outline with 3px offset, applied site-wide.
  • Prefers-reduced-motion: every transition and reveal animation is wrapped in a @media (prefers-reduced-motion: reduce) override that disables them.
  • No autoplay video, no auto-rotating carousels, no automatic timing-based focus shifts.
  • Resizable text without horizontal scroll up to 200% browser zoom.
  • Theme-color meta set to Prussian Blue (#0D1B2A) so mobile browser chrome respects brand contrast.

4. Testing approach

The design system targets WCAG 2.2 contrast and keyboard operation. Current automated release checks cover structure, routes, claims, and responsive overflow; a complete keyboard and assistive-technology audit has not yet been recorded.

Planned before any public production launch: NVDA (Windows) and VoiceOver (macOS / iOS) screen-reader walks of the full site, and a Lighthouse + axe-core lab audit.

5. Known limitations

  • The Open Graph share image at /assets/og.png is a rasterized brand card; it does not carry alt text in the file itself. Social platforms generate their own alt text from the page’s og:title and og:description, both of which are descriptive.
  • The site has not yet undergone a third-party VPAT (Voluntary Product Accessibility Template) audit. We will commission one when a customer engagement requires it.
  • Long-form articles in the Resources section use EB Garamond italic for editorial emphasis. Italic serif at small sizes can be slightly harder to read for users with low vision; we keep italic use limited to short accent phrases, never full paragraphs.

6. Conformance posture

We design the Site against WCAG 2.2 AA. We do not claim AAA, and we do not claim certification by any accessibility body. The known limitations listed in Section 5 are tracked and will be addressed in subsequent updates.

7. Reporting an accessibility issue

If anything on the Site is not working for you, please submit a report through the intake form on our contact page and write “Accessibility feedback” in the message. Please tell us: (a) which page; (b) what assistive technology you are using; (c) what you were trying to do; and (d) what happened. We aim to acknowledge accessibility reports within a few business days and to share a remediation timeline within two weeks.

8. Remediation process

Reports are triaged by severity. Critical issues (anything that blocks access for users of assistive technology) are addressed first. Lower-severity issues are batched into design-system updates.

9. Related resources

10. Contact

Accessibility inquiries: the intake form on our contact page
Vertical Edge AI LLC, Austin, TX

Last updated: 2026-08-26. We update this statement annually or as the Site’s accessibility posture changes.