The Widget Settings page separates features into four areas:
- Accessibility Settings
- Accessibility Profiles
- Accessibility Plugins
- Accessibility Tools
These groups are useful for configuration, although the technical boundaries are not always visible to website visitors.
Accessibility settings adjust the experience
Settings are the individual controls visitors use to change the page or activate assistance.
They cover several different needs.
Text and readability
- Font Size
- Line Height
- Letter Spacing
- Dyslexia Typo
- Text Simplification
Visual presentation
- Contrast
- Color invert
- Saturation
- Remove Images
- Disable Animations
Orientation and interaction
- Highlight Links
- Big Cursor
Reading and audio
- Audio
- Read Aloud
Most of these functions belong to the widget’s core or are provided by a core component. They do not require every optional capability to be loaded.
Smart Contrast and simplified-language functionality are different: they depend on their corresponding additional capabilities.
Profiles combine several settings
Profiles are presets rather than separate technical features.
Selecting a profile can activate a group of suitable settings together:
- Epileptic
- Visual Impaired
- Easy Language
- Concentration
- Smart Screen
- Color Deficiency
A profile does not create a new accessibility function by itself. It coordinates functionality already available to the controller.
For example, a profile that relies on an optional capability can only provide the intended experience when that capability is enabled.
Tools provide focused visitor functions
The tools area controls functions that visitors can open for a particular task:
- Magnifying Glass
- Page Structure
- Simplified Page
- Dictionary
A tool may present its own view, interaction pattern, or language setting. This makes it different from a simple toggle such as increasing font size or highlighting links.
Additional capabilities extend the core widget
The area currently named Accessibility Plugins controls separately loaded capabilities:
- Audio
- User Guide
- Language Selection
- Easy Language
- Code Fix
- Keyboard
- Read Aloud
- Smart Contrast
- Video Transcription
These functions are implemented as separate files or plugin classes. They are loaded only when enabled for the controller.
This modular approach has two practical consequences.
A smaller configuration loads less code
When no additional capabilities are enabled, the widget uses a smaller code base and has less functionality to initialize.
Each enabled capability adds code and may add further processing. Some additions are small, while more complex functions naturally require more.
Enabling every available option is therefore not automatically the best configuration. The better approach is to enable the functions that are genuinely useful for the website and its visitors.
Not every capability appears in the widget
An enabled capability can behave in different ways:
- It may add a new control to the widget.
- It may support an existing accessibility setting.
- It may provide additional options for another feature.
- It may process the website in the background.
- It may connect prepared platform content with the visitor interface.
This is why “plugin” can be a confusing customer-facing term. It describes how the software is organized, not necessarily what the visitor sees.
Beta features
The current interface marks these capabilities as beta:
- Audio
- User Guide
- Video Transcription
Beta functions are available for use but may still be refined. They should be tested carefully on the connected website before being made part of an important visitor workflow.
How the groups relate to one another
A single visitor feature can involve more than one area.
For example:
- A capability may first need to be enabled.
- Its visitor-facing setting must also be available.
- A profile may activate that setting automatically.
- The feature may require prepared content or a selected language.
- The visitor ultimately uses it through the widget.
This relationship is intentional. It allows website owners to control both the technical capabilities being loaded and the choices presented to visitors.
A practical configuration principle
Start with the core settings that are useful for most visitors.
Then add profiles, tools, and optional capabilities according to the actual website:
- Enable Language Selection when multiple prepared languages are available.
- Enable Easy Language when simplified content has been prepared.
- Enable Video Transcription when processed media content is available.
- Enable Read Aloud when spoken page access should be offered.
- Enable Smart Contrast when dynamic contrast adjustment is appropriate.
- Enable background capabilities only when their behavior is wanted.
After each group of changes, save the configuration and test the connected website.