Accessonaut – Accessibility Widget & Reading Aids

Yes. The free plan covers one website with all reading aids and design options and shows a small credit link in the widget menu. It includes a monthly volume of widget views; if your website reaches it, the widget keeps working and you get a notice in your account. Paid plans add more websites, larger scans and monitoring and remove the credit link.

Yes. The widget is provided by the Accessonaut service, and the plugin needs the public project ID of your website. Creating a free account takes a few minutes.

No. No widget can do that. Accessibility laws such as the German BFSG and the European Accessibility Act refer to requirements like WCAG, and they are met by the website itself: alternative texts, a logical heading structure, sufficient contrast in your theme, forms with labels and menus that work with the keyboard. The reading aids are an additional help for your visitors. What helps: check your website with automated scans and a manual test, fix the problems at the source and publish an accessibility statement. Your Accessonaut account supports all three steps.

The widget sets no cookies; reading preferences stay in the visitor's browser. Loading the widget transmits the usual request data, such as the IP address, to the Accessonaut service, which is operated from Germany and hosted in the EU. Usage notices are anonymous and are not sent with Do Not Track or Global Privacy Control. Whether you load the widget before or after consent is your decision based on your own privacy assessment; mention the service in your privacy policy. All requests are listed under "External services".

The plugin adds a single deferred script tag in the footer and nothing else, so it does not block the rendering of your pages. Without an enabled connection it adds nothing to your pages at all. It makes no server-side requests and stores only its own small settings.

Yes. The plugin outputs its script through wp_footer(), which block themes, classic themes and page builders such as Elementor or Divi use. After changing the settings, clear your page and CDN cache. If a caching plugin delays JavaScript until the first interaction (for example "Delay JavaScript execution" in WP Rocket), the widget button appears late; exclude widget.js from that option if it should appear immediately.

Yes. You can activate the plugin for the whole network or for single sites. The settings are stored per site, so the widget stays off on every site until you enter the service address and project ID there. If a site has its own domain, create a separate project for it in your Accessonaut account. Deleting the plugin removes its settings on all sites of the network.

No. Only the public project ID and the service address are embedded. Never paste credentials or private API keys into these fields.

Yes. Save a trusted HTTPS service address and click the preview button. Only this click loads the administrator preview. It shows the current local form, including unsaved changes, and always includes the free-plan credit link. Check the central design in your Accessonaut account or on the published website.

No. The local design only controls the appearance. A paid plan removes the credit link, and functional settings stay in your Accessonaut account.

Install the plugin from the directory and activate it. Versions up to 1.3 were installed in the folder "inclusiveweb": the new version switches that copy off and keeps your settings; then delete the deactivated old entry. Versions 1.4 and 1.5 update as usual.