CoderEmbassy AWAC — Accessibility for WooCommerce

By Saleh Ahmad

0+ active installationsVersion 1.0.3

Find accessibility problems in your WooCommerce store. Local scans, saved evidence and manual checks. No overlay, no data sent out.

Description

AWAC helps you find and track accessibility barriers in your WooCommerce store, so you can fix them.

It scans your shop, product, cart and checkout journeys on your own server, shows you exactly what it found and where, and gives you a checklist for the things a scanner cannot judge. Everything stays on your site.

Be clear about what it is. AWAC reports what it observed and what it could not check. It does not claim your store is legally compliant, fully conformant or “WCAG certified”, and it does not give you a compliance score. Automated checks only cover part of WCAG; a person who understands accessibility still needs to review your store.

No overlay. AWAC does not add an accessibility widget or overlay to your storefront.

What you get

  • Audit your WooCommerce journeys. Same-site scans of an initial set of pages in your store.
  • Local checks. The axe-core engine plus WooCommerce-aware rules, run on your own server.
  • Issues. A list of problems with the evidence behind each one, so you can see what to fix.
  • Manual checks. Human review checklists for what automated tools cannot judge.
  • Reports. Printable, readable reports of your findings.
  • History. Redacted excerpts, lifecycle history, dismissal notes and retention controls.
  • Accessible admin. Keyboard navigation, focus management, dark mode and semantic reports.
  • Safe by design. A safe-mode boundary for remediation features. Scan links are short-lived and same-site.

Privacy

AWAC does not send scanned page content or accessibility findings to CoderEmbassy or to any scanning service.

Scan evidence is stored locally for the retention period you set. AWAC checks daily through WordPress cron and deletes expired scan runs, pages, occurrences and issue evidence that is no longer attached to a retained occurrence. Cleanup runs when WordPress cron is triggered by site traffic. Reversible remediation history is kept because its recorded “before” state may still be needed to undo a change. Uninstalling keeps your evidence unless you explicitly enable permanent removal in wp-config.php.

Installation

  1. Install and activate WooCommerce.
  2. Upload the plugin to /wp-content/plugins/, or install it from Plugins → Add New.
  3. Activate CoderEmbassy AWAC.
  4. Open WooCommerce → AWAC, review Settings, then start with an Audit.

FAQ

Does AWAC make my store compliant?

No. AWAC helps you identify and track accessibility barriers. Automated checks cover only part of WCAG, and a human evaluation is required.

Does AWAC use an overlay?

No. AWAC does not add an accessibility overlay or widget. Any remediation is targeted, reversible and subject to the plugin’s safety controls.

Does scanning place orders or contact payment gateways?

No. The scan runner uses isolated session handling. It does not submit a real order and does not capture payment-iframe content.

Does AWAC send my pages or results to an outside service?

No. Scanning and storage happen on your own site. Nothing is sent to CoderEmbassy or to a scanning service.

Where are the results kept, and for how long?

In your own WordPress database, for the retention period you choose in Settings. Expired scan evidence is deleted daily through WordPress cron. Uninstalling keeps the evidence unless you enable permanent removal in wp-config.php.

Do I need WooCommerce?

Yes. AWAC is built for WooCommerce shopping journeys and requires WooCommerce to be active.

Screenshots

Changelog

1.0.3

  • Clearer wording on the Audit screen.
  • Fixed: evidence for WooCommerce variation findings now shows as readable code instead of escaped text.
  • Fixed: the Dashboard counts now refresh after a scan without reloading the page.

1.0.2

  • Adjusted ARIA attributes in the admin screens.

1.0.1

  • Preserves reversible remediation history when expired scan evidence is removed.

1.0.0

  • Initial release.
  • Enforces the configured scan-evidence retention period with daily local cleanup.