Accessibility Statement

We sell accessibility testing, so skipping our own statement would be a poor look. WCAGsafe is committed to making wcagsafe.com usable by everyone, including people who browse with screen readers, keyboards, magnification, or other assistive technology. This page states where we actually stand — including the parts we have not fixed.

Conformance status

wcagsafe.com is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means most of the site meets the standard, but some content does not. The known exceptions are listed in the next section.

We are not claiming full conformance, and we would rather say that than publish a statement that overstates it. WCAG 2.1 AA is also the standard referenced by EN 301 549 for the European Accessibility Act, so the same assessment covers both.

Non-accessible content

The content below does not fully conform to WCAG 2.1 AA. We have grouped it by why it is still there.

Deliberate exceptions we are keeping

• Demonstrations of failing contrast. Some pages — including ADA Compliance for Websites and our color contrast guide — contain sample text and color swatches set at deliberately low contrast, because the point of the example is to show what a failure looks like. Every sample is described in the surrounding text, so nothing depends on seeing the swatch. Our own scanner flags these, and that is expected.
• Pass and fail markers in code examples. The red and green “fails / passes” labels in our tutorials, and the risk badges on our industry pages, use our semantic color palette. Some of those reds and greens fall below the 4.5:1 minimum for body text. Each one is paired with a ✗ or ✓ character, so the meaning never depends on color alone, but the contrast ratio itself is still short.

Gaps we intend to close

• Generated PDFs are not tagged. The reports and audit certificates we generate are untagged PDFs: they carry no structure tree, so a screen reader cannot reliably follow their reading order. Every finding in a report is also available as an HTML page in your dashboard, which is the route we recommend today. Tagging the PDF output is on our list.
• Embedded third-party interfaces. Sign-in, sign-up, and checkout are rendered by our identity and payment providers. We pick vendors that take accessibility seriously and we report problems upstream, but we do not control that markup and cannot fix it ourselves.

How we assessed this site

This statement is based on a self-evaluation carried out on July 11, 2026 and reviewed on August 24, 2026. We tested wcagsafe.com with our own scanning engine, which runs the open-source axe-core rule set against each page in a real browser, and we confirmed individual findings by running axe directly against the live pages to read the exact color pairs and contrast ratios.

That pass found real failures and we fixed them: low-contrast text on colored backgrounds, muted gray body copy below 4.5:1, faint fine print, and inline links that were distinguished by color alone and are now underlined. The pricing cards were restyled to raise the contrast of their headers, badges, and buttons.

Automated testing catches a meaningful share of WCAG issues, not all of them. We have not commissioned an independent third-party audit or formal assistive-technology user testing of this site, and we would rather say so than let the word “audit” imply more than it is.

The WCAGsafe browser extension

Our Chrome extension is covered by this statement too. Its panel is operable by keyboard, and every result it reports is available as text rather than color alone. If you hit a barrier in the extension specifically, mention that in your message — it ships separately from the website.

Feedback and contact information

If you find an accessibility barrier on wcagsafe.com, or you need something from this site in a different format, tell us at support@wcagsafe.com.

It helps if you include the page address, what you were trying to do, and the browser or assistive technology you were using — but send it even if you only have one of those. We aim to reply within 5 business days, and we will tell you either when the fix is going out or why we have not been able to make it.

If we do not resolve it

If you contact us about a barrier and are not satisfied with our response, you can escalate. In the United States, complaints about website accessibility can be filed with the U.S. Department of Justice Civil Rights Division. In the European Union, each member state designates its own enforcement body under the European Accessibility Act. Nothing on this page limits any right you have under the ADA, the EAA, or any other law.

Preparation of this statement

This statement was prepared on August 24, 2026 using the structure of the official EU model accessibility statement: conformance status, non-accessible content, how and when the site was assessed, and how to give feedback. We review it whenever we make a substantial change to the site, and at least once a year.

You can build the same kind of statement for your own site with our free accessibility statement generator. It runs in your browser, needs no signup, and produces text you can paste straight into your site. This page is informational and is not legal advice.