=== Equivora ===
Contributors: mujahidwp
Tags: accessibility, accessibility statement, wcag, european accessibility act, a11y
Requires at least: 6.6
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Accessibility without overlays: write an accessibility statement, collect barrier reports and find accessibility problems in your content.

== Description ==

Since June 2025 the **European Accessibility Act (EAA)** asks many online shops and service websites to publish an accessibility statement and to give visitors a way to report barriers. Public sector websites in the EU have the same duty, and many other organizations follow the same practice voluntarily.

Most accessibility plugins add an "overlay" toolbar on top of your site. Accessibility experts and many people with disabilities advise against overlays, because they do not fix the underlying problems. **Equivora takes the honest route** and helps you with the three things that actually matter:

1. **Accessibility Statement builder** — answer a few plain questions (standard, conformance status, known limitations, contact, enforcement procedure) and Equivora writes a clear, well-structured statement. Show it with the Accessibility Statement block. It always reflects your latest answers.
2. **Barrier reports** — the Accessibility Feedback block is a fully accessible form where visitors tell you what they could not use. Reports arrive privately in your dashboard with a status (New, In progress, Resolved) and you get an email.
3. **Content Check** — scans your published posts and pages for common problems: images without alternative text, file names used as alt text, empty or vague links ("click here"), empty buttons, skipped or empty headings, a second H1, iframes without a title, tables without headers and autoplaying media. Posts are re-checked automatically whenever you update them.

= Highlights =

* **No overlay, no toolbar, no tracking.** Equivora never changes how your site looks for visitors.
* **One-click setup** — create the statement page and the feedback page with a single button.
* **Accessible by design** — real labels, hints linked with `aria-describedby`, errors announced to screen readers, focus moved to the result, works with keyboard only and without JavaScript.
* **No CAPTCHA** — CAPTCHAs are a barrier for many people. Spam is stopped by a honeypot, a time check, a rate limit and your Disallowed Comment Keys.
* **Works with page caching** thanks to a signed, refreshable form token.
* **Yearly review reminder** — the dashboard reminds you when your statement is more than a year old.
* **Privacy friendly** — reports are never published, IP addresses are only kept as a short-lived salted hash for the rate limit, and reports are included in the WordPress personal data export and erase tools.
* **Blocks only, no build step**, lightweight and translation ready.

= Important =

Equivora helps you document and improve accessibility. It is not legal advice, and no plugin can make a website accessible by itself. Automated checks find only part of all problems, so keep testing with a keyboard and a screen reader.

== Installation ==

1. Install and activate Equivora from the Plugins screen.
2. Go to **Accessibility > Statement**, answer the questions and click **Save statement**.
3. Click **Create pages** to publish an Accessibility Statement page and an Accessibility Feedback page. Link the statement page in your site footer.
4. Open **Accessibility > Content Check** and click **Check all content**.

== Frequently Asked Questions ==

= Does Equivora make my website compliant with the EAA or WCAG? =

No plugin can do that on its own. Equivora gives you the statement and the feedback mechanism that the law expects, and helps you find common content problems. Fixing your theme and content is still needed.

= Why no accessibility overlay or toolbar? =

Overlays try to repair a site with JavaScript on top of it. They often conflict with the assistive technology people already use and do not remove the barriers in your code and content. Equivora focuses on real fixes and honest communication instead.

= Which standard should I choose? =

The European Accessibility Act refers to the harmonised standard EN 301 549, which includes WCAG 2.1 level AA. WCAG 2.2 level AA is the newest version and a good target for new websites.

= Where do barrier reports go? =

They are stored privately under **Accessibility > Barrier Reports** and are never published. You can also receive an email for each new report under **Accessibility > Settings**.

= Can I use the feedback form without the statement? =

Yes. Both blocks work independently.

= Which content does the Content Check scan? =

All published posts, pages and other public post types. Developers can change the list with the `equivora_check_post_types` filter and the list of vague link texts with the `equivora_generic_link_words` filter.

= Does the plugin send data to external services? =

No. Everything stays on your website.

= What happens when I delete the plugin? =

Settings and check results are removed. Barrier reports and your statement are kept unless you enable the option to delete them under **Accessibility > Settings**.

== Screenshots ==

1. The Accessibility Statement builder with known limitations.
2. A published accessibility statement on the front end.
3. The Accessibility Feedback form for visitors.
4. Barrier reports in the dashboard with status.
5. The Content Check with errors and warnings per post.

== Changelog ==

= 1.0.0 =
* First release: Accessibility Statement builder and block, Accessibility Feedback block with private barrier reports, and the Content Check.

== Upgrade Notice ==

= 1.0.0 =
First release.
