Klarvo Access – Accessibility Fixes for WooCommerce
| 开发者 | klarvo |
|---|---|
| 更新时间 | 2026年8月25日 03:26 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Applies fixes in your live HTML, server-side — targeted tag rewrites in the output, never client-side JavaScript painted over the page. Screen readers and assistive technology receive the corrected markup.
- Reversible and safe — fixes are stored locally; deactivating the plugin removes every applied change. Targeted tag rewrites with an integrity fail-safe preserve your markup (block-theme inline SVGs are not corrupted).
- Serves an accessibility statement — an honest, structured statement page generated from your real conformance data, published at a fixed URL on your site.
- WooCommerce-aware — built for stores. Fixes apply server-side across your site's served pages; scanning covers your homepage and the key store pages the service discovers.
安装:
- Install and activate the plugin.
- Create a Klarvo Access account at klarvoaccess.com and add your store.
- In your store, go to Settings → Klarvo Access, generate a connection token from your Klarvo Access dashboard, and pair your store.
- Run a scan from your Klarvo Access dashboard. Validated fixes are pushed to your store and applied automatically.
- Optionally publish your accessibility statement from the dashboard.
屏幕截图:
常见问题:
Is this an accessibility overlay or widget?
No. Accessibility overlays inject client-side JavaScript that paints supposed remediations on top of the page; assistive technology often still receives the original, broken markup. Klarvo Access rewrites the real served HTML server-side, so screen readers receive the corrected page. Administrators can optionally turn on a private diagnostic highlighter from the WordPress admin bar to inspect recorded findings. That tool changes no page content, is never sent to visitors, and is not the remediation mechanism.
Does the plugin work on its own?
No. It applies fixes generated by the Klarvo Access service and requires a Klarvo Access account (a paid subscription). Scanning your store is free; applying fixes requires a paid plan.
Will this make my site "100% compliant" or protect me from lawsuits?
No, and we will never claim that. Automated tools cannot establish full conformance, and no one can guarantee legal immunity. Klarvo Access fixes what automation can and reports the rest honestly. A WCAG 2.2 AA conformance certificate (scoped and dated) is issued only by the Klarvo Access professional human audit add-on.
What happens if I deactivate the plugin?
Every applied fix is removed and the served HTML returns to its original state. The accessibility statement page is removed. Your page cache is purged so visitors receive the reverted pages too. Stored data (the fix list and settings) remains, so re-activating restores your fixes.
What happens if I uninstall the plugin?
Uninstalling removes all stored data: the fix table and every plugin setting (pairing, keys, the statement copy, cache state). Nothing is left in your database. Your site serves its original, untouched HTML.
How does it work with full-page caching?
When fixes change, the plugin purges your page cache automatically (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer, the Cloudflare plugin, WP-Optimize, Hummingbird, Breeze, and Varnish). The Klarvo Access service then independently checks the page real visitors receive; until your cache serves the fixed page, the fix is honestly shown as "waiting for your page cache" — never falsely marked complete.
Is it compatible with my theme?
Yes — it applies targeted rewrites to the served HTML and is theme-agnostic. It is tested with block themes (it preserves inline SVGs and other markup that naive HTML processors corrupt).
更新日志:
- Stylesheet fixes (colour contrast, focus outlines, link underlines, the skip link's focus style) are now delivered through WordPress's own enqueue system instead of being written into the page markup, per WordPress.org guidelines — with the same server-side, no-overlay guarantees and full reversal on deactivate.
- The screen-reader-only "Opens in a new tab" warning applies only when its hiding stylesheet is confirmed present on the page, so it can never render as visible text.
- The fix store is now verifiable end to end: the service can confirm the exact set of fixes your store holds, and a store that cannot read its own state says so honestly instead of reporting an empty set.
- Visitor-facing and admin text is fully translatable (updated translation catalogue), including the simplified summary block and accessibility statement fallbacks.
- Tested up to WordPress 7.1; passes the WordPress.org Plugin Check with no errors or warnings.
- First public release of the Klarvo Access service connector.
- Applies reversible accessibility fixes server-side in the real HTML, with an integrity fail-safe and independent served-page verification.
- Supports alternative text, link and button names, form labels, document language, colour contrast, skip links, landmarks, headings, and other store-focused remediations.
- Includes an honest served accessibility statement, a human review queue, internationalisation, complete uninstall cleanup, and automatic integration with common WordPress page caches.
- Cache-aware apply: automatic page-cache purging (WP Rocket, LiteSpeed, W3 Total Cache, WP Super Cache, SiteGround Optimizer, Cloudflare plugin, WP-Optimize, Hummingbird, Breeze, Varnish) whenever fixes change, plus cache observability for the service.
- Real document language: the service now reads your store's actual language for
langfixes (no hardcoded values). - Full internationalisation (text domain
klarvo-access) and a complete uninstall routine (removes the fix table and all settings). - Production service endpoint as the default; quality and safety hardening throughout.
- Initial release: server-side fix application (targeted tag rewrite), engine pairing, fix store, authenticated REST endpoints, and the served accessibility statement.