← WOWStudio Accessibility Remediation
Documentation
Everything the plugin does, written for the person who has to use it. Start at the beginning if it is a new install, or go straight to the reference if you know what you are looking for.
Getting started
Scanning
- How scanning worksTwo passes, one on the server and one in your browser, and why neither of them alone is enough.
- Choosing what to checkWhich post types are scanned, why templates and patterns are not, and how to add your own.
- Reading the reportWhat the score counts, what it deliberately does not, and how to use the four figures on the dashboard.
Fixing
- Working through findingsThe inspector, what each finding tells you, and how to get through a long list without losing your place.
- Applying and undoing fixesMarkup fixes, CSS fixes, the preview and diff, the override layer, and what happens when your theme outranks a rule.
- Site-wide fixesFourteen switches that supply what a theme leaves out, each one honest about what it might disturb.
- Describing imagesThe bulk alt-text editor, where the text is saved, and how to tell a decorative image from one that needs describing.
- False positivesSetting a finding aside, recording why, doing it everywhere at once, and taking it back.
Documenting
Reference
- Every checkAll 41 checks, with the WCAG success criterion each one maps to, its severity, and whether a machine can settle it.
- FiltersThe 28 hooks the plugin exposes, what each one changes, and worked examples of the ones people reach for most.
- Roles and capabilitiesThe four capabilities, which roles get them by default, and how to let somebody scan without handing them the whole report.
- The command lineFour WP-CLI commands for scanning, listing findings, inspecting checks and toggling site-wide fixes, with every option.
Running it
- Privacy, data and uninstallingWhat the plugin stores, what it sends anywhere, which is nothing, and exactly what happens when you remove it.
- TroubleshootingLoopback failures, fixes that appear to do nothing, page builders, counts that look wrong, and scans that never finish.
- What it cannot doThe honest limits of automated accessibility testing, and what still needs a person after every check has passed.
19 pages. If something you needed is not here, that is a gap worth knowing about — tell us and we will write it.