How accessible is your website?Start free check
Documentation

Display problems and conflicts

Fix two buttons, a covered chat button, the wrong widget language or a page builder that drops the code, and see why your website looks different.

Updated October 28, 2026

The widget shows, but something looks wrong or clashes with another part of your website. Here are the usual cases.

Your website looks different

allyWay changes how your website looks only when someone switches on a tool in the widget – and then only in that person's browser – or when you approve a visible change in the Report. Most often you tried a tool while testing.

  1. Look in a private window

    Open your website in a private (incognito) window. Looks normal there? Then only your browser is affected.

  2. Reset the widget

    In your normal browser, open the allyWay widget and click Reset settings.

  3. Look for another tool

    Still different in a private window? Remove any other accessibility tool still installed.

AI fixes – image descriptions and names for screen readers – don't change how your website looks. Visible changes you approved, such as a stronger text color, show for every visitor. In Report › Fixed by AI, click View next to the issue, then See every change – Change back takes one off from the next page load on. A fix that would start to show after your website changes is paused at the next check – See paused fixes on the Report lists them.

Two buttons on your page

Your page most likely has two accessibility tools, or two different allyWay codes, such as an old and a new one. Search your page's source for "loader.js" and for other accessibility tools. Compare each allyWay code with the one on Installation, with the right website selected. Remove any other allyWay code, and the other tools' code or plugins. Then clear your cache and check again in a private window.

The same allyWay code twice on one page shows only one button. We recommend only one accessibility widget: two can change the same things at once and work against each other.

  1. Open Widget position

    Open Design (the page is titled Appearance) and find the Widget position card.

  2. Choose the device

    Click the tab where the overlap happens: Desktop, Tablet or Mobile. Each has its own position and distance.

  3. Move the button

    Pick another spot, for example Bottom left, or move the sliders under Distance from edge (up to 100 px).

  4. Save

    Click Save changes at the top right and reload your website.

The button sits on top of other page elements, so on small screens it can cover a cookie banner's buttons. Check your website on a phone after moving it.

The widget shows the wrong language

The widget starts in the language a visitor picked before. Otherwise, with Auto-detect page language on, it uses your page's language if available – else your Default Language.

On Design, in the Language card, set Default Language to the language most of your visitors read. For a multilingual website, turn on Auto-detect page language, and under Display Options switch on the languages you need. Click Save changes, then test in a private window, so no language you picked earlier is remembered.

Auto-detect follows the language each page declares in its code. If every language version declares the same one, ask your developer to set the right language on each page. See Set the widget languages.

Visitors' settings stay on

That's normal: the widget remembers each visitor's choices, so they don't switch on bigger text again on every page. They're stored only in that visitor's browser – not on our servers, not in cookies – and separately for www.example.com and example.com. Reset settings in the widget turns everything off.

The code is in a page builder block

An Elementor "HTML" widget, a Divi "Code" module or a "Custom HTML" block adds the code to that one page only – and a normal text block shows it as text. Remove it there and add it site-wide, for example with the WPCode plugin: open Code Snippets › Header & Footer, paste the code into Footer and click Save Changes. Then clear your cache and check a few pages.

  • Elementor Pro: Elementor › Custom Code › Add New Custom Code, location <body> – End, condition: your entire site.
  • Divi: Divi › Theme Options › Installation – paste it into Add code to the < body > and switch on Enable body code.
  • Block editor: only administrators and editors may save scripts (on a multisite network, only super admins).

The widget disappears in a single-page app

The code is probably inside a component your app removes when visitors navigate. Add it once to your app's main HTML page, for example index.html or the root layout. The widget then stays across all your app's pages.

Browsers and page speed

The widget is built for Chrome 87, Edge 88, Firefox 78 and Safari 14 or newer, on computers and phones – not for Internet Explorer. A tool that needs a feature the browser lacks shows "Not supported".

The code is a small script that waits until your page's content is ready, then loads the widget in the background. Speed test tools such as Lighthouse may list it as "third-party" code. Don't use "delay JavaScript until interaction" for allyWay. See Supported platforms and technology.

Check that it works

Open your website in a private window on a computer and a phone: one allyWay button, in the right spot and language.

Still stuck?

Our support team replies within a few hours.

Contact support

Installation helper

Step-by-step setup guides for your platform.

Open the helper