Accessibility Statement

Last updated: April 27, 2026

Vrge is built by TRD Ventures LLC. We believe that software for working professionals should be usable by working professionals — including those who rely on assistive technologies, keyboard navigation, screen readers, captions, or custom display settings to do their work.

This statement covers the Vrge marketing website (getvrge.com) and the Vrge desktop application.

Conformance target

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. WCAG 2.1 AA is the standard most jurisdictions reference (EU EAA, ADA Title III guidance, Section 508 alignment) and the one we consider the right baseline for a tool used in professional work.

Current status

We aim for full WCAG 2.1 AA conformance and we are not there yet. As a small, single-developer team we're building accessibility in from the start rather than retrofitting later — but a formal third-party audit has not yet been conducted. We will publish the audit results when one is complete.

Concrete commitments today:

• All interactive elements are reachable and operable by keyboard alone. Focus indicators are visible and respect prefers-reduced-motion.
• Semantic HTML and ARIA roles are used for navigation, tab panels, dialog windows, and form controls.
• Text contrast targets WCAG AA at minimum (4.5:1 for body text, 3:1 for large text and UI components).
• Images that convey meaning include descriptive alternative text; decorative images are marked aria-hidden.
• The interactive demo on the homepage is labelled and operable by keyboard, with the same data accessible without animation.
• Forms communicate errors textually, not by colour alone.

Known limitations

We are honest about what isn't there yet. As of the date above:

• The site has no light-mode toggle. We use a dark theme that meets AA contrast targets, but a light option is on the roadmap for users who prefer or require one.
• The interactive demo includes drag-and-drop on the Pipeline view. Keyboard equivalents work, but the screen-reader announcements for drag-state changes are still being refined.
• Some long-form pages (Privacy, Terms, License) use single-column layouts without an in-page table of contents. We intend to add one.
• We have not yet completed a third-party accessibility audit. We will commission one and publish results.

The desktop application

Vrge ships as a Tauri-based desktop app for macOS and Windows. It inherits OS-level accessibility features — system fonts, system contrast settings, screen reader integration via the platform accessibility API, and keyboard-only operation. We follow the same conformance target on the desktop UI as on the website.

How to report an issue

If you encounter an accessibility barrier — anywhere on the site or inside the desktop app — please tell us. We treat accessibility reports with the same priority as a security report: triage within one business day, fix targeted within two weeks for in-scope issues.

Email accessibility@getvrge.com with:

• The page or screen where you encountered the issue
• What you were trying to do and what happened (or didn't)
• Your assistive technology (screen reader name + version, OS, browser if relevant)

If a barrier is blocking you from using something you've paid for, also email hello@getvrge.com and we'll work with you on an immediate alternative path while we fix the underlying issue.

Changes to this statement

We will update this page as conformance improves and as known limitations are resolved. Material changes are reflected in the “Last updated” date at the top.