barrierefreiheit.wikiCheck · Understand · Compare

Method

How the website check works

A test result is only worth as much as the method behind it. This page sets out what is tested, how it is tested and where the limits lie.

What is tested

The check fetches the public address you enter and evaluates the delivered HTML. The following is tested:

  • selected HTML accessibility rules with the axe testing engine, including labelling of images, labelling of form fields, names of links and buttons, the page title and the language of the document,
  • the page title of the checked page,
  • the language of the HTML document,
  • the main headings of the checked page.

Every finding names the rule, the impact, the affected CSS selector and an excerpt of the element that was found.

Illustration: A check report lists findings with different severities.
The check is exclusively read-only and blocks scripts of the checked page.

How it is tested

Sequence

  1. You enter the address and your e-mail address and confirm that you are responsible for the website.
  2. You receive a private confirmation link by e-mail. The link contains a random identifier and a random token, which is transmitted in the URL fragment and therefore appears neither in server log files nor in referrer information.
  3. The job is placed in a shared, private job store and processed by a dedicated checking process.
  4. You see the result on a private page. From there you can request an offer for the remediation directly.

Protection of the checked website

The check is exclusively read-only. Scripts of the checked page are blocked, all subresources are intercepted, and only the main document is loaded. This avoids loading or changing the checked website through the check.

Protection against misuse

Internal addresses and private network ranges are blocked for check targets, DNS resolution and redirects are checked, and the connection is pinned to the expected address. Every job has limits for length, scope, duration and repetitions. A job has to be confirmed within 48 hours, reports are deleted after 14 days.

Limits of the procedure

The check expressly does not test:

  • contrast and visible design,
  • operation with the keyboard,
  • screen reader output and semantic quality,
  • comprehensibility of content, language and alternative texts,
  • multi-step flows such as cart, checkout or booking,
  • the complete website: the single page you entered is tested,
  • whether accessibility law applies to your case.
No conformity proof. A result without findings does not mean that your website is accessible. It means that within the tested rule set, nothing was found on the tested page.

What a good workflow looks like

The technical check is the entry point, not the end. Reliable results also require an audit with keyboard and screen reader, a review of the central paths such as search, cart and checkout, an assessment of the content, and a re-check after implementation. More on the service types

How your data is handled

  • Your e-mail address is used for the confirmation link and for delivering the result.
  • It is not added to a marketing list and is not used for newsletters.
  • The report is stored privately, not published and not indexed.
  • Unconfirmed requests expire after 48 hours, reports after 14 days.
  • Processing takes place for your requested check and, only on explicit request, for an individual offer.

Details in the privacy policy. You can request deletion at any time.