=== Faro Accessibility ===
Contributors: farowp
Tags: accessibility, wcag, a11y, accessibility audit, accessibility checker
Requires at least: 6.4
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 0.8.1
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Accessibility scanner for WordPress: finds WCAG 2.2 AA issues, who must fix them and how, and keeps evidence of progress. Spanish, no accounts.

== Description ==

Faro Accesibilidad reviews your pages with axe-core 4.10.2 inside your own browser and turns the result into a work list you can act on:

* **Priority, not a wall of errors.** Every issue is grouped by severity and labelled with who has to fix it: your content, your theme or a plugin.
* **How to fix it.** Each rule comes with concrete WordPress steps, a link to open the page in the editor and a button to copy the CSS selector.
* **Decisions with memory.** Mark each issue as open, fixed or ignored with a note. A rescan respects your decisions: ignored issues do not come back, fixed issues that reappear are reopened.
* **Manual review.** 16 checks in 6 groups (keyboard, forms, content, media, visual, documents) for what no scanner can see.
* **History.** Every scan records new, closed and reopened issues, so you can show progress instead of claiming it.
* **Accessibility statement draft.** Generated from the real state of the site. It never says "fully conformant" while serious issues remain open.
* **Whole-site scan.** Scan every registered page of your site one after another from the dashboard.
* **Stale page watch.** A daily check flags pages that have not been reviewed in 7, 14 or 30 days and sends one email at most per week.

= What it does not do =

* It does not add an accessibility overlay or toolbar that rewrites your HTML in the visitor's browser. Those tools hide symptoms, break on updates and do not make a site compliant.
* It does not fix your site for you. It tells you what is wrong, where it is and how to correct it. The change is made in the page, the template or the plugin that generates it.
* It does not promise legal compliance. Compliance belongs to the site owner; this plugin gives you the evidence and the statement draft.

= Languages =

English is the source language and a complete Spanish translation is included. WordPress uses the language set for each site.

= Privacy =

Nothing leaves your site. Scans run in your browser, results are stored in your own database, and the plugin makes no requests to any external service. There is no account, no licence key and no telemetry.

= Requirements =

* WordPress 6.4 or later, PHP 7.4 or later.
* A modern browser to run scans (Chrome, Edge, Firefox or Safari).
* JavaScript enabled in the admin.

== Installation ==

1. Upload the plugin folder to `/wp-content/plugins/`, or install it through Plugins → Add New.
2. Activate the plugin through the Plugins screen.
3. Open any page of your site while logged in as an administrator and press **Escanear accesibilidad** in the admin bar.
4. Review the report under **Accesibilidad** in the admin menu.

== Frequently Asked Questions ==

= Does it make my site accessible? =

No single plugin can. It finds and prioritises the problems a machine can verify, gives you the steps to fix them, and keeps a record of what you have fixed. The manual checks cover what automated tools cannot see.

= Does it work with any theme or plugin? =

Yes. It analyses the rendered HTML of your pages, so it works with block themes, classic themes, page builders and WooCommerce. Some issues will be owned by the theme or by a plugin, and the report tells you so.

= Which languages does it speak? =

The interface is written in English as its source language and ships with a complete Spanish (es_ES) translation. WordPress picks the language of each site; nothing is hardcoded. Other languages can be added through translate.wordpress.org.

= Does it send data anywhere? =

No. Everything runs and stays on your site. There are no external API calls, accounts or telemetry.

= Can I use it on client sites? =

Yes. It is GPL, there is no per-site fee and no upsell inside the admin beyond a single line in the footer.

== Screenshots ==

1. Dashboard with the health score, the open issues by severity and every page with its last scan.
2. Pages table with the whole-site scan button and the pages that need a new scan.
3. Page report: score, severity summary and the list of issues to work through.
4. Every issue with its fix guide, the selector to copy and the decision (fixed or ignored).
5. Scan history with new, closed and reopened issues, and how the health score evolves.
6. Manual review: 16 checks that no scanner can decide, with status and note.
7. Accessibility statement draft generated from the real state of the site.

== Changelog ==

= 0.8.1 =
* Fix: the admin menu entry and the header of the dashboard were hard-coded in Spanish; in an English install they now read "Accessibility", and the product name is translated in the Spanish catalogue.


= 0.8.0 =
* The plugin is now fully internationalised: every screen, report, email and JavaScript message goes through the translation functions, with English as the source language.
* Ships with a complete Spanish (es_ES) translation: the interface Spanish users already know, now as a translation instead of hardcoded strings.
* New languages/faro-accesibilidad.pot so other languages can be translated.

= 0.7.2 =
* Fixed a PHP 8.3 deprecation when an issue had no note yet.
* Plugin Check on the release build: 0 errors. Release ZIP contains only runtime files.

= 0.7.1 =
* New health score: it measures the average page with a curve that does not saturate (previously any site with around 35 serious issues showed 0 forever).
* Scans store the score calculated from what is still open, without counting duplicates.

= 0.7.0 =
* Whole-site scan from the dashboard: pages of the same domain, with progress and a stop button.
* Stale page watch: daily check, email at most once a week, "Sin revisar" chip in the dashboard.

= 0.6.0 =
* Accessibility statement draft: conformance status derived from the data, scope, known issues and contact details; published as a draft page or downloaded as standalone HTML.

= 0.5.0 =
* Fix guide per rule: concrete WordPress steps, open the page in the editor, view the page and copy the selector.

= 0.4.0 =
* Compared history: every scan records new, closed and reopened issues, with an evolution chart and a table of the last scans.

= 0.3.0 =
* Manual review: 16 checks in 6 groups with status, note and progress bar.

= 0.2.0 =
* Issue states: open, fixed and ignored with a note; filters; rescanning respects human decisions.

= 0.1.0 =
* First version: axe-core 4.10.2 scanner, page report, CSV export and REST API.

== Upgrade Notice ==

= 0.7.2 =
* Fixed a PHP 8.3 deprecation when an issue had no note yet.
* Plugin Check on the release build: 0 errors. Release ZIP contains only runtime files.

= 0.7.1 =
Fixes the health score, which stayed at 0 on sites with many issues.
