=== BazSite Accessibility ===
Contributors: bazsite
Tags: accessibility, wcag, a11y, alt text, accessibility toolbar
Requires at least: 6.2
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 0.2.2
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Scan every page for accessibility problems, fix what can be fixed automatically, and add an optional accessibility toolbar.

== Description ==

BazSite Accessibility opens every published page in your browser and runs the WCAG 2.1 A and AA checks of axe-core, the engine most accessibility checkers use, plus a few of its own: pictures marked as decorative, a link to an accessibility statement, videos and PDF files to check by hand. You get a score and a plain list of what was found, where, and how it is fixed. The scan is free.

One click turns on the automatic fixes. They change what visitors get, never the texts saved in your pages, and each one can be turned off:

* Image descriptions from the media library for pictures placed without one.
* Names for icon links and buttons, titles for embedded frames, names for form fields, and "opens in a new tab" for such links.
* A clear keyboard focus outline.
* Pinch zoom on phones where the theme blocked it.
* Underlined links inside text.
* A "skip to content" link when the theme has none.
* Text colors with too little contrast, changed to the closest color that passes.

Images in the media library without a description can be described by AI from the picture itself. That runs on BazSite's servers and is paid from your BazSite credits; every description is logged and can be undone.

You can also show an accessibility toolbar on the site (off by default): bigger text, high contrast, grayscale, highlighted links, a readable font and no animations. The visitor's choices stay in their own browser. And you can create a draft accessibility statement page in the site's language.

Automatic checks find about half of what accessibility standards ask; the rest (captions, reading order, testing with a real screen reader) needs a person. Neither the plugin nor the toolbar makes a site compliant by itself.


= Third-party code =

axe-core by Deque Systems (https://github.com/dequelabs/axe-core), MPL-2.0, included as assets/axe.min.js with its license.

== Installation ==

1. In your WordPress admin, go to **Plugins → Add New**, search for "BazSite Accessibility", then install and activate it. (Or upload the zip in **Plugins → Add New → Upload Plugin**.)
2. Open **BazSite → Accessibility** in the admin menu. The first scan starts by itself; it runs in your browser and is free.
3. Click **Fix automatically** to see what will change and turn the fixes on. Each one can be turned off later.
4. Optional: turn on the accessibility toolbar and create a draft accessibility statement page.
5. To get AI descriptions for images, click **Connect to BazSite** and sign in, or open a free account.

== Frequently Asked Questions ==

= Is the scan free? =
Yes. The scan, the score, the automatic fixes, the toolbar and the statement page are free. Only AI image descriptions use BazSite credits or a plan.

= Does it make my site compliant? =
No plugin can do that alone. Automatic checks find about half of what accessibility standards ask; the rest (captions, reading order, testing with a screen reader) needs a person. The plugin shows what it found and what still needs a person.

= Does it change my content? =
The automatic fixes change what visitors get, never the texts saved in your pages, and each fix can be turned off. AI image descriptions are written into the media library, logged, and can be undone. A hard-to-read color can also, when you choose so, be changed right in the Elementor widget or block that sets it, logged with a backup and undone in one click.

= Does the toolbar slow the site? =
It is off by default. When on, it adds one small script and style, and the visitor's choices stay in their own browser.

== Screenshots ==

1. The site's accessibility score in five parts and the most important problems.
2. Everything the scan found, one row per rule, with where and how it is fixed.
3. Automatic fixes, each with its own switch.
4. The accessibility toolbar and its settings.

== External services ==

Only the AI image descriptions use BazSite (https://bazsite.com), a service run by the plugin's authors. Nothing is sent before an administrator connects the site.

* **Connecting** (when an administrator clicks "Connect to BazSite"): the site's address, name and language are sent, and the administrator approves in their own browser. BazSite returns a key that is stored in this site's options.
* **AI image descriptions** (when an administrator asks for them): the public addresses of media library images without a description, their file names and the titles of the pages they belong to.

The scan itself runs in the administrator's browser with axe-core, included in the plugin; pages are not sent anywhere.

BazSite terms of use: https://bazsite.com/en/terms
BazSite privacy policy: https://bazsite.com/en/privacy

== Changelog ==

= 0.2.2 =
* Scanning again opens only the pages changed since the last scan; a "Full scan" button checks every page, and a site-wide change (theme, plugin, menus, Elementor's site settings) checks every page by itself.
* Every line that can be fixed says "Not fixed yet" and has its own "Fix now" button, with what the fix does; after the fix it shows "Fixed".
* Before a fix that changes the look, a window shows the colors before and after, and offers two ways: change the color right in Elementor or the block (with undo), or a CSS layer as the page is shown that leaves every setting as it was.
* After a fix the site's caches (SiteGround, WP Rocket, LiteSpeed, W3 Total Cache, Elementor and others) are emptied, only the pages that had the problem are scanned again, and the result says how many places were fixed, how many are left and why.
* Every hard-to-read text on a page is fixed, not only the first 25.
* Buttons that point at a part that isn't on the page (Elementor's phone menu and accordions) are explained in plain words, shown on their page with one click, and fixed automatically.
* "Examples" shows the element's code again.
* The toolbar picks its icon and text color by itself: dark on a light color, white on a dark one.

= 0.2.1 =
* Built exactly as the WordPress.org package: full readme (installation, questions, external services), icons and banners.
* Tested up to WordPress 7.1.

= 0.2.0 =
* A new screen in BazSite's shared look: the score with its five parts, the most important problems, a table with one row per rule, search and filters, and a card on the BazSite home screen.
* The first scan runs by itself right after installing.
* "Fix automatically" shows what will change, fixes, scans again and shows the result, with one "Undo".
* Every text color that is too faint is fixed automatically, on the exact element when no shared rule is safe; only what truly needs a person stays, with the reason.
* Clear labels: "Will be fixed automatically", "Fixed", "Needs a person, and why".
* The toolbar opens and closes with a short animation, has 4 sizes, 6 positions (bottom, middle or top, right or left), a distance from the side and up or down, its own colors for the button and the panel's buttons, and a "Accessibility toolbar by BazSite" line.

= 0.1.3 =
* Image descriptions are written for search too and use the SEO plugin's business profile when it is installed.
* Comes with BazSite's updated shared look (core 1.3.0): a richer BazSite home screen.

= 0.1.2 =
* BazSite's new shared look and home screen.

= 0.1.1 =
* Every issue is explained in plain words: what it means for visitors and how to fix it, with who can fix it (automatic, you, or a developer).
* New automatic fixes: hidden parts the keyboard could still reach, button names that differ from their words, wrong ARIA labels from themes and plugins, scrolling boxes.
* Under the one "BazSite" admin menu item.

= 0.1.0 =
* First version: accessibility scan and score, automatic fixes, AI image descriptions with undo, accessibility toolbar, draft accessibility statement.
