AI Use & Accessibility

Last Updated: August 24, 2026

Part 1 — How InstaGovOps uses AI

InstaGovOps uses artificial intelligence in two distinct ways. They behave differently and it matters which one you are relying on.

1.1 Generative AI (writes text)

We use Anthropic's Claude models to draft proposal content, summarize solicitations, extract requirements from RFP documents, and describe why an opportunity may fit your company. This content is generated by a language model. It is a starting point, not a finished submission.

Generative AI can state things that are incorrect, outdated, or fabricated — including certifications, past performance, personnel, pricing, and compliance claims your company does not actually hold. Every generated document must be read and corrected by a person before it goes anywhere near a contracting officer.

1.2 Embedding-based matching (scores relevance)

We use Voyage AI embeddings to measure how semantically close an opportunity is to your company profile. This produces part of the match score you see on each opportunity. It does not write anything and does not read your documents. Match scores are a prioritization aid — they are not a determination that you are eligible for, or should bid on, a given opportunity.

1.3 What we do not do

  • We never submit anything to a government portal without a person at your organization approving the document and starting the filing. Automated Grants.gov filing, an optional add-on, transmits only what your Authorized Organization Representative has certified.
  • We do not use your proposal content, company profile, or uploaded documents to train AI models.
  • We do not represent AI-generated content as human-authored anywhere in the product.

1.4 Your disclosure obligations

Some agencies, programs, and solicitations require offerors to disclose the use of generative AI in preparing a response, and a few restrict it outright. Those rules vary by agency and change often. Reviewing the solicitation for AI-use terms and making any required disclosure is your responsibility as the offeror — InstaGovOps cannot make that determination for you and does not attach a disclosure to your documents automatically.

1.5 Human review is required, not suggested

Documents produced by our AI tools are saved in a pending review state and cannot be marked submitted until a person explicitly approves them. This gate exists because you — not InstaGovOps — sign and certify what goes to the government.

1.6 Administrative controls

AI features can be switched off per capability and per account by a platform administrator, and there is a master switch that disables all AI activity at once. If you need AI features disabled for your organization, contact support.

Part 2 — Accessibility statement

2.1 Our target

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, which is the standard referenced by Section 508 of the Rehabilitation Act and commonly applied under the Americans with Disabilities Act.

2.2 Current status — partially conformant

InstaGovOps is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means some parts of the platform do not yet fully meet the standard. We are publishing the known gaps rather than claiming a level of conformance we have not verified.

2.3 What currently works

  • Pages can be zoomed and text resized without loss of content.
  • A “skip to main content” link is available to keyboard users.
  • Pages declare a language and expose a single main landmark.
  • Images carry text alternatives; form fields have programmatic labels.
  • The interface works at mobile widths without horizontal scrolling.

2.4 Known gaps we are working on

  • Color contrast. Some text and control combinations — notably gold-on-light section labels and the primary button style — fall below the 4.5:1 ratio required at Level AA.
  • Touch target size. A number of controls are smaller than the 44 × 44 CSS-pixel target recommended for touch input.
  • Heading semantics. Some card and panel titles are styled as headings without heading markup, which affects screen-reader navigation.
  • Complex data views. Opportunity tables and the browser-agent screens have not been fully audited for keyboard and screen-reader use.

2.5 Assessment method

This statement is based on internal self-evaluation using automated checks against live pages, including programmatic contrast, landmark, heading, label, and target size measurement. It has not been evaluated by an independent third party, and no VPAT has been produced.

2.6 Feedback and requests

If you encounter an accessibility barrier on this platform, or need information provided in an alternative format, contact us at support@instagovops.com. Tell us the page and what you were trying to do. We aim to respond within five business days.

If a barrier prevents you from meeting a solicitation deadline, say so in your message and we will prioritize it.

2.7 Compatibility

InstaGovOps is built for current versions of Chrome, Edge, Firefox, and Safari. Older browsers may not support the accessibility features described above.

Questions

Contact support@instagovops.com for anything on this page. See also our Terms of Service, Acceptable Use Policy, and Privacy Policy.