Product and scope
What the report covers, the version evaluated and the date of the evaluation.
- intramedial.com, the documentation and the dashboard, as in the statement
- The date and the version evaluated
- Anything excluded, and why
Coming soon
This page will publish a conformance report for intramedial.com, the documentation and the dashboard: each WCAG 2.2 success criterion, how we meet it, and where we do not yet. It is not written yet. Our accessibility statement, and the way to tell us about a barrier, are available today.
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
The report will follow the usual structure of an accessibility conformance report, so a procurement team can read it like any other.
This page is planned. Below is its structure: each section, what it is for and what it will contain. Nothing here is sample content, and nothing is shown as available that is not.
What the report covers, the version evaluated and the date of the evaluation.
How the report is intended to be produced and kept current.
Each criterion is tested against the scope, with the methods stated in the report.
Each result is entered in the criteria table with its conformance level and remarks.
The statement sets out our target, what we do and the gaps we know about. Barriers can be reported now.
Join the waitlist and we will tell you when our accessibility conformance report is published on this page.
That is our target. We have not yet had an independent accessibility audit, and the statement lists the gaps we know about.
The format is not decided. VPAT is the Information Technology Industry Council's template for accessibility conformance reports, with editions for WCAG, Section 508, EN 301 549 and all three.
No report exists yet. The statement is available today, and you can send accessibility questions to support@intramedial.com.

The standards the report evaluates against. WCAG 2.2 level AA is our stated target. Whether the report also covers other standards is to be decided.
The methods, the tools and assistive technologies used, and who carried out the evaluation. We have not yet had an independent accessibility audit.
One row per success criterion, with a conformance level and remarks. The levels will use the terms of the VPAT format: Supports, Partially supports, Does not support, Not applicable.
What does not yet conform, and what we are doing about it. The statement names three areas today:
How to tell us about a barrier. Write to support@intramedial.com with the page, what you were trying to do and the assistive technology you use. We answer within one business day.
The report appears on this page with its date and the version evaluated.
When the site changes in a way that affects a result, the report is revised and dated again.
If you need information in another format, ask and we will provide it.
Want product news or security notices as well? All newsletters →
Join the waitlist on this page. You confirm once by email, and we tell you when the report is published.
The planned request page.
Sources, as of October 2026W3C: Web Content Accessibility Guidelines 2.2 ↗ITI: VPAT, version 2.5Rev ↗