Skip to main content
Invoset

Legal

VPAT 2.5 Accessibility Conformance Report

This document summarizes the accessibility posture of the Invoset application using the VPAT 2.5 template. It covers the public marketing site, the authenticated dashboard, the public verification page, and the embeddable badge.

Effective
June 8, 2026
Last updated
June 8, 2026

Product information

  • Product: Invoset web application
  • Vendor: Ravencord Inc., 6688 Nolensville Rd, Ste 108 #2225, Brentwood, TN 37027, United States
  • Registered agent (Delaware service of process): Legalinc Corporate Services Inc., Newark, DE
  • Contact: accessibility@invoset.com
  • Report version: 1.1
  • VPAT template version: 2.5Rev INT (April 2023)
  • Standards covered: WCAG 2.1 Level A and Level AA

Evaluation methods used

This report combines two evaluation methods, each cited in the conformance levels below:

  • Automated testing using an industry-standard rule engine against every page in the public sitemap and the authenticated dashboard.
  • Manual keyboard-only testing across the primary user journeys (sign up, add site, verify domain, run scan) and the public marketing flow (landing, pricing, blog, contact).

Planned but not yet engaged: External manual review by a CPACC-certified auditor. The first external audit is targeted for Q3 2026 and this report will be re-issued after that pass.

VPAT 2.5 distinguishes "Supports", "Partially Supports", "Does Not Support", and "Not Applicable". A criterion is recorded as Partially Supports when the automated and manual passes uncovered any non-trivial defect, and as Not Evaluated when neither pass has covered it yet.

Applicable standards/guidelines

  • WCAG 2.1 Level A: Partially evaluated. See criteria evaluated to date below; criteria not listed are Not Evaluated pending the external audit cycle.
  • WCAG 2.1 Level AA: Partially evaluated. See criteria evaluated to date below; criteria not listed are Not Evaluated pending the external audit cycle.
  • Revised Section 508 (36 CFR Part 1194) Chapter 5 (Software): the criteria that map directly to WCAG 2.1 Level A and AA are addressed by the WCAG conformance above. Section 508-specific criteria (502 Interoperability with Assistive Technology, 503 Applications, 504 Authoring Tools) have not yet been evaluated and are recorded as Not Evaluated pending a Section 508 specialist review.
  • EN 301 549 V3.2.1: relevant criteria mirror WCAG 2.1 AA.

WCAG 2.1 Level A: criteria evaluated to date

  • 1.1.1 Non-text Content: Supports. All informational images carry alt text or are aria-hidden when decorative.
  • 1.3.1 Info and Relationships: Supports. Semantic landmarks and headings in every page.
  • 2.1.1 Keyboard: Supports. All interactive controls are reachable and operable from the keyboard.
  • 2.4.1 Bypass Blocks: Supports. A skip link is the first focusable element on every page.
  • 2.4.4 Link Purpose (In Context): Supports. All links are unique within their surrounding context.
  • 3.1.1 Language of Page: Supports. lang="en" set on every page.
  • 3.2.1 On Focus: Supports. No focus event triggers a context change.
  • 4.1.2 Name, Role, Value: Supports. ARIA attributes used only when needed; otherwise native semantics.

WCAG 2.1 Level AA: criteria evaluated to date

  • 1.4.3 Contrast (Minimum): Supports. Body text and inline link text against the cream background were measured at 5.0:1, exceeding the 4.5:1 minimum (verified after the May 2026 design-token adjustment).
  • 1.4.5 Images of Text: Supports. No images of text are used outside the wordmark.
  • 1.4.10 Reflow: Supports. Layout reflows down to 320px without two-dimensional scrolling.
  • 1.4.11 Non-text Contrast: Supports. UI controls and informational graphics meet 3:1.
  • 1.4.12 Text Spacing: Supports. Custom CSS does not interfere with user-agent text-spacing overrides.
  • 1.4.13 Content on Hover or Focus: Supports. Tooltips are dismissable, hoverable, and persistent.
  • 2.4.5 Multiple Ways: Supports. Sitemap, in-page navigation, and search-engine indexing all available.
  • 2.4.6 Headings and Labels: Supports. Headings and form labels are descriptive.
  • 2.4.7 Focus Visible: Supports. focus-visible outlines used throughout.
  • 3.1.2 Language of Parts: Not Applicable. Single-language site.
  • 3.3.3 Error Suggestion: Supports. Form errors describe how to correct the input.
  • 4.1.3 Status Messages: Supports. role="status" used for save toasts and error banners.

Known limitations and remediation timeline

  • 1.4.4 Resize Text: Supports. Body text scales to 200% without loss of content. Beyond 200%, individual dashboard controls may begin to clip; this is outside the WCAG 1.4.4 threshold but is being addressed alongside the next dashboard pass.
  • Embeddable badge: Supports for the SVG itself; the surrounding host page is the customer's responsibility.
  • Public PDFs: Audit-trail and scan PDFs are generated through the browser print pipeline; tagged-PDF output depends on the browser used (Chromium-based browsers emit tagged PDFs). Manual conformance review by a third-party auditor is planned with the next external audit.

Legal notice

This report is provided for informational purposes only. It does not constitute legal advice, a guarantee of compliance, or an indemnification against any claim under the ADA, Section 508, the European Accessibility Act, or any other statute. Ravencord Inc. disclaims warranties of specific accessibility outcomes; see our Terms of Service and Disclaimer for full details.

Procurement teams may request a counter-signed copy of this report on company letterhead by emailing accessibility@invoset.com.