{"id":366379,"date":"2026-09-18T13:16:17","date_gmt":"2026-09-18T13:16:17","guid":{"rendered":"https:\/\/de.wordpress.org\/plugins\/barrierepruefung-de-web-accessibility-checker\/"},"modified":"2026-09-18T14:17:50","modified_gmt":"2026-09-18T14:17:50","slug":"barrierepruefung-de-web-accessibility-checker","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/barrierepruefung-de-web-accessibility-checker\/","author":20997413,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.6.4","stable_tag":"0.6.4","tested":"7.1.1","requires":"6.5","requires_php":"8.1","requires_plugins":null,"header_name":"Barrierepruefung.de \u2013 Web Accessibility Checker","header_author":"Lukas Bock","header_description":"Scans this site for accessibility barriers and embeds your accessibility statement via shortcode.","assets_banners_color":"f8f9f8","last_updated":"2026-09-18 14:17:50","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/github.com\/lukasboc\/barrierepruefung-wordpress","header_author_uri":"https:\/\/barrierepruefung.de","rating":0,"author_block_rating":0,"active_installs":0,"downloads":75,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.6.3":{"tag":"0.6.3","author":"lukasbo","date":"2026-09-18 13:16:10","revision":3702038},"0.6.4":{"tag":"0.6.4","author":"lukasbo","date":"2026-09-18 14:17:50","revision":3702126}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3702038,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3702038,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3702038,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3702038,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"barrierepruefung\/erklaerung":{"name":"barrierepruefung\/erklaerung","title":"Accessibility statement"}},"tagged_versions":["0.6.3","0.6.4"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3702038,"resolution":"1","location":"assets","locale":"","width":2464,"height":1808},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3702038,"resolution":"2","location":"assets","locale":"","width":2464,"height":2220},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3702038,"resolution":"3","location":"assets","locale":"","width":2464,"height":2908}},"screenshots":{"1":"Setup under Tools \u2192 Accessibility<\/em>: the page explains where account, API token and site ID\ncome from before it asks for them.","2":"After connecting: the status of the site, the page quota of the current billing period, the\nstored connection and the shortcode for the statement.","3":"After a scan: the open findings as a work list \u2014 severity, success criterion, number of\noccurrences and the pages affected. Each rule can be expanded to its individual occurrences."}},"plugin_section":[],"plugin_tags":[1953,244989,240916,35375,1956],"plugin_category":[34],"plugin_contributors":[281445],"plugin_business_model":[],"class_list":["post-366379","plugin","type-plugin","status-publish","hentry","plugin_tags-accessibility","plugin_tags-barrierefreiheit","plugin_tags-bfsg","plugin_tags-bitv","plugin_tags-wcag","plugin_category-accessibility","plugin_contributors-lukasbo","plugin_committers-lukasbo"],"banners":{"banner":"https:\/\/ps.w.org\/barrierepruefung-de-web-accessibility-checker\/assets\/banner-772x250.png?rev=3702038","banner_2x":"https:\/\/ps.w.org\/barrierepruefung-de-web-accessibility-checker\/assets\/banner-1544x500.png?rev=3702038","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/barrierepruefung-de-web-accessibility-checker\/assets\/icon-128x128.png?rev=3702038","icon_2x":"https:\/\/ps.w.org\/barrierepruefung-de-web-accessibility-checker\/assets\/icon-256x256.png?rev=3702038","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/barrierepruefung-de-web-accessibility-checker\/assets\/screenshot-1.png?rev=3702038","caption":"Setup under Tools \u2192 Accessibility<\/em>: the page explains where account, API token and site ID\ncome from before it asks for them."},{"src":"https:\/\/ps.w.org\/barrierepruefung-de-web-accessibility-checker\/assets\/screenshot-2.png?rev=3702038","caption":"After connecting: the status of the site, the page quota of the current billing period, the\nstored connection and the shortcode for the statement."},{"src":"https:\/\/ps.w.org\/barrierepruefung-de-web-accessibility-checker\/assets\/screenshot-3.png?rev=3702038","caption":"After a scan: the open findings as a work list \u2014 severity, success criterion, number of\noccurrences and the pages affected. Each rule can be expanded to its individual occurrences."}],"raw_content":"\n

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

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

Screenshots of the occurrences stay on the service's website and are reachable from the link to\nthe full report.<\/p>\n\n

The statement is embedded server-side<\/strong> \u2014 so it is fully present without JavaScript and for\nassistive technologies.<\/p>\n\n

What the plugin does not do<\/h4>\n\n

It does not change your site and does not repair anything automatically. So-called\naccessibility overlays do not remove barriers, regularly make things worse for people using\nassistive technologies, and are not proof of conformance.<\/p>\n\n

External services<\/h3>\n\n

This plugin calls an external service whose address you enter yourself during setup (default:\nbarrierepruefung.de).<\/p>\n\n

What is transmitted:<\/p>\n\n

    \n
  • the address of this site,<\/li>\n
  • the API token you created,<\/li>\n
  • the ID of your site within the service.<\/li>\n<\/ul>\n\n

    No<\/strong> content and no<\/strong> personal data of your visitors are transmitted. Transmission happens\nwhen you start a scan, when you verify the domain, when the page Tools \u2192 Accessibility<\/em> is\nopened (at most every five minutes, from the cache after that), when you expand a rule to see\nits occurrences, or when the statement is retrieved (at most once an hour, likewise from the\ncache after that).<\/p>\n\n

    Privacy policy of the service: https:\/\/barrierepruefung.de\/datenschutz\nTerms of service: https:\/\/barrierepruefung.de\/agb<\/p>\n\n

    Shortcode<\/h3>\n\n
    [barrierefreiheitserklaerung] outputs the text of your accessibility statement, rendered on\n<\/code><\/pre>\n\n
    the server. The block \u201cAccessibility statement\u201d offers the same scope and the same embedding \u2014\nwith the settings teil<\/code>, stand<\/code> and ueberschrift<\/code>.<\/p>\n\n
    Example for the complete statement:<\/p>\n\n
    [barrierefreiheitserklaerung]\n<\/code><\/pre>\n\n
    Example for the non-conformance section only, embedded one level deeper:<\/p>\n\n
    [barrierefreiheitserklaerung teil=\"maengel\" ueberschrift=\"3\"]\n<\/code><\/pre>\n\n
    teil<\/h4>\n\n
    Which excerpt of the statement is output.<\/p>\n\n
      \n
    • komplett<\/code> (default) \u2014 the complete statement.<\/li>\n
    • maengel<\/code> \u2014 the section on known barriers only.<\/li>\n
    • kontakt<\/code> \u2014 the section with the contact details for feedback only.<\/li>\n<\/ul>\n\n
      An unknown value returns the complete statement without an error message, exactly like\n    komplett \u2014 and so does the case where the requested section is not found in the statement\nthat was loaded.<\/p>\n\n
      ueberschrift<\/h4>\n\n
      The level given to the topmost heading of the output (default 2<\/code>). It is measured relative to\nthe topmost heading that actually occurs in the statement \u2014 not fixed to an h1 \u2014 so that the\ntext fits into the heading hierarchy of your page.<\/p>\n\n
      Values from 2<\/code> to 4<\/code> are allowed; smaller or larger values are clamped to that range without\nan error message (1<\/code> therefore behaves like 2<\/code>, 5<\/code> like 4<\/code>). Headings further down inside\nthe statement are shifted along accordingly, but never beyond h6.<\/p>\n\n
      stand<\/h4>\n\n
      ja (default) appends a paragraph with the version number and the date of the statement \u2014 but\n<\/code><\/pre>\n\n
      only if the statement that was loaded brings a date with it. If it does not, the paragraph is\nomitted even with stand=\"ja\"<\/code>. Any other value suppresses the paragraph in every case.<\/p>\n\n
      sprache<\/h4>\n\n
      Is accepted, but has no effect in this version \u2014 the language of the output follows solely the\nlanguage version stored in the service.<\/p>\n\n\n
        \n
      1. Install and activate the plugin. Open Tools \u2192 Accessibility<\/em> \u2014 the page explains every step\nbelow, including where each value comes from.<\/li>\n
      2. Create an account at barrierepruefung.de, or sign in if you already have one.<\/li>\n
      3. Add this site there, using exactly the address of this WordPress installation. If a different\naddress is stored, the domain cannot be verified in step 6.<\/li>\n
      4. Under Websites \u2192 [site] \u2192 Embedding<\/em>, section WordPress plugin and API<\/em>, choose Create\ntoken<\/em>. The API token and the site ID are shown once, in that place.<\/li>\n
      5. Enter both under Tools \u2192 Accessibility<\/em> and leave the service address as it is.<\/li>\n
      6. Verify the domain \u2014 the plugin serves the proof itself, you do not need DNS access.<\/li>\n
      7. Start a scan and insert the shortcode [barrierefreiheitserklaerung]<\/code> on a page.<\/li>\n<\/ol>\n\n\n
        \n
        Do I have to set a DNS record?<\/h3><\/dt>\n
        No. The plugin serves the proof itself, as a meta element and as a file under\n    \/.well-known\/a11y-site-verification.txt.<\/p><\/dd>\n
        I started a scan \u2014 where is the result?<\/h3><\/dt>\n
        A scan takes a few minutes. The page does not update on its own, because an automatic reload\nwould move the focus and interrupt screen reader users (WCAG 2.2.2). While a scan is running,\nTools \u2192 Accessibility<\/em> says so and offers \u201cCheck whether the scan has finished\u201d as its main\nbutton.<\/p><\/dd>\n
        What happens if the service is unreachable?<\/h3><\/dt>\n
        The last successfully loaded version of the statement continues to be delivered \u2014 with its\noriginal date. A statement that disappears from the site because of an outage would be a legal\nproblem for you.<\/p><\/dd>\n
        Which languages does the plugin come in?<\/h3><\/dt>\n
        English (source language) and German. The template for further translations ships with the\nplugin under languages\/barrierepruefung-de-web-accessibility-checker.pot<\/code>.<\/p><\/dd>\n
        I mistyped something while connecting \u2014 how do I get back?<\/h3><\/dt>\n
        Under Tools \u2192 Accessibility<\/em> the stored connection is shown together with a \u201cDisconnect\u201d\nbutton. The form then reappears and you can enter token, site ID and address again. The service\naddress can also be reset to its default value on its own there. Your account is not affected;\nthe token stays valid and is revoked in the account.<\/p><\/dd>\n
        What is left behind after uninstalling?<\/h3><\/dt>\n
        Nothing. Uninstalling removes all options and caches, including the token and the last loaded\nversion of the statement \u2014 in a network, for every subsite individually.<\/p><\/dd>\n
        Does the automated scan replace an expert audit?<\/h3><\/dt>\n
        No. Automated tests cover only part of the requirements. The service guides you through the\nremaining test steps; the statement explicitly states that it is based on a self-assessment.<\/p><\/dd>\n\n<\/dl>\n\n\n
        0.6.4<\/h4>\n\n
          \n
        • Fixed: In the German translation, the hint shown before the first scan closed the quoted\nbutton label with a straight quotation mark instead of the German one.<\/li>\n
        • Changed: New versions are deployed to the plugin directory from the tagged GitHub release, so\nboth carry the identical package.<\/li>\n<\/ul>\n\n
          0.6.3<\/h4>\n\n
            \n
          • Fixed: A rule with exactly one occurrence offered \"Show 1 occurrences\". The string had no\nsingular form. It now ships in both forms, in English and in German - and languages with other\nplural rules get the room they need as well.<\/li>\n<\/ul>\n\n
            0.6.2<\/h4>\n\n
              \n
            • Fixed: After verifying the domain the page reported \"The domain is verified\" at the top and kept\nshowing \"Domain verified: no\" below it, together with the button that had just done the job -\nfor up to five minutes, and only \"Refresh status\" got past it. Verifying now discards the cached\nstate, the way starting a scan already did. A failed attempt leaves the cache alone: nothing\nchanged at the service then.<\/li>\n
            • Fixed: Entering a new connection, and resetting the service address, discard the cached state as\nwell. It belongs to one connection and one address.<\/li>\n<\/ul>\n\n
              0.6.1<\/h4>\n\n
                \n
              • Changed: The setup instructions no longer explain what the token is allowed to do and where it\nis stored - at that point you are looking for the token, not for its permissions.<\/li>\n
              • Changed: The last step now says what the service address is - where the plugin sends its\nrequests - instead of advising whether to change it.<\/li>\n<\/ul>\n\n
                0.6.0<\/h4>\n\n
                  \n
                • Changed: The plugin slug - and with it the text domain, the folder name in the ZIP and the\nfuture directory URL - is now \"barrierepruefung-de-web-accessibility-checker\" instead of\n\"a11y-checker\". The old one was the abbreviation of a name already taken by another plugin.<\/li>\n
                • Changed: Internal prefixes moved along while that is still cheap: options and transients are\n\"barrierepruefung_\", classes \"Barrierepruefung_<\/em>\", files \"includes\/class-barrierepruefung-*.php\".<\/li>\n
                • Changed: The admin page now lives at \"?page=barrierepruefung\", the block is\n\"barrierepruefung\/erklaerung\", and the front-end CSS classes are \"barrierepruefung-erklaerung\",\n\"barrierepruefung-stand\" and \"barrierepruefung-hinweis\".<\/li>\n
                • Changed: Uninstalling now also removes the options and transients written under the old prefix.<\/li>\n
                • Unchanged: the proof of domain ownership (\"a11y-site-verification\") - that name belongs to the\nservice, not to this plugin.<\/li>\n
                • Upgrade notice: the plugin file was renamed, so WordPress deactivates a pre-release copy when\nyou replace it. Enter the connection again after activating. A statement placed with the block\nreports \"unexpected content\" because the block namespace changed; the shortcode\n[barrierefreiheitserklaerung] is unaffected.<\/li>\n<\/ul>\n\n
                  0.5.1<\/h4>\n\n
                    \n
                  • Changed: The link in the plugins list is now labelled \"Settings\" throughout - the label that sits\nnext to every other plugin and is therefore what people look for.<\/li>\n
                  • Changed: The plugin is credited to Lukas Bock, linked to barrierepruefung.de.<\/li>\n<\/ul>\n\n
                    0.5.0<\/h4>\n\n
                      \n
                    • New: The page explains the setup on first use - that the plugin does not scan on its own but is\nthe way into the service, that the token is valid for this one site, and then step by step where\naccount, token and site ID come from (Websites -> your site -> Embedding<\/em>, section WordPress\nplugin and API<\/em>). It used to be one sentence that assumed an account nobody knew about yet.<\/li>\n
                    • New: The instructions state the address of this installation. If a different one is stored with\nthe service, domain verification fails later without a visible reason.<\/li>\n
                    • New: After activation a one-time notice points to the page, and the plugins list carries a \"Set\nup\" link.<\/li>\n
                    • New: The token field says that the number and the vertical bar in front belong to the token.<\/li>\n
                    • Changed: While a scan is running, \"Check whether the scan has finished\" is the primary button and\nthe running-scan notice sits above the buttons instead of below them. Previously the grey\n\"Refresh status\" button was lost next to the blue \"Scan now\", so whoever had started a scan could\nnot see how to get to the result.<\/li>\n
                    • Changed: \"Scan now\" is hidden while a scan is running - a second run would only use up quota.<\/li>\n
                    • Changed: While the first scan is still running the findings section says so, instead of pointing\nat a button that does not exist at that moment.<\/li>\n
                    • Changed: The page now also says why<\/em> it does not update on its own: an automatic reload would\nmove the focus and interrupt screen reader users (WCAG 2.2.2).<\/li>\n<\/ul>\n\n
                      0.4.0<\/h4>\n\n
                        \n
                      • New: Every rule in the findings list can be expanded. \"Show N occurrences\" fetches the\nindividual occurrences of that one rule - page, selector, measurements such as \"contrast 2.41:1\ninstead of 4.5:1\", colour values, the state in which the element becomes visible, the viewport\nand the HTML snippet. Paging happens in steps of 20.<\/li>\n
                      • New: Expanding and paging are ordinary links. Still no JavaScript in the plugin, and only the\nrule you are actually working on is fetched.<\/li>\n
                      • Changed: Findings now come before the quota. They are the reason someone opens the page.<\/li>\n
                      • Changed: Screenshots are not loaded into the WordPress admin area. The page points to the full\nreport instead and says that opening it asks you to sign in first.<\/li>\n
                      • Fixed: For signed-out users the link to the full report ended in a bare error page. The service\nnow sends signed-out visitors to the sign-in page and back to the report afterwards.<\/li>\n<\/ul>\n\n
                        0.3.1<\/h4>\n\n
                          \n
                        • Changed: The readme and the plugin description are in English now, as the WordPress Plugin\nDirectory requires.<\/li>\n
                        • Changed: English is now the source language of the plugin's own strings. German ships as a\ntranslation in languages\/barrierepruefung-de-web-accessibility-checker-de_DE.po - a German installation shows exactly the same\ntext as before.<\/li>\n
                        • Changed: Tested up to WordPress 7.1.<\/li>\n
                        • Known limitation: only the de_DE translation is bundled. Installations running de_AT, de_CH or\nde_DE_formal fall back to English until the plugin is listed in the directory and\ntranslate.wordpress.org supplies those language packs.<\/li>\n<\/ul>\n\n
                          0.3.0<\/h4>\n\n
                            \n
                          • New: Tools \u2192 Accessibility shows the open findings of the last scan - for each rule the\nseverity, the success criterion, the number of occurrences, a note on how to fix it and the\npages affected. Fixing happens in WordPress, \"Scan now\" closes the round.<\/li>\n
                          • New: The page states the page quota of the current billing period.<\/li>\n
                          • New: A \"Refresh status\" button fetches quota and findings again. It deliberately replaces an\nautomatic page reload, which would be disruptive for screen reader users.<\/li>\n
                          • New: If a scan is currently running, the page says so instead of showing an outdated result.<\/li>\n
                          • Changed: State and findings are cached for five minutes; starting a scan and \"Refresh status\"\ndiscard the cache.<\/li>\n
                          • Changed: If the site cannot be retrieved, the reason given by the service is now shown with it.<\/li>\n<\/ul>\n\n
                            0.2.1<\/h4>\n\n
                              \n
                            • New: The stored connection is visible under Tools \u2192 Accessibility and can be undone again.\nUntil now the plugin hid the form as soon as token and site ID had been saved once - even if\nthey were wrong.<\/li>\n
                            • New: The service address can be reset to its default value on its own; the form suggests the\naddress entered last instead of always the default.<\/li>\n
                            • Fixed: A discarded address remained as an empty option; every request afterwards went to a\nrelative path. In that case the default value now applies again.<\/li>\n<\/ul>\n\n
                              0.2.0<\/h4>\n\n
                                \n
                              • Fixed: The heading level is now measured against the topmost heading actually output. Until\nnow the h1 of the statement stayed an h1 at the default setting - in the middle of a page\nthat is itself a violation of WCAG 1.3.1 -, and a section embedded with teil=\"maengel\" or\nteil=\"kontakt\" came out one level too deep. If you have been balancing the levels by hand\nwith ueberschrift=\"3\", switch to ueberschrift=\"2\" now (or leave the attribute out).<\/li>\n
                              • Fixed: The feedback message in the admin area was URL-decoded twice, which made a message\ncontaining a literal percent sequence (e.g. \"%41\") arrive as a character.<\/li>\n<\/ul>\n\n
                                0.1.0<\/h4>\n\n
                                  \n
                                • First release: connection, domain verification, starting a scan, shortcode and block.<\/li>\n
                                • German and English language version, complete uninstall.<\/li>\n<\/ul>","raw_excerpt":"Scans this site for accessibility barriers and embeds your accessibility statement via shortcode.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/366379","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=366379"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/lukasbo"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=366379"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=366379"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=366379"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=366379"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=366379"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=366379"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}