Retest of the digital accessibility audit of wcagtoolkit.com

Summary

wcagtoolkit.com is our own website. It is where we explain and sell the WCAG Radar, so we had it audited in August 2026 against WCAG 2.2, levels A and AA. The audit produced 23 findings.

We retested all 23 of them in August 2026. None of them are still open.

We publish this report because we ask the same of the organisations we audit. A retest covers the findings from the earlier audit and is not a second full evaluation of every success criterion. The pages we looked at are listed under Sample, so you can check the result yourself.

- Passed
- Failed
55 Total
- passed
Impact
Minor: 0 Medium: 0 Serious: 0
Type
Content: 0 Technical: 0
Score per principle (passed)
Perceivable - of 20
Operable - of 20
Understandable - of 13
Robust - of 2
Failed success criteria:
About this audit
Evaluated by
Proper Access
Commissioned by
Proper Access
Report date
August 22, 2026
Standard
WCAG 2.2
Methodology
WCAG-EM

Scope of the audit

  • All findings from the audit of wcagtoolkit.com of August 2026
  • The pages and the WCAG Radar tool listed under Sample

Out of scope:

  • Success criteria that were rated as sufficient in the audit of August 2026 and were not retested
  • Content that comes from third parties

Accessibility support baseline

  • Mozilla Firefox, version 152
  • Google Chrome, version 150
  • Apple Safari, version 18
  • NVDA screen reader in combination with Firefox
  • VoiceOver screen reader in combination with Safari
  • Other common browsers and assistive technologies

Technologies of the website

  • HTML
  • CSS
  • JavaScript
  • DOM
  • SVG
  • WAI-ARIA

Issues found

Filter findings by:
Impact:
Type:
About this audit

Purpose of This Report

This evaluation provides an overview of the extent to which the tool currently complies with WCAG 2.2, levels A and AA. The Web Content Accessibility Guidelines (WCAG) are international guidelines for web content accessibility. These guidelines are divided into four principles: Perceivable, Operable, Understandable, and Robust, each with specific measurable success criteria.

Testing Process

This evaluation was conducted following the WCAG-EM reporting methodology. The following process was used:

  • Determining what is in and out of scope
  • Identifying the technologies in use
  • Compiling a sample
  • Evaluating the sample
  • Documenting identified issues

The evaluation covers all requirements from the European accessibility standard EN 301 549 (WCAG 2.2).

The majority of the evaluation is a manual process. However, some criteria are supported using automated tools, such as axe-core and Chrome Developer Tools.

Fine Print

Since the evaluation is based on a sample, some issues may go unnoticed and could be assessed differently in subsequent evaluations. The sample is representative of all content on the tested domain. The evaluation provides a snapshot; when implementing improvements, new accessibility issues may arise.

The assessment of each criterion is based on a falsification approach: “compliant” means that we found no reasons to assess it as “non-compliant.”

For each issue, we provide up to three examples. The same issue may appear in multiple locations. Use this report as a blueprint to check all parts of the website.

How does this report work?

Viewing and filtering findings

All accessibility issues we found are listed under Issues found. You can filter the findings by:

  • Impact (Serious, Medium, Minor, Advice) — how severe is the problem for the user?
  • Type (Content, Technical) — does the content or the code need to change?
  • Status (Open, Resolved) — which problems have already been fixed?

Tracking progress

You can track your progress in two ways:

  • CSV export — export all findings as a CSV file and load it into an (online) spreadsheet to collaborate with your team.
  • Jira export — export all findings as a Jira-compatible CSV file. Import it via Jira > Issues > Import issues from CSV. Findings are created as bugs with a priority based on impact.
  • Track in the browser — enable this option to keep track per finding of whether it has been resolved. Your progress is stored in your browser. No one else can see your result. Note: the progress is tied to your browser. If you use a different browser or device, the count starts over.
  • Action plan — download a prioritised action plan to resolve the issues step by step. This is available for audits from March 2026 onwards.

Sharing a link to a specific finding

A link icon appears at each finding when you hover over it. Click this icon to copy the direct link to that finding. You can paste this link into an email or chat message, for example to ask Proper Access a question about a specific point.