Installing and first run

What you need

Requirement	Minimum
WordPress	6.8
PHP	8.1
Tested up to	WordPress 7.1

There is nothing else. No account, no API key, no licence. The plugin contacts no external service at any point, so it works the same on a laptop with no internet connection as it does on a production server.

Installing it

The ordinary way is through your own admin: Plugins → Add New, search for WOWStudio Accessibility Remediation, install and activate.

If you would rather install by hand, download the zip from the WordPress.org directory and upload it to /wp-content/plugins/wowstudio-accessibility-remediation, then activate it from the Plugins screen.

The source is on GitHub if you would rather read it before you run it, which for a plugin that edits your markup is a reasonable thing to want.

What happens on activation

Nothing to your site. This is worth stating plainly, because plugins in this category have a reputation for switching things on.

Activating it:

• adds an Accessibility Remediation menu to your admin
• grants its capabilities to administrators and editors
• creates its own database tables for scans, findings and decisions
• opens a short setup screen

It does not scan anything, change any markup, add anything to your front end, or switch on a single site-wide fix. Every one of those needs you to ask for it.

The setup screen

On first activation you land on a three-step setup rather than an empty report. It covers what the plugin does, what it refuses to claim, the site-wide fixes available to you, and running your first scan.

Every step is optional and nothing is enabled for you. If you skip the whole thing, you end up exactly where you would have been anyway.

The four screens

Once it is running, the plugin is four pages in your admin menu.

Screen	What it is for
Dashboard	The report. Score, totals, what comes up most, which pages have the most to do.
Scan & Fix	The working screen. Choose what to check, read findings, apply fixes, manage images and site-wide fixes.
Settings	Which post types are scannable, which site-wide fixes are on, and the rest of the configuration.
Statement	Generate, edit and publish an accessibility statement.

The header on every screen tells you when anything was last checked, with a shortcut to check more.

Who can see it

Administrators get everything. Editors can run scans and read reports, but cannot change settings or apply fixes. That split is deliberate and it is adjustable — see Roles and capabilities.