WordPress
Theme, plugin and block markup
Start with the affected template, block or plugin output rather than adding a front-end overlay.
Platform-aware accessibility checks
ClearSite recognises WordPress, Shopify, Squarespace and Wix pages, then uses that context to make the route from finding to source-level fix less vague.
Supported platforms
Detection comes from the rendered page markup. If ClearSite cannot identify a supported platform confidently, it returns general HTML and CSS guidance rather than pretending it knows the publishing system.
Theme, plugin and block markup
Start with the affected template, block or plugin output rather than adding a front-end overlay.
Theme and storefront markup
Use the affected product, collection or theme component to separate content fixes from theme-code fixes.
Template and block markup
Identify whether the barrier sits in editable page content, a block setting or custom CSS and code.
Builder and component markup
Trace the finding back to the relevant editor element, page setting or custom component before retesting.
ClearSite checks the rendered markup for platform signals instead of asking you to choose a generic report type.
Findings include the affected element and guidance framed for the detected platform, with axe-core guidance as the deterministic fallback.
Re-scan the same live page. A change is useful when the detected barrier clears, not merely when the editor says it saved.
What platform-aware means
ClearSite tests the page a browser renders with axe-core. Platform detection adds context to the fix instructions; it does not change the underlying accessibility standard or turn an automated scan into a full audit.
Some questions still require a person: whether alternative text is useful, whether a full keyboard journey makes sense, and whether the experience works with assistive technology. For a definitive assessment or legal position, combine automated checks with manual specialist review.
Read the broader website accessibility scanner workflow and testing limits.
Scan a homepage, product page, contact form or checkout step, then fix the shared source and test again.
Run the free scan