← Trust center
Trust center · Accessibility statement

WCAG 2.1 Level AA, and where we still fall short.

Our commitment, our current conformance status, what we have implemented, the limitations we know about, and how to report a barrier.

Effective
22 Aug 2026
Version
v1.3
Owner
Winrove Trust Desk
Contact
hello@winrove.com

01Our commitment

Winrove targets Web Content Accessibility Guidelines (WCAG) 2.1 Level AA conformance. Many of our customers are federal contractors carrying Section 508 obligations of their own, and we treat that as our baseline rather than as an optional concern.

Accessibility is part of our definition of done: a feature that excludes a population of users is not finished, even if it ships.

02Conformance status

On 22 August 2026 we ran axe-core against the marketing core URL set: home, pricing, features, contact, templates, capability-statement, free-tools, compare, and help. That pass recorded 0 critical and 0 serious findings on Firefox and WebKit.

We do not claim full WCAG 2.1 Level AA conformance. Color contrast was not instrumented in that pass, and the known limitations below still apply to the product and to some marketing surfaces. We do not display a conformance badge.

03What we do

  • Semantic HTML throughout, with landmark regions and heading hierarchy that screen readers can navigate.
  • Full keyboard operability for every interactive element. Visible focus indicators on all controls.
  • Color tokens are chosen toward 4.5:1 for body text and 3:1 for large text and controls. Contrast was not instrumented in the 22 Aug 2026 axe pass, so those ratios are a design target, not a measured claim.
  • Text alternatives for all meaningful images. Decorative images marked as such.
  • Explicit labels and error messages on every form field. Required fields announced.
  • Responsive layouts that remain usable at 200% browser zoom and on narrow viewports.
  • ARIA attributes used only where standard HTML semantics are insufficient.
  • Reduced-motion preferences respected for animations and transitions.

04Known limitations

We will not pretend this list is complete. Areas we are actively working on:

  • Third-party embeds. Stripe checkout iframes inherit Stripe's accessibility implementation, which is generally strong but outside our direct control.
  • Complex data visualizations. Some analytics charts in the dashboard do not yet have full table-equivalent alternatives. A text-summary toggle is in progress.
  • PDF exports. Generated proposal PDFs are being upgraded to PDF/UA so they are reliably tagged for screen readers. Current exports include text layers but are not yet fully tagged.
  • Data-dense marketing pages. Some editorial layouts on the marketing site use decorative plates and dense tables; we are auditing them against 1.3.1 (Info and Relationships) as they are redesigned.
  • Color contrast. The 22 Aug 2026 axe pass did not instrument contrast, so we do not treat WCAG 1.4.3 as verified.
  • No accessibility overlay. This marketing site does not load a third-party overlay widget (UserWay, accessiBe, or similar). Dated 22 Aug 2026.

05Reporting issues

If you encounter a barrier on any page or in the product, email hello@winrove.com with:

  • The URL of the page
  • The assistive technology you were using (NVDA, JAWS, VoiceOver, etc.) and version
  • Steps to reproduce
  • What you expected and what happened instead

We respond within 5 business days and prioritize accessibility regressions ahead of other bug work.

06Technical specifications

This marketing site uses HTML5, WAI-ARIA, CSS, and vanilla JavaScript. Interactive tools and the product-tour preview use React 18. It is tested against:

  • Current versions of Chrome, Firefox, Safari, and Edge on desktop and mobile
  • NVDA and JAWS on Windows
  • VoiceOver on macOS and iOS
  • TalkBack on Android

07Contact

Accessibility coordinator: hello@winrove.com. We read every report.