The installed embed script connects the website to a specific SimplifyAccess controller.
The controller provides the widget with its current appearance, settings, profiles, tools, additional capabilities, and prepared content.
For routine configuration changes, the embed code does not need to be replaced.
The core widget and optional capabilities
The widget has a core that provides its interface and most basic accessibility settings.
Additional capabilities are stored in separate files or plugin classes. The widget loads them only when they are enabled for the controller.
A configuration with no additional capabilities therefore requires less code than one using Audio, Easy Language, Code Fix, Keyboard, Read Aloud, Smart Contrast, Video Transcription, and the other optional functions.
This allows each website to use a configuration suited to its needs instead of loading every possible function.
Visible and background functionality
An enabled capability does not always create a new item in the widget.
It may:
- Add a visitor-facing control
- Support an existing setting
- Provide an expandable set of options
- Connect prepared content with the website
- Change behavior in the background
As a result, the absence of a new menu item does not necessarily mean that an enabled capability is inactive.
Saved settings are retrieved by the website
After you save a configuration, the connected website retrieves the current controller settings.
The installed script uses the Controller ID to determine:
- Which settings are available
- Which profiles are enabled
- Which tools should appear
- Which optional files must be loaded
- Which appearance configuration should be used
- Which prepared content belongs to the website
Each website must therefore use the embed code generated for its own controller.
Configuration caching
Widget settings are cached in the visitor’s browser for approximately one hour.
Caching reduces repeated requests and helps the widget load efficiently when a visitor opens several pages.
It also means that a browser which recently visited the website may continue to show the previous configuration for a short period.
To review a recent change, use:
- A new private browsing window
- A different browser
- A different device
- A new test after the cache has expired
Replacing the embed script is not necessary for a normal configuration update.
Enabling a feature does not create its content
Some visitor functions depend on content prepared in the platform.
For example:
- Easy Language needs suitable simplified content.
- Text Simplification needs processed page content.
- Video Transcription needs a completed transcription.
- Language Selection needs content in the corresponding languages.
The configuration decides whether the function is available. The content workflow determines what it can show.
Disabling an additional capability
When an optional capability is disabled, its separate code should no longer be loaded after the widget receives the updated configuration.
Related controls or background behavior may also stop being available.
Before disabling a capability, consider whether it is used by:
- An enabled accessibility setting
- An accessibility profile
- A visitor-facing tool
- Prepared content already offered on the website
Test the widget afterward to confirm that the remaining configuration still works as intended.
When a change does not appear
Check that:
- The changes were saved.
- The correct controller was edited.
- The website uses that controller’s embed code.
- The required capability is enabled.
- Any required content has been prepared.
- The browser is not using a cached configuration.
- The domain matches the controller.
- The Browser Cache is cleared, including indexeddb.
When the widget itself does not load, review the installation and connection status instead of the feature configuration.