WooCommerce plugin: reading aids that match your shop

Accessonaut for WooCommerce 1.2.0 requires WordPress 7.0 or later, active WooCommerce 11.2.2 or later and PHP 7.4 or later. PHP 8.3 is recommended. You also need an Accessonaut account and a project for your shop domain. The standard WordPress plugin is optional.

Installation is via the ZIP file. This does not claim that the plugin is published on or approved by WordPress.org or the WooCommerce Marketplace.

1. 1Make a backup and prepare a test copy of your shop. Check the requirements and activate WooCommerce.
2. 2Open Plugins → Add New Plugin → Upload Plugin, upload the ZIP file and activate Accessonaut for WooCommerce.
3. 3Open WooCommerce → Accessonaut. Enter the HTTPS service address and the public project ID from your project. Secret API keys do not belong in these fields.
4. 4Choose the central project design or style the widget locally. Open the live preview explicitly when you want to load it.
5. 5Check the area selection and the notes on the external service. Only then switch the widget on and save.
6. 6Clear page and CDN caches. Check the public shop, mobile views and the purchase journey before you move to your live shop.

Go to the detailed WooCommerce installation guide

After installation, the widget is switched off. For the later embed, shop overview, product pages, product categories and product tags are preselected.

Cart, checkout and customer account are deselected at first. You can enable each of these areas separately and then check them with your theme, your blocks and your payment providers.

Order confirmations and pages for paying an order that already exists always stay excluded from the WooCommerce embed. The area selection does not lift these exclusions.

Start with one of five templates and adjust colours, font, menu width, corners, shadows, texts and the opener. Separate edge spacing is available for smartphone and desktop. Use your central project design or manage the display directly in the WooCommerce plugin.

Your visitors’ personal reading settings take priority. Colour contrasts that are too low are adjusted when displayed. Design options are also available on the Free plan; there the Accessonaut brand link stays visible.

The WooCommerce plugin works on its own. If you also equip editorial pages with the standard WordPress connector from version 1.2.0, the WooCommerce plugin handles the shop areas. The standard connector handles all other pages. This way, the WooCommerce plugin’s own activation and area settings apply in the shop.

Remove additional embed codes from the theme or tag manager and check that at most one widget appears. The plugins do not interfere with the order or payment logic.

Only after you explicitly activate it do visitors load the widget and the project configuration from the Accessonaut service. The preview in the admin area is also only loaded when you click.

For the configuration, the WooCommerce embed only uses the website origin, that is protocol, hostname and, if applicable, port. Full page addresses and their parameters are not transmitted for this. Widget requests are sent without a referrer. Alt-text assignments and the private browser assistant are not loaded in WooCommerce mode.

When the connection is established, the service still receives the IP address and usual browser request data. Personal display preferences can be stored locally in the browser. Cover these processes in your privacy notice and check the linked terms of your configured service address.

• Operate navigation, product variants, quantity selection and “Add to cart” entirely with the keyboard.
• Check the mini cart, dialogs and their focus. After closing, visitors should not lose their place.
• Check the classic or block-based cart and checkout you actually use. If you run both variants, test both.
• Test form labels, error messages, shipping and payment selection and embedded payment fields. Use your test shop and test payments for this.
• Make sure the widget does not cover any buy buttons, cookie banners or focused fields. Check the customer account and the excluded order pages separately.

Reading aids complement the work on accessible content and processes. They do not fix faulty checkout logic and do not prove full WCAG or legal conformance. External payment fields and third-party frames need their own checks.