Accessibility statement
Conformly is committed to making this website and the Conformly product usable by everyone, including people who use screen readers, keyboard-only navigation, screen magnification or speech input. This statement sets out where we stand — including the barriers we know about and have not fixed yet.
Conformance status
The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. Conformly is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that some parts of the content do not fully conform to the standard — those parts are listed below.
This assessment covers getconformly.com and the Conformly web application, and was carried out by our own team in August 2026 against WCAG 2.1 Level AA. It also informs our position under Directive (EU) 2019/882 (the European Accessibility Act), which has applied since 28 June 2025, and the harmonised standard EN 301 549.
What we have measured and fixed
Keyboard operable throughout
Every interactive control — including the compliance graph's system and vendor nodes — is reachable and operable with a keyboard alone, and shows a visible focus indicator when you get there.
Skip links on every surface
The marketing site, the product workspace and the sign-in pages each start with a 'Skip to content' link, so keyboard and screen-reader users can bypass the header and sidebar.
Text contrast at 4.5:1 or better
Body text and secondary text in the product workspace and on the sign-in pages meet the 4.5:1 ratio required by WCAG 1.4.3, in both the light and the dark theme.
Form fields you can see and name
In the product workspace, on the sign-in pages and in the vendor assessment, input, textarea, select and checkbox borders meet the 3:1 non-text contrast ratio (WCAG 1.4.11), and every field is programmatically bound to its label.
Named controls
Icon-only buttons — delete, copy, close — carry an accessible name, so a screen reader announces what they do rather than just 'button'.
Landmarks and headings
Each page exposes a main landmark, distinct navigation landmarks, and a single top-level heading that describes the page.
Known non-conformances
We would rather tell you about a barrier than have you discover it. The following issues are known to us and are not yet fixed.
1.4.3 Contrast (Minimum) — Level AA
Where: Secondary and caption text on parts of the public content library: the glossary, the guides and how-it-works hubs, the EU AI Act article/role pages, the AI vendor and comparison pages, the enforcement tracker, and the free tools (penalty calculator, deadline timeline, Article 50 readiness checker, watermark checker).
Some captions on these pages use a light slate grey that measures about 2.56:1 against white, below the 4.5:1 required. The text is supporting detail, never the only copy carrying a point, but it is harder to read than it should be.
Remediation in progress. Target: Q4 2026.
1.4.11 Non-text Contrast — Level AA
Where: Form fields on the public marketing site: the contact and lead forms, the report request form, the penalty calculator and the watermark checker.
These forms style their own field borders rather than using the shared design token we corrected, so their outlines measure about 1.48:1 against the white field — below the 3:1 required for a user interface component boundary. The fields are still labelled, keyboard operable and show a clear focus ring when selected.
Remediation in progress. Target: Q4 2026.
1.1.1 Non-text Content / 1.4.1 Use of Colour — Level A
Where: The compliance graph in the product workspace (/app/graph).
The graph is keyboard operable and every node has an accessible name, but risk class is still conveyed largely through colour, and there is no equivalent data table for the graph as a whole. The same information is available in list form elsewhere in the product, but not as a direct alternative on that screen.
A table view of the same data is planned. Target: Q4 2026.
PDF/UA tagging — outside WCAG, required by EN 301 549 clause 10
Where: Generated documents: the Annex IV technical documentation export, the auditor report, and the Statement of Applicability.
Our PDF exports are not yet tagged for accessibility — headings, reading order and table structure are not exposed to assistive technology. The same content is available as accessible HTML inside the product.
Under investigation with our PDF renderer. No committed date yet.
Independent audit and VPAT
Where: Site-wide.
Our conformance claim is based on our own internal audit against WCAG 2.1 Level AA, not on a third-party assessment, and we do not yet publish a VPAT / EN 301 549 accessibility conformance report.
We will provide the current internal audit findings on request to any customer or prospective customer who asks.
Third-party content
Where: Embedded analytics and payment provider flows.
Checkout is handled by our payment provider on their own pages. We do not control the accessibility of that content and have not audited it.
Not under our control. We will raise reported issues with the provider.
Give us feedback, or report a barrier
If you hit an accessibility barrier on this site or in the product — including anything not listed above — please tell us. Describe the page or screen, what you were trying to do, and the assistive technology and browser you were using, if you can.
Accessibility contact
We aim to acknowledge accessibility reports within 5 working days and to tell you what we intend to do about the issue, and when. If you are not satisfied with our response, you can escalate to the enforcement body responsible for the European Accessibility Act in your EU Member State.
You can also reach us through our contact page.
For procurement and vendor reviews
We do not yet publish a VPAT or an EN 301 549 accessibility conformance report. If your procurement process requires one, email support@getconformly.com and we will share our current internal audit findings — including everything listed on this page — and work with you on the format you need.
How we assessed this
- Method: internal self-evaluation against WCAG 2.1 Level AA — measured contrast ratios, keyboard-only walkthroughs of the sign-in, marketing and workspace flows, and inspection of the rendered accessibility tree.
- Scope: getconformly.com and the Conformly web application. Generated PDF exports were assessed separately and are listed as a known non-conformance above.
- Last reviewed: 9 August 2026.
- Next scheduled review: 9 February 2027, and after any significant change to the product.