Title: Silicon Sicily Accessibility Fixer for WooCommerce Author: siliconsicily Published: October 19, 2026 Last modified: October 19, 2026 --- Search plugins ![](https://ps.w.org/silicon-sicily-accessibility-fixer/assets/banner-772x250.png? rev=3754809) ![](https://ps.w.org/silicon-sicily-accessibility-fixer/assets/icon-256x256.png? rev=3754809) # Silicon Sicily Accessibility Fixer for WooCommerce By [siliconsicily](https://profiles.wordpress.org/siliconsicily/) [Download](https://downloads.wordpress.org/plugin/silicon-sicily-accessibility-fixer.1.0.0.zip) * [Details](https://wordpress.org/plugins/silicon-sicily-accessibility-fixer/#description) * [Reviews](https://wordpress.org/plugins/silicon-sicily-accessibility-fixer/#reviews) * [Installation](https://wordpress.org/plugins/silicon-sicily-accessibility-fixer/#installation) * [Development](https://wordpress.org/plugins/silicon-sicily-accessibility-fixer/#developers) [Support](https://wordpress.org/support/plugin/silicon-sicily-accessibility-fixer/) ## Description Accessibility Fixer scans the six pages that matter for a sale — home, category, product, cart, checkout, my account — with axe-core, the same accessibility engine used by professional testing tools, running privately in your own browser. It reports every issue it finds, with a likely origin (theme, plugin, or content) and the WCAG criteria involved. For a handful of common, well-understood issues it can fix the underlying HTML in code: a missing or invalid page language, a duplicated or empty page title, a missing skip-to-content link, and links or buttons with no accessible name. Each fix is off by default, has a preview, and can be switched off at any time, restoring the page exactly as it was. **What Accessibility Fixer does not do.** It does not make your store compliant. No automated tool can honestly promise that. It is not legal advice and it does not replace a manual review or an audit by a qualified professional. It does not touch your cart, checkout, or account pages with any fix — those are only scanned and reported, never modified, because a mistake there could stop a sale. It does not write anything to your theme files, your database content, or your product catalog. It does not use an overlay or a widget that changes what visitors see in their browser; every fix is applied in the HTML your server sends out, or not at all. **Why this matters now.** The European Accessibility Act has been in force since 28 June 2025 and covers e-commerce; separately, accessibility lawsuits against online stores are common in the United States. Accessibility Fixer does not chase either of those facts with fear-based claims — it just finds and fixes what it honestly can, and lists what still needs a person to look at it. **How it works, in short.** 1. You read a short notice about what the plugin does and does not do, and acknowledge it once per admin account. 2. You run a scan. By default the cart and checkout are scanned empty, with nothing added and nothing written; there is an opt-in to scan checkout with one real product in your own session, which is removed automatically afterward. 3. You get a report per page: rule, severity, WCAG references, a code snippet, a likely origin, and whether a fix is available. 4. For fixable issues you can preview the change privately, then turn it on. Accessibility Fixer asks known caching plugins to clear the page and re-checks the live HTML without credentials, so you can see whether the fix actually reaches your visitors— caching can otherwise hide a fix that is technically “on.” 5. A manual checklist covers what no automated tool can verify (contrast, alternative text, focus order, and more), with a status you set yourself. 6. Every screen ends with the same line: this report is not a certification and not legal advice. **Performance and safety.** Fixes only apply where nothing else is switched on; with everything off, Accessibility Fixer adds no code to your public pages. Each fix measures its own added time, and switches itself to “suspended” if it ever averages more than 20 ms per page, so it cannot quietly slow your store down. **Your data.** Everything stays on your site. Scanning runs in your browser; axe- core ships inside the plugin; nothing is sent to any external server. This is version 1.0: free, focused on the buying journey, honest about its limits. A paid version with scheduled scans, multi-site management, and more is being considered for later, entirely as a separate plugin — nothing in this free version will ever be locked behind it. **In italiano.** Accessibility Fixer trova e corregge nel codice i problemi di accessibilità del tuo negozio WooCommerce, e ti dice con onestà che cosa resta da controllare a mano. Scansiona le sei pagine che contano per una vendita (home, categoria, prodotto, carrello, cassa, account) con axe-core, lo stesso motore degli strumenti professionali, eseguito nel tuo browser senza inviare nulla all’esterno. Per quattro problemi comuni( lingua della pagina, titolo, link “salta al contenuto”, link e bottoni senza nome) applica la correzione nell’HTML, con anteprima, verifica e possibilità di spegnerla in qualsiasi momento. Non tocca mai carrello, cassa e account, non scrive nel tema né nel database, non usa barre o widget sovrapposti e non promette conformità: nessuno strumento automatico può farlo. La traduzione italiana dell’interfaccia è pronta e sarà distribuita da translate.wordpress.org dopo la pubblicazione. ### What’s next Accessibility Fixer 1.0 is deliberately small: six store pages, four fixes, everything verified. Here is what we are planning for the next releases, in the order we expect to ship them: * **More in-code fixes.** Product images with no alternative text, filled from the product name; form fields with a placeholder but no label; duplicate element IDs; links that open a new tab without saying so. Same rule as today: a fix is applied only when the correct value is certain, otherwise the issue is reported, not guessed. * **Scan any page you choose.** Add your blog, landing pages or legal pages to the six store pages scanned by default. * **A guide for every manual issue.** For each problem Accessibility Fixer cannot fix safely, a short page explaining where it usually comes from and how to correct it in your theme. * **Report export.** PDF and CSV, for agencies and for keeping a record of what was checked and when. **Your feedback decides the order.** We are a very small team and we build what people actually ask for. If one of these matters to your store, or if something is missing from the list, tell us in the support forum or leave a review: a single message saying “I need the image fix” moves it up the list. Bug reports are welcome too, with the theme name and WooCommerce version if you can. Nothing on this list will ever be locked behind a paid version: what is free today stays free. ### Third-party libraries Accessibility Fixer bundles axe-core 4.13.0 (Copyright Deque Systems, Inc.), licensed under the Mozilla Public License 2.0, which is compatible with the GPL this plugin is distributed under. The licence text ships in `assets/vendor/axe-core-LICENSE. txt`. The file shipped is the official minified distribution build, unmodified. The human- readable source for the same version is at https://github.com/dequelabs/axe-core/ releases/tag/v4.13.0, and `assets/vendor/README.md` records the version, licence and provenance in full. ### Privacy Accessibility Fixer does not send any data to an external server. Scanning happens in your own browser, and axe-core is included in the plugin itself. On your own site, Accessibility Fixer stores, in its own database tables and WordPress options: * Scan results (page, issue, likely origin) for up to the 10 most recent full scans, plus the latest verification scan per fix per page. * Which fix is on, off, or suspended, and its measured performance. * The status of each manual checklist item, and who last updated it. * The identifier of the admin user who acknowledged the notice or switched a fix on or off, with a timestamp — nothing about your store’s visitors is ever collected. Uninstalling the plugin removes its database tables and settings. The acknowledgement log is kept by default so it survives a reinstall, but can be deleted at uninstall time from Settings. ## Screenshots [⌊Report — every issue found across the six scanned pages, with severity, likely origin, and whether a fix is available.⌉⌊Report — every issue found across the six scanned pages, with severity, likely origin, and whether a fix is available.⌉[ Report — every issue found across the six scanned pages, with severity, likely origin, and whether a fix is available. [⌊Fixes — the four available fixes, each with its own switch, mechanism, reliability, and verification status.⌉⌊Fixes — the four available fixes, each with its own switch, mechanism, reliability, and verification status.⌉[ Fixes — the four available fixes, each with its own switch, mechanism, reliability, and verification status. [⌊Preview — trying a fix privately before turning it on for visitors.⌉⌊Preview — trying a fix privately before turning it on for visitors.⌉[ Preview — trying a fix privately before turning it on for visitors. [⌊Comparison — before and after a fix is switched on or off: resolved, new, and unchanged issues.⌉⌊Comparison — before and after a fix is switched on or off: resolved, new, and unchanged issues.⌉[ Comparison — before and after a fix is switched on or off: resolved, new, and unchanged issues. [⌊Manual checks — the checklist for what no automated scan can verify, with status you set yourself.⌉⌊Manual checks — the checklist for what no automated scan can verify, with status you set yourself.⌉[ Manual checks — the checklist for what no automated scan can verify, with status you set yourself. [⌊Welcome and acknowledgement — the notice every admin reads once before any fix can be switched on.⌉⌊Welcome and acknowledgement — the notice every admin reads once before any fix can be switched on.⌉[ Welcome and acknowledgement — the notice every admin reads once before any fix can be switched on. ## Installation 1. Upload the plugin through Plugins > Add New, or extract it into `wp-content/plugins/`. 2. Activate Accessibility Fixer for WooCommerce. 3. Open WooCommerce > Accessibility Fixer in the admin menu. 4. Read the short notice and select “I have read and understood.” This unlocks the fix switches; scanning works either way. 5. Run your first scan. It takes a few minutes on a typical store. 6. Read the report, try a fix in preview, and turn on the ones you want. Check the manual list for what still needs a human look. ## FAQ ### Does this make my store meet an accessibility law or standard? No. Accessibility Fixer finds and fixes some common, well-defined issues in your store’s code, and lists everything else that needs a manual check. No plugin, and no automated tool of any kind, can put a store fully in line with an accessibility law or standard on its own. Treat the report as a helpful starting point, not a finish line. ### Is this legal advice? No. Accessibility Fixer is not a law firm and does not provide legal advice. If you need to know exactly what a law requires for your store, talk to a qualified professional. ### Does it change my theme files or database? No. Accessibility Fixer never writes to your theme files, your plugin settings, or your database content (products, orders, pages, posts). Its own settings and scan history live in the plugin’s own database tables and a couple of WordPress options, and those are removed when you uninstall the plugin (see Privacy below). ### Does it touch checkout, cart, or account pages? Accessibility Fixer scans checkout, cart, and account pages — those pages have some of the biggest accessibility gaps in a typical store — but it never applies a fix to them. A mistake in that part of the buying journey could stop a sale, so issues found there are reported only, with instructions for a manual fix in your theme. ### Does it add anything to my checkout by default? No. By default, cart and checkout are scanned empty, with nothing added to any cart. There is an opt-in, off by default, to add one existing product to your own admin session so the real checkout form can be scanned; Accessibility Fixer warns you that other plugins may react to a cart change, and it removes the product automatically when the scan finishes. If you close the tab while the scan is still running, the product stays in your cart until you next open the Accessibility Fixer panel, which then removes it. ### Does it send data anywhere? No. Scanning runs in your own browser using axe-core, which ships inside the plugin. Accessibility Fixer makes no calls to any external service and collects no telemetry. The only identifying information it stores is which admin user acknowledged the notice or switched on a fix, and when — kept on your own site. ### Does it work with caching plugins? Accessibility Fixer asks WP Rocket and LiteSpeed Cache to clear a page after you switch a fix on or off, and shows a warning for other caching layers it cannot reach directly (a CDN, for instance). After every change it also re-fetches the live page without any login credentials and checks that the fix is actually present in what a visitor would receive — so a stale cache shows up as “enabled, not verified” instead of silently doing nothing. ### What can it actually fix automatically? Four things, each with its own on/off switch: a missing or invalid page language attribute, a duplicated or empty page title, a missing skip-to-content link, and links or buttons that have no accessible name but where one can be determined with certainty (for example from an image’s existing alt text or a linked product’s name). Nothing is ever guessed or invented — if Accessibility Fixer cannot be sure, it reports the issue instead of fixing it. ### Why does the summary always say “N issues… M manual checks”, never a score or a percentage? Because a single score invites people to mistake it for a certification. Accessibility Fixer intentionally shows no badge, no percentage, and no pass/fail grade — only what was found, what was fixed, and what still needs a person. ### Will a fix slow down my store? Each fix measures the time it adds to a page. If the average across recent requests goes above 20 milliseconds, that fix automatically suspends itself until you re- enable it, so a slowdown cannot go unnoticed. With no fix turned on, Accessibility Fixer adds nothing to your public pages at all. ### Which themes and WooCommerce versions are supported? Storefront, Twenty Twenty-Four, and Twenty Twenty-Five are directly supported for fixes. On other themes, scanning always works; each fix checks compatibility before doing anything, and reports “theme not supported” instead of guessing. WooCommerce: the two most recent major versions are supported. ### What happens if I uninstall the plugin? All Accessibility Fixer database tables and settings are removed. The log of who acknowledged the notice and when is kept by default, in case you reinstall later, but you can choose to delete it too, in Settings. ### Where can I get help? Through the plugin’s support forum here on WordPress.org. We aim to reply within two business days. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Silicon Sicily Accessibility Fixer for WooCommerce” is open source software. The following people have contributed to this plugin. Contributors * [ siliconsicily ](https://profiles.wordpress.org/siliconsicily/) [Translate “Silicon Sicily Accessibility Fixer for WooCommerce” into your language.](https://translate.wordpress.org/projects/wp-plugins/silicon-sicily-accessibility-fixer) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/silicon-sicily-accessibility-fixer/), check out the [SVN repository](https://plugins.svn.wordpress.org/silicon-sicily-accessibility-fixer/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/silicon-sicily-accessibility-fixer/) by [RSS](https://plugins.trac.wordpress.org/log/silicon-sicily-accessibility-fixer/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.0 * First release: scanning of six store pages, origin reporting, four in-code fixes with preview and verification, manual checklist, scan history and comparison. ## Meta * Version **1.0.0** * Last updated **2 days ago** * Active installations **Fewer than 10** * WordPress version ** 6.9 or higher ** * Tested up to **7.1.3** * PHP version ** 7.4 or higher ** * Tags * [a11y](https://wordpress.org/plugins/tags/a11y/)[accessibility](https://wordpress.org/plugins/tags/accessibility/) [ada](https://wordpress.org/plugins/tags/ada/)[wcag](https://wordpress.org/plugins/tags/wcag/) [woocommerce](https://wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://wordpress.org/plugins/silicon-sicily-accessibility-fixer/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/silicon-sicily-accessibility-fixer/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/silicon-sicily-accessibility-fixer/reviews/) ## Contributors * [ siliconsicily ](https://profiles.wordpress.org/siliconsicily/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/silicon-sicily-accessibility-fixer/)