Accessibility statement

Our commitment

Revion Solutions, Incorporated is committed to digital accessibility. GuardGrid exists because we think the web should work for everyone who tries to use it, and because organizations deserve honest measurement rather than a badge.

That commitment has an obvious implication: we hold guardgrid.ai to the same standard we measure for our customers. It would be difficult to argue we take this seriously if we did not test our own site continuously, publish what we find, and say plainly where we fall short.

Accessibility is treated here as an ongoing operational practice rather than a project with an end date. Every time we ship a page or a component, it is scanned again.

Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for making web content more accessible to people with disabilities. There are three levels of conformance: A, AA, and AAA.

guardgrid.ai aims to conform to WCAG 2.2 level AA. We are working toward that target and the site substantially conforms where we have verified it. We are not claiming full conformance, and we are not certified by anyone.

We use that wording deliberately. A large site changes continuously, automated testing cannot evaluate every success criterion, and we have not completed a formal third-party audit of guardgrid.ai. Any organization telling you its site is permanently and completely conformant is describing something that is very difficult to sustain in practice. What we can say honestly is that we test everything we publish, we act on what we find, and we will tell you where the gaps are.

We target WCAG 2.2 rather than 2.1 because 2.2 is backward compatible: meeting 2.2 level AA also satisfies 2.1 and 2.0 at the same level. That matters for readers whose own obligations are framed around WCAG 2.1 AA.

How we test this site

guardgrid.ai is monitored continuously with the GuardGrid platform. Every page on the property is crawled and tested against the WCAG success criteria on a schedule, not sampled, and findings identify the specific failing element and the criterion it breaks. New pages enter that cycle automatically as they are published.

Automated scanning is necessary and not sufficient, and we would rather be direct about that than imply otherwise. Industry consensus puts automated detection at roughly a third to 40 percent of WCAG success criteria, and the W3C states plainly in its guidance on evaluating accessibility that "no tool alone can determine if a site meets accessibility standards. Knowledgeable human evaluation is required to determine if a site is accessible."

So automated monitoring is paired with manual review. People on our team check the things machines cannot judge: whether alternative text is meaningful rather than merely present, whether reading order makes sense, whether an error message explains how to fix the problem, and whether each page and interactive component can be operated using a keyboard alone.

Scope

This statement applies to the guardgrid.ai marketing website, including its product pages, comparison and solution pages, blog, and legal pages.

The GuardGrid application, which customers reach through a separate login, is a different product surface with its own release cycle and is not covered by this statement.

Two components on this site are embedded from third parties and are not fully under our control: a scheduling widget on our demo booking page, and a bot-protection widget on our contact form. We selected both deliberately and we monitor them, but we cannot rewrite their internals. If either one blocks you, the alternative contact routes in the feedback section below will reach us just as reliably, and we will respond by whatever channel works for you.

Known limitations

A statement that lists only strengths is not worth much. Here is what we know we have not resolved or verified:

• Third-party embedded components. The scheduling and bot-protection widgets described above are outside our direct control. Alternatives are provided.
• Formal assistive technology testing is incomplete. We have not completed structured testing across every combination of browser, operating system, and assistive technology, so we are not claiming verified compatibility with all of them.
• No third-party audit. Our assessment is a self-evaluation. It has not been independently audited, and we will say so until that changes.
• The automated testing ceiling. Continuous scanning gives us broad, repeatable coverage of the criteria machines can evaluate. It does not cover the criteria that require human judgement, which is why manual review runs alongside it and why reports from real users matter to us.

If you find something not listed here, we would genuinely like to know. That is the fastest way this list gets shorter.

Technical specifications

Accessibility on guardgrid.ai relies on the following technologies working with your browser and any assistive technology you use:

• HTML
• CSS
• JavaScript
• WAI-ARIA

The site is a statically generated set of pages. It is built to work with current versions of major browsers and the assistive technologies that run on them, and core content and navigation remain usable when JavaScript is unavailable. As noted in the limitations above, we have not completed formal compatibility testing against every browser and assistive technology combination, so we are describing how the site is built rather than claiming verified support for each pairing.

Assessment approach

Revion Solutions, Incorporated assessed the accessibility of guardgrid.ai by self-evaluation, combining continuous automated testing of every page using the GuardGrid platform with manual review by our own team. This assessment has not been independently audited by a third party.

One point of clarification, since it is relevant to how this site is built and to what we sell: GuardGrid is not an accessibility overlay. We do not add a widget, script, or runtime layer to any website, including our own. We test the HTML that is actually served, because that is what a person using a screen reader receives and what an auditor examines. Accessibility here comes from the markup and content, not from a script layered over it.

This statement was last reviewed on August 7, 2026. We review it whenever the site changes materially, and at least annually.

Prepared using the structure recommended by the W3C Web Accessibility Initiative. You can learn more about writing accessibility statements from the W3C WAI guidance on developing an accessibility statement.