Sign inGet started
← All policies

Recovea Accessibility Statement

Last updated: 2026-07-25

1. Our commitment

Recovea, Inc., a Delaware corporation ("Recovea," "we," "us," or "our"), is a bootstrap-funded United States company. We design, build, and operate the Recovea service for AI-spend metering, observability, optimization, spend control, reporting, verification, and related managed offerings (collectively, the "Service"). We want the Service to be usable by as many people as reasonably practicable, including people who use assistive technology such as screen readers, screen magnifiers, voice-input software, switch devices, and keyboard-only navigation.

We are working toward, and aim to conform to, the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium (W3C). We treat WCAG 2.2 AA as our target reference standard and as a continuous, iterative engineering goal — not a fixed end state, and not a present claim of full conformance. This Statement describes where we are today, how we test, what we know is not yet there, and how to reach us.

This Statement is published in good faith and updated as the Service evolves. It is not a contractual warranty, representation, guarantee, certification, or service-level commitment, and it does not modify, expand, or narrow any agreement between you and Recovea. See Section 11 (No warranty; relationship to your agreement).

2. Scope of this Statement

2.1 What this Statement covers

This Statement applies to the web-based interfaces that Recovea controls and that are generally used to evaluate, purchase, configure, and operate the Service, namely:

  • the public marketing and informational pages at recovea.ai;
  • the customer console / dashboard (the authenticated web application), including the sign-in and email-verification-code flow, account and billing settings, and the spend-control and reporting surfaces; and
  • the developer and legal documentation pages we publish under our own domains.

We design these surfaces to be perceivable, operable, understandable, and robust within the meaning of WCAG 2.2.

2.2 What this Statement does not cover

Accessibility conformance is assessed against human-facing user interfaces. This Statement therefore does not cover, and we make no conformance representation about:

  • Programmatic and machine interfaces that have no human user interface — including our HTTP API endpoints (for example, the OpenAI-compatible and Anthropic-compatible request paths at api.recovea.ai), command-line tooling (such as recoveactl), software development kits, the open ledger / verifier file formats, and webhooks. These are consumed by software, not assistive technology, and accessibility guidelines do not meaningfully apply to them.
  • Content, outputs, and responses generated by third-party model providers (for example, OpenAI, Anthropic, or OpenRouter). Recovea is a neutral, in-path conduit that proxies the Customer's own traffic on the Customer's own provider keys; Recovea does not author, control, or guarantee the form, structure, or accessibility of third-party model output.
  • Customer-controlled and Authorized-User-controlled configurations and content — including data, prompts, dashboards, labels, exports, or integrations that a Customer or its Authorized Users create, name, arrange, or supply.
  • Downloadable artifacts in their consuming application (for example, a CSV, JSON, or ledger export opened in a third-party spreadsheet or editor), beyond providing the data in a documented, machine-readable, and re-derivable form.
  • Legacy, beta, experimental, preview, or internal-only features that are not part of the generally available production interfaces, which may not yet meet our target standard and are excluded until promoted to general availability.

2.3 Third-party user-interface components

Some user-interface components inside our surfaces are provided by third parties and are rendered or hosted by them, not built by Recovea. Most notably:

  • Payment and billing UI is provided by our payment processor (Stripe) as an embedded component — the Stripe Elements PaymentElement card form, rendered by Stripe inside our own upgrade and billing pages. We do not redirect to a Stripe-hosted checkout page.
  • Identity, sign-in, and consent prompts, cookie/consent banners, and certain embedded widgets may be supplied by third-party vendors.

We select reputable vendors that themselves publish accessibility commitments and conformance documentation, and we configure these components to be as accessible as the vendor permits. However, the underlying accessibility of a third-party component is determined by that vendor, and we do not control its markup, focus behavior, labeling, or remediation timeline. Where a third-party component does not meet our target standard, we will look for a reasonable accessible alternative path (for example, an alternate way to provide required information) and will list any known material limitation in Section 6 as we become aware of it.

3. Target standard and measure

  • Standard: WCAG 2.2, Level A and Level AA success criteria.
  • Measure / conformance posture: "aims to conform / working toward." We do not state that the Service is "compliant," "certified," "fully conformant," or "accessible to all users." Conformance is partial and continuously improving, and may vary by page, flow, component, browser, operating system, and assistive-technology combination.
  • Companion standards we track: We monitor the U.S. Section 508 framework, the ADA Title III web-access landscape, and EN 301 549 as informative references for our U.S. business customers, without representing conformance to any of them.

4. Recovea-specific accessibility design measures

We have designed the following high-traffic, business-critical flows with assistive-technology and keyboard use in mind, and we work to keep them operable as the Service evolves.

4.1 Sign-in and email-verification-code flow

Because account access is gateway-critical, we have designed the sign-in and email-verification ("email code") flow to be operable by screen readers and by keyboard alone, and we work to keep it so. Measures we aim to provide and maintain include:

  • a logical, predictable focus order and a visible keyboard focus indicator throughout the flow;
  • programmatically associated labels and instructions for the email field and the one-time verification-code field, so assistive technology announces what each input is for;
  • accessible error, status, and "code sent" / "code expired" / "code resent" messaging announced to assistive technology (for example, via appropriate live-region or status semantics) rather than conveyed by color or position alone;
  • the ability to complete sign-in, request a new code, and submit a code without a pointing device and without a strict time limit that cannot be extended or restarted; and
  • support for browser and assistive-technology autofill / paste of the verification code where the user's tools provide it.

We treat regressions in this flow as high-priority accessibility defects.

4.2 Console, spend-control, and reporting surfaces

For the authenticated console — including the spend-control surface (budget caps, alerts, and kill-switch controls) and reporting/analytics views — we work toward keyboard operability, programmatic names/roles/values for interactive controls, non-color-dependent status indicators (for important state such as budget thresholds and alerts), text alternatives for meaningful non-text content, and reflow/resize support so content remains usable at increased zoom and reduced viewport widths. Complex data visualizations are paired with, or backed by, accessible tabular or exportable data wherever practicable.

4.3 General measures

Across our surfaces we aim to provide semantic structure and headings, descriptive page titles and link text, sufficient text contrast, visible focus states, skip-to-content affordances, form labels and error identification, captions or transcripts for substantive prerecorded media we publish, and respect for user preferences such as reduced motion where supported.

5. How we test

We use a combination of automated and manual methods. We describe only what we actually do today; we do not claim audits, certifications, or artifacts that do not yet exist.

  • Automated checks: Automated accessibility tooling integrated into our development workflow flags common machine-detectable issues (for example, missing form labels, insufficient contrast, missing alternative text, and certain ARIA and structure errors) during the build of customer-facing surfaces.
  • Manual keyboard testing: We perform keyboard-only operability checks of core flows — prioritizing the sign-in / email-code flow, account and billing settings, and the primary spend-control and reporting paths.
  • Manual screen-reader spot-checks: We perform periodic screen-reader spot-checks of core flows using commonly available screen readers and browsers.
  • Cadence: We run automated checks on an ongoing basis as part of our development process, and perform manual keyboard and screen-reader spot-checks of the core flows on a recurring basis and ahead of significant changes to those flows. Cadence is best-effort and may vary with engineering capacity; nothing here is a committed schedule.

Independent audit and VPAT — none exists today. No independent third-party accessibility audit has been completed, and no Voluntary Product Accessibility Template (VPAT) / Accessibility Conformance Report has been published. We may, in our discretion, commission such an audit or report in the future, but we make no commitment to do so or to any timeline. We will not represent that an independent audit has occurred, or publish a VPAT, until one has actually been completed; any future VPAT will state the standard, scope, evaluation methods, and date as of its issuance. Please do not infer the existence of an audit or VPAT from this Statement.

6. Known limitations (known to us)

Despite our efforts, some parts of the Service may not yet fully meet WCAG 2.2 AA. We disclose limitations that we are currently aware of, in the interest of candor; this list is not exhaustive, reflects our knowledge as of the "Last updated" date, and changes as we remediate issues and discover new ones:

  • Third-party payment, identity, and consent components (for example, the embedded Stripe Elements card form and any third-party sign-in or consent prompts) are governed by the vendor's own accessibility implementation, which we do not control and which may not fully meet our target standard (see Section 2.3).
  • Complex data visualizations and dense reporting tables may not be fully optimized for every screen reader and may rely on accompanying tabular/exportable data as the accessible equivalent.
  • Some interactive and dynamically updated states may not announce optimally in every assistive-technology / browser combination.
  • PDF, CSV, JSON, and ledger exports are provided as documented, machine-readable data and may not carry full document-tagging/accessibility metadata in every consuming application.
  • Beta, preview, experimental, and recently shipped features may temporarily lag the target standard until remediated.
  • Variability across platforms: behavior may differ across operating systems, browser versions, and assistive-technology versions; we test against commonly available combinations and cannot test every permutation.

We prioritize remediation based on user impact, frequency of use, and severity, with login and billing-critical flows treated as highest priority.

This good-faith disclosure of known limitations is not an admission that the Service fails to comply with any law, regulation, or standard, and may not be used as such.

7. Need help, or found a barrier? Contact us / feedback

We welcome your feedback, and we want to know if you encounter an accessibility barrier or need information, a feature, or a transaction in an alternative accessible format or by an alternative means.

  • Email: accessibility@recovea.ai.
  • What to include (so we can help quickly): the page or URL, the flow or feature, what you were trying to do, the barrier you hit, and the browser, operating system, and assistive technology (with versions) you were using. Please do not include passwords, API keys, or sensitive personal data. Information you submit is handled under our Privacy Notice.

Alternative-format / accommodation requests. If you cannot complete a task because of an accessibility barrier, contact us at the address above and we will work in good faith to provide the needed information, support, or a reasonable alternative means of access. We aim to respond promptly to accessibility requests. This is a good-faith statement of intent only; it is not a guaranteed response time or service level, and nothing in this Section starts or runs any response clock (see Section 11).

We do not retaliate against anyone for raising an accessibility concern in good faith.

8. Enforcement, complaints, and dispute resolution

We prefer to resolve accessibility concerns directly and informally — please contact us first using Section 7, which is the fastest path to a fix.

  • For Recovea customers and Authorized Users: any formal dispute arising out of or relating to the Service (including this Statement) is governed by the dispute-resolution, arbitration, class-action-waiver, governing-law, and venue provisions of the agreement between you and Recovea (the click-through Terms of Service / Master Services Agreement, as applicable). This Statement does not create a separate or independent cause of action, remedy, warranty, or service-level entitlement.
  • For members of the public who are not parties to a Recovea agreement: nothing in this Statement waives, and we do not ask you to waive, any non-waivable statutory accessibility right. For non-parties, this Statement is informational only and confers no rights; any statutory accessibility right is governed by applicable law. Public, non-party complainants are not subject to any arbitration agreement by reason of this Statement.

9. Governing law

This Statement, and any non-contractual matter arising from it, is governed by the laws of the State of Delaware, excluding its conflict-of-laws rules. Recovea, Inc. is a Delaware corporation. The Service is offered from and hosted in the United States and is intended for business customers; references to non-U.S. standards in this Statement are informational only.

10. Related policies and cross-references

This Statement should be read together with, and is subject to, our other published terms and policies, including our Terms of Service / Master Services Agreement, Privacy Notice, Data Processing Addendum, Security Statement, and Acceptable Use Policy. In the event of any conflict between this Statement and those agreements regarding warranties, disclaimers, limitations of liability, indemnification, or dispute resolution, those agreements control. Your use of the Service is also subject to those agreements, which include conspicuous "AS IS / AS AVAILABLE" disclaimers and limitations of liability.

11. No warranty; relationship to your agreement (conspicuous disclaimer)

THIS ACCESSIBILITY STATEMENT IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. IT IS NOT A CONTRACT, WARRANTY, REPRESENTATION, GUARANTEE, CERTIFICATION, OR SERVICE-LEVEL COMMITMENT, AND IT CREATES NO LEGALLY ENFORCEABLE OBLIGATION, RIGHT, OR REMEDY.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE SERVICE IS PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS, AND RECOVEA DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT, AND ANY WARRANTY THAT THE SERVICE OR ANY INTERFACE WILL BE FULLY ACCESSIBLE, UNINTERRUPTED, ERROR-FREE, OR CONFORMANT TO ANY PARTICULAR ACCESSIBILITY STANDARD. STATEMENTS THAT WE "AIM TO," "WORK TOWARD," OR "ARE WORKING TOWARD" CONFORMANCE ARE STATEMENTS OF PRESENT INTENT AND EFFORT, NOT GUARANTEES OF RESULT.

NOTHING IN THIS STATEMENT EXPANDS, NARROWS, OR OTHERWISE MODIFIES THE WARRANTIES, DISCLAIMERS, LIMITATIONS AND CAPS ON LIABILITY, INDEMNITIES, OR DISPUTE-RESOLUTION TERMS SET OUT IN THE TERMS OF SERVICE / MASTER SERVICES AGREEMENT AND OTHER APPLICABLE AGREEMENTS, EACH OF WHICH CONTINUES TO APPLY IN FULL. NOTHING IN THIS STATEMENT WAIVES ANY NON-WAIVABLE RIGHT YOU MAY HAVE UNDER APPLICABLE LAW.

12. Ownership, review, and changes to this Statement

  • Owner: Recovea's accessibility efforts and this Statement are owned and maintained by Recovea's head of product/engineering, who serves as the responsible, accountable owner and the point of escalation for accessibility. Contact: accessibility@recovea.ai.
  • Review: We review this Statement periodically, and additionally upon material changes to the Service, our testing practices, or our target standard, or the completion of any future independent audit or VPAT.
  • Changes: We may update this Statement at any time by posting a revised version with a new "Last updated" date. Material changes take effect when posted. The current version is the one published at our then-current legal/accessibility URL.

Recovea is a bootstrap-funded U.S. company; nothing in this Statement concerns investment or securities. "Recovea" is claimed as a common-law mark (™/℠) and is not registered unless and until a registration issues.