PerseiaThink Accessibility Audit for EAA

PerseiaThink Accessibility Audit for EAA analyses the rendered content of your posts and pages against 40 automated tests, mapped to 12 WCAG 2.2 success criteria — eleven at level A or AA, plus one level-AAA good practice that ships as a notice — and shows you a prioritised, actionable list of issues right in the editor. WCAG is the yardstick European accessibility legislation is built around: the EU Accessibility Act sets functional requirements, and the harmonised standard EN 301 549 (which incorporates WCAG) is the usual way to demonstrate you meet them. It runs entirely on your own server: no external APIs, no accounts, no tracking, no data sent anywhere. Not affiliated with Accessibility Checker, Adinav, GranTech, or any other accessibility-audit plugin for the EAA. What it checks (40 tests) Images (7) — missing alt; alt that is just the file name; alt padded with "image of…"; over-long alt that should be a long description; empty alt on large, content-looking images; image buttons with no alternative text; image-map areas with no name. Links (7) — links with no perceivable text; vague text such as "read more" or "click here"; raw URLs used as link text; links to PDFs and other files that never say so; title attributes that merely repeat the link text; two adjacent links pointing to the same place; links that open a new tab without warning. Forms (5) — fields with no associated label; <label for> pointing at nothing; <fieldset> with no <legend>; radio/checkbox groups with no group name; personal-data fields missing autocomplete (WCAG 1.3.5, level AA). Headings and structure (4) — empty headings and skipped heading levels; paragraphs in bold used as fake headings; lists faked with dashes or numbers instead of real list markup; empty lists and orphaned list items. Tables (3) — data tables with no header cells; no <caption>; headers attributes pointing at ids that do not exist. Media and motion (5) — video with no captions track; audio with no alternative; media that autoplays with no way to stop it; <blink> and <marquee>; timed meta refresh. ARIA and semantics (9) — buttons and iframes with no accessible name; broken ARIA references; invalid role values; aria-hidden wrapped around focusable elements; widget roles missing their required state; role="presentation" used where it removes needed meaning; duplicated ids that something references; positive tabindex. Who the EU Accessibility Act obliges (and who it does not) Most plugins in this space imply that every website owner is now legally on the hook. That is not what the law says, so here is the honest version — for Spain, where this plugin is focused. Other EU countries transposed the same directive with their own texts, so check yours. First test — is it one of the covered services? The Act does not cover "websites" in general. It covers a closed list: e-commerce, consumer banking, e-books, passenger transport, electronic communications and access to audiovisual media services, among others. A brochure site for a plumber is not automatically in scope. Second test — are you a microenterprise? If you are in scope, Spain's Ley 11/2023 (art. 3) exempts microenterprises that provide services — fewer than 10 people and annual turnover or balance sheet total not exceeding €2 million — from the accessibility requirements and from any obligation to comply with them. Note the exemption covers services: it does not extend to making, importing or distributing the physical products the Act also lists. Obligations have been enforceable since 28 June 2025. Being outside the Act is not the same as being off the hook. Spain's general non-discrimination rules on access to goods and services offered to the public (RDL 1/2013, Ley 15/2022) apply regardless of company size, and if you deliver a public service or receive public funding, RD 1112/2018 may apply too. Beyond the law: a larger client, a marketplace or a public tender can require accessibility contractually, and a sizeable share of the population — around a quarter of EU adults report some activity limitation (Eurostat) — is affected by whether your site works for them. This is a plain-language summary, not legal advice. If you need to know whether the law applies to you, ask a professional. Honest by design Automated tools detect roughly 30–40% of accessibility problems. This plugin finds many common issues and tells you how to fix them — it does not change your content for you, and it does not guarantee legal compliance with the EAA or any regulation, which always requires human review. Treat it as an assistant, not a certificate. Spanish first The plugin ships with a complete Spanish (es_ES) translation and is written around the EU Accessibility Act and Spain's Ley 11/2023. On a Spanish WordPress install it appears in Spanish automatically. Pro add-on, for agencies A separate Pro add-on is available for agencies and professionals maintaining client sites: whole-site and scheduled scans, issue history over time, an accessibility statement backed by your real audit data, a printable compliance report, and a colour-contrast deep scan. The free plugin described here is fully functional on its own.

0.2.0

• Expanded from 16 to 40 automated tests, covering 12 WCAG 2.2 success criteria (eleven at level A/AA plus one AAA good practice) — including 1.3.5 Identify Input Purpose (AA).
• New checks across images, links, forms, tables, lists, media, motion and ARIA.
• Clearer wording about who the European Accessibility Act actually obliges.

0.1.0

• Initial release: 16 WCAG 2.2 checks, automatic scan on save, editor panel, site summary page, front-end highlighter, English + Spanish (es_ES). Runs entirely on your server.