Skip to content
Pandus

Pandus Accessibility for WordPress: find, explain and fix accessibility problems

Pandus Accessibility 1.0.0

Free. WordPress 6.5 or newer, PHP 7.4 or newer; tested up to WordPress 7.1. Works with WooCommerce.

In the WordPress.org plugin directory: under review.

Download the plugin (.zip)

Pandus Accessibility is a free WordPress and WooCommerce plugin that checks your site against the WCAG 2.2 AA criteria every week, shows each problem next to the page or product where it occurs, suggests fixes you approve, and adds an accessibility information page and a "Report a barrier" form required under the European Accessibility Act. It is an automated check, not a full audit, and it does not add an overlay.

What the plugin does

  • Weekly WCAG 2.2 AA checks of every page of the site, with 98 automated rules explained in plain language.
  • Problems where you work: a dashboard widget with what to fix first, and a box next to the editor of every page, post and WooCommerce product.
  • Suggested fixes: image descriptions (alt text) and theme fixes that you review, apply and can undo.
  • Accessibility information page for the EAA (Article 13) and the German BFSG (§14), with the known limitations from the latest check.
  • "Report a barrier" form so customers can tell you what they cannot use.
  • Automatic check after changes: a new check runs after you switch the theme or update themes and plugins.
  • Seven languages: English, Ukrainian, German, Polish, Czech, Romanian and Russian.

How to install the plugin

  1. Download the plugin (button above) and, in WordPress, go to Plugins → Add New → Upload Plugin, choose the file and activate it.
  2. Open Pandus in the admin menu and click Connect to Pandus.
  3. Sign in to Pandus or create a free account, then click Connect. You come back to WordPress automatically; there is no key to copy.
  4. The first check starts right away and usually takes a few minutes for the first pages.
  5. Fill in your details for the accessibility information page and create the page.

The plugin gets access only to the connected site, not to your other sites or your account, and you can disconnect it at any time.

Problems next to every page, post and product

In the editor of each page, post and WooCommerce product, the Accessibility (Pandus) box lists the problems the latest check found on that very page: what is wrong, who it affects, how to fix it in WordPress or WooCommerce, which element on the page, and a link to the full explanation of the rule. You fix a missing image description or an unlabelled field where you edit the content, without searching through a long report.

The dashboard widget shows the number of problems by severity — critical, serious, moderate, minor — and the three to fix first. Check now starts a new check within the limits of your plan.

Suggested fixes you review and approve

The Suggested fixes page in the plugin changes your site itself, only after you confirm it:

  • Image descriptions (alt text). Images in the media library without a description get a suggestion from the product or file name. You correct it and save. The same descriptions can be added to images already placed in pages and posts.
  • Theme fixes, each with its own switch: allow zooming on phones, a "Skip to content" link, a visible keyboard focus, underlined links in text. They change the HTML and CSS your server sends, not a script in the browser.
  • Apply all suggested fixes shows the full list of changes and a warning first. After applying, one button undoes the descriptions, the page texts and the theme fixes. Pages you edited after applying are left as they are.

Automatic fixes cover only some problems. They do not make a site accessible on their own and do not mean that it meets any law; check the result on a phone and with the keyboard.

Accessibility information page for the EAA and BFSG

Since 28 June 2025 the European Accessibility Act asks online shops and other services for consumers in the EU, except micro-enterprises, to describe how they meet the accessibility requirements. The plugin creates this page as a draft with the shortcode [pandus_accessibility_statement]: you add your company, the service, its accessibility features, contacts and the market surveillance authority, and the known limitations come from the latest automated check, with its date. Have the text reviewed by your lawyer before you rely on it.

"Report a barrier" form

Customers must be able to report accessibility problems. The form [pandus_report_barrier] works without JavaScript, is usable with a screen reader and the keyboard, and is protected against spam. Each report reaches you by e-mail — you can reply to the visitor directly — and appears in your Pandus account, where you mark it as handled. A visitor's name and e-mail are stored only with their consent.

Automatic check after updates

Theme and plugin updates are when new problems usually appear. A few minutes after you switch the theme or update WordPress, themes or plugins, the plugin starts a new check, at most once an hour.

What the plugin does not do

  • It does not add an accessibility overlay or a toolbar. Overlays do not fix the code that assistive technology relies on; in 2025 the US Federal Trade Commission fined accessiBe $1 million over claims that its widget makes sites compliant.
  • It does not change your site without your confirmation.
  • It does not promise that the site meets the EAA, the BFSG, the ADA or any other law. Automated checks find part of the problems; some need a manual review.

Plans

The plugin is free. The free Pandus plan checks the home page of one site once. The paid plans check every page of the site each week, keep the history and add reports for your clients; agency plans cover 10, 25 or 50 sites with white-label reports. See pricing.

Privacy and data

Pandus runs on servers in the European Union. The plugin sends Pandus the address of your site to run the checks, and the reports from the barrier form. The checks read your public pages like a visitor; they do not log in and do not read your database. Details are in the privacy policy.

Requirements

WordPress 6.5 or newer, PHP 7.4 or newer. Tested with the current version of WordPress and with WooCommerce. Works with any theme, including block themes.