Select one or more tags, then press “Search Plugins”

Find Plugin with any / all of the selected criteria
Search Plugin

Barrierepruefung.de – Web Accessibility Checker Wordpress Plugin - Rating, Reviews, Demo & Download

Barrierepruefung Wordpress Plugin - Rating, Reviews, Demo & Download
No ratings yet
Free
Follow for free plugins, new theme releases and theme news

Plugin Description

The plugin connects your WordPress installation to an auditing service for digital
accessibility. From the admin area you can start a scan, review the open findings together with
a note on how to fix them, and output the text of your accessibility statement on a page via
shortcode or block.

Under Tools Accessibility the findings of the last scan are laid out as a work list: for
each rule the severity, the success criterion, the number of occurrences, what needs to be done
and which pages are affected. Expand a rule to see its individual occurrences — page, selector,
the measured values and the HTML snippet — so you can find the spot in WordPress. Below that,
the page quota of the current billing period. You fix things in WordPress; then you start the
next scan from the same place.

Screenshots of the occurrences stay on the service’s website and are reachable from the link to
the full report.

The statement is embedded server-side — so it is fully present without JavaScript and for
assistive technologies.

What the plugin does not do

It does not change your site and does not repair anything automatically. So-called
accessibility overlays do not remove barriers, regularly make things worse for people using
assistive technologies, and are not proof of conformance.

External services

This plugin calls an external service whose address you enter yourself during setup (default:
barrierepruefung.de).

What is transmitted:

  • the address of this site,
  • the API token you created,
  • the ID of your site within the service.

No content and no personal data of your visitors are transmitted. Transmission happens
when you start a scan, when you verify the domain, when the page Tools Accessibility is
opened (at most every five minutes, from the cache after that), when you expand a rule to see
its occurrences, or when the statement is retrieved (at most once an hour, likewise from the
cache after that).

Privacy policy of the service: https://barrierepruefung.de/datenschutz
Terms of service: https://barrierepruefung.de/agb

Shortcode

[barrierefreiheitserklaerung] outputs the text of your accessibility statement, rendered on

the server. The block “Accessibility statement” offers the same scope and the same embedding —
with the settings teil, stand and ueberschrift.

Example for the complete statement:

[barrierefreiheitserklaerung]

Example for the non-conformance section only, embedded one level deeper:

[barrierefreiheitserklaerung teil="maengel" ueberschrift="3"]

teil

Which excerpt of the statement is output.

  • komplett (default) — the complete statement.
  • maengel — the section on known barriers only.
  • kontakt — the section with the contact details for feedback only.

An unknown value returns the complete statement without an error message, exactly like
komplett — and so does the case where the requested section is not found in the statement
that was loaded.

ueberschrift

The level given to the topmost heading of the output (default 2). It is measured relative to
the topmost heading that actually occurs in the statement — not fixed to an h1 — so that the
text fits into the heading hierarchy of your page.

Values from 2 to 4 are allowed; smaller or larger values are clamped to that range without
an error message (1 therefore behaves like 2, 5 like 4). Headings further down inside
the statement are shifted along accordingly, but never beyond h6.

stand

ja (default) appends a paragraph with the version number and the date of the statement — but

only if the statement that was loaded brings a date with it. If it does not, the paragraph is
omitted even with stand="ja". Any other value suppresses the paragraph in every case.

sprache

Is accepted, but has no effect in this version — the language of the output follows solely the
language version stored in the service.

Screenshots

  1. Setup under <em>Tools → Accessibility</em>: the page explains where account, API token and site ID
come from before it asks for them.

    Setup under Tools → Accessibility: the page explains where account, API token and site ID
    come from before it asks for them.

  2. After connecting: the status of the site, the page quota of the current billing period, the
stored connection and the shortcode for the statement.

    After connecting: the status of the site, the page quota of the current billing period, the
    stored connection and the shortcode for the statement.

  3. After a scan: the open findings as a work list — severity, success criterion, number of
occurrences and the pages affected. Each rule can be expanded to its individual occurrences.

    After a scan: the open findings as a work list — severity, success criterion, number of
    occurrences and the pages affected. Each rule can be expanded to its individual occurrences.


Reviews & Comments