Limitations

The widget changes how a page is displayed for one visitor. It doesn't make a site compliant with ADA, EAA, EN 301 549 or WCAG, and installing it is not a legal defence. Regulators act against products that claim otherwise, such as the FTC's 2025 order against accessiBe.

• Missing alt text, form labels, headings, keyboard support and contrast in your own design still need fixing at the source.
• Don't advertise the widget as a compliance solution, and don't present it as one in your accessibility statement.

Some parts of a page are out of the widget's reach.

• Cross-origin iframe elements (embedded video, maps, payment forms) and closed shadow roots: browsers keep every script out of them. Same-origin iframes and open Shadow DOM are adjusted.
• “Stop animations” stops CSS, script and SVG animations; GIFs, canvas and animation that scripts draw frame by frame keep moving.
• The launcher steps aside when keyboard focus lands on a control under it (WCAG 2.4.11), but still covers its corner for mouse and touch users: keep that corner free, or move it with offset.

Some adjustments trade precision for safety.

• “Page zoom” uses CSS zoom, which doesn't trigger your media queries. Browser zoom reflows better: suggest it in your accessibility statement.
• “Line spacing” sets a line height of 1.5 times the chosen percentage on all text.
• Letter spacing is not applied to Arabic and other joined scripts (it would break the letters apart); word spacing still is.
• Color modes override backgrounds and remove background images, except on form controls, links and buttons. Decorative icons drawn as background images elsewhere disappear.
• Text size measures each element's size once. If your app later changes an element's font size through a class change, it keeps the earlier size until the page reloads.
• Color adjustments apply to the screen only, not to printing.

Chrome and Edge 120+, Firefox 126+ and Safari 16.4+ (desktop and mobile) get every feature; older versions lose single features, such as page zoom. CI runs the end-to-end tests in Chrome only; Firefox and Safari rest on feature support and manual testing.