What you need
A published Wix website with a connected domain and access to custom code. In Accessonaut, first create a project with your actual website domain and open the installation page in the project.
Step by step
- In your site dashboard, open Settings → Custom Code.
- Add a new entry and paste the embed code. Give it a clear name, for example Accessonaut.
- Choose all pages and placement at the end of the body. Load the script once per document.
- Apply the change and test the published domain, page changes and mobile views.
What the embed looks like
Use the ready-made code from your project. The example needs your real project ID and the publicly reachable service address.
<script src="https://accessonaut.com/widget.js"
data-project-id="YOUR_PROJECT_ID"
data-language="en" defer></script>Match the design to your website
In your Accessonaut project, open “Reading-aid widget”. Five templates and a live preview help you with the design: colours, fonts, menu width, corners, shadows, an icon or labelled opener and your own texts. Position and edge spacing can be set separately for desktop and smartphone. After saving, your existing embed code picks up the project design automatically; the public configuration is cached for up to one minute.
In the WordPress plugin you can choose local settings instead. These take priority over the project design. Design options are available on all plans. On the Free plan, the Accessonaut notice stays visible. Your visitors’ personal reading settings take priority over design defaults.
Keep in mind
Use the global custom code. An HTML embed in an isolated iframe cannot adapt the surrounding Wix website. Align the integration with your privacy and consent settings.
Common questions about Wix
What requirements does Wix list?
According to Wix, the site must be published and have a connected domain. A connected domain requires an active Premium or Studio plan. If you change the domain later, Wix deletes your code snippets. Add the code again and update the domain in the Accessonaut project.
Should the code load once or on every page?
Wix lets you choose whether the code loads only once per visit or on each page your visitor opens. Choose loading once for the widget. If the script does run again, the widget does not create a second instance when it is already on the page. Still, check several page changes.
Does the widget load before cookie consent?
Wix categorises custom code as essential by default. It then loads before consent and cannot be disabled. On the Code Type tab you can choose another category, such as Functional. The widget then only loads after consent. The widget sets no cookies and stores reading settings locally in the browser. Decide based on your privacy assessment.
Why can’t I see the widget in the editor?
According to Wix, custom code does not take effect in the editor and only runs on the published site. So always check the widget on your domain.
If something does not work
The widget disappeared after a domain change.
Cause: Wix removes code snippets when you change the domain.
Fix: Create the entry under Settings → Custom Code again and enter the new domain in the Accessonaut project.
The widget only appears after a click in the cookie banner.
Cause: The code is assigned to a category that requires consent.
Fix: That is the result of your setting. Check on the Code Type tab whether it matches your privacy assessment.
You want to remove the widget.
Cause: The entry loads on all selected pages until you delete it.
Fix: Delete the Accessonaut entry under Custom Code and then check the live site.
Check the installation
- Open the public website in a private window. The widget appears exactly once.
- Reach the button with the keyboard. Open the panel, change the text size and close it again.
- Check the homepage, a subpage, a form and the mobile view. The widget must not cover any important controls.
- In the Network tab, check that widget.js and the project configuration load from your service address. If there are errors, check the domain, project ID and CSP.
- For Free projects, the visible Accessonaut notice remains part of the widget. Permissions come from your project.
Privacy and limits
When it loads, the visitor’s browser fetches the script and the project configuration from the Accessonaut service. This involves the IP address, browser request data and the website hostname. Display preferences are stored locally in the browser. Cover the integration in your privacy notice and check your specific configuration.
The reading aids do not guarantee conformance. Also check barriers in the source code and complete user journeys, both automatically and manually.