The widget is configured for each website. A feature can be unavailable because it is disabled, needs prepared content, depends on the browser, or is not offered on the current device.
First distinguish a missing control from a visible control that cannot provide a result. They often have different causes.
A control is missing
Open the relevant panel section and check the available options. The website owner decides which settings, profiles, and helpers appear.
In the default mobile interface, Big Cursor, Magnifying Glass, and Dictionary are hidden. These tools use pointer-oriented interactions. Their absence on a phone does not necessarily indicate an installation problem.
Two websites using SimplifyAccess may intentionally offer different controls.
A reading tool opens but has no content
Easy Language and Plain Language depend on prepared alternatives for the current page. Page translation and video captions also need corresponding prepared content.
Enabling a capability does not create that content. An alternative available on one page may be absent on another.
Simplified Page works differently: it extracts supported existing content into a reading view. If that view is empty, allow the original page to load and try again.
A feature changes only part of the page
The widget works with content it can identify and access. Text inside images, embedded third-party services, and complex custom components can behave differently from ordinary page text.
Prepared simplified or translated text also needs to match the current content. If the website was recently rewritten, its alternatives may need updating.
Read Aloud is silent
Check the device volume and browser mute state, then start playback directly from the player. Try a normal paragraph. Available voices and speech behaviour depend on the browser and device.
See Listening to Content with Read Aloud.
Voice commands do not respond
Check microphone permission and the phrases shown in Commands. Speech recognition must be supported in the current environment. Interface-language availability does not guarantee an identical voice-command set.
See Navigating with Voice Commands.
A change produces an uncomfortable result
Turn off the last adjustment or select Reset. Try settings individually before combining them. If a script-driven page component remains affected after disabling motion controls, reload the page with those controls off.
Information to give the website team
Include the page address, feature name, device and browser, the action you tried, and what happened. Mention whether the control was missing, an error appeared, or the result was incomplete.
For website owners
Check the correct controller, its enabled capabilities, visible settings, and prepared page content. Save the configuration and account for cached settings when reviewing changes.
See Opening and Navigating Widget Settings and How Widget Changes Reach Your Website for the configuration workflow.