Theme structure
Find heading, landmark, link-name, and navigation issues that repeat across templates.
Rendered-site checking
Find WordPress accessibility issues in the page users receive
Scan the rendered result, then trace the affected element back to a theme template, block, plugin output, or editor content.
Typical WordPress work
Editor content
Catch contrast, image alternative, and form-label problems introduced while publishing pages.
Plugin output
Re-scan forms, menus, and widgets after configuration or plugin updates change their markup.
Review the transaction, not just the storefront
Cart, checkout, login, and payment are connected customer jobs. Treat them as one testable journey while keeping the automation boundary visible.
Cart
Check product options, quantity controls, update messages, names, focus order, and rendered errors.
Checkout
Scan reachable checkout states and record guided keyboard, reflow, label, and error-prevention checks.
Login and account
Use a dedicated saved test account for configured authenticated scans and repeatable journeys.
Payment hand-off
Review the rendered transition and return states; third-party payment behavior still needs human testing.
What automation can support
Rendered markup, accessible names, labels, contrast, structure, selected-rule regressions, and reached-page evidence.
What still needs people
Keyboard flow, understandable errors, content meaning, assistive-technology behavior, and third-party payment states.
See the evidence before signing up
The sample is a real report view: severity, affected element, rule, and a practical direction for the fix. Automated coverage is clearly separated from manual review.
Platform questions
Do I need to install a plugin?
No. wcagc scans the rendered public website, so it does not require a platform plugin.
Will the scan find every accessibility issue?
No. Automated tests find only part of WCAG issues. Theme semantics, content quality, keyboard flows, and assistive-technology behavior also need manual review.
Can I verify a change after fixing it?
Yes. Re-scan the affected page or saved site and compare current evidence while keeping manual checks in the workflow.