How accessible is your website?Start free check
Documentation

Corrections without AI

Which wrong settings in your page's code allyWay corrects by itself – free and without AI – how each is tried first, and how to undo one.

Updated October 23, 2026

Some problems our check finds come from a setting in your page's code that is clearly wrong – a typo, an outdated name or a value browsers don't understand. allyWay corrects these by itself, without AI and for free. Screen readers, the keyboard and visitors' own settings then work as intended, and your website looks the same.

Before you start

  • An active plan. The free trial has no fixes – also none without AI.
  • allyWay installed on your website: the corrections go live through allyWay's widget.

What allyWay corrects

What our check finds What allyWay does
A role – what an element is for screen readers – that is misspelled or outdated Uses the role that was meant: "nav" → "navigation", "directory" → "list".
A misspelled setting for an element's name or description Corrects it – aria-labeledby → aria-labelledby, aria-lable → aria-label – only when what it holds fits.
role="text" around links or buttons, or "decoration" on an element that can still be used Removes it.
A heading role without its level Gives it level 2.
A property that doesn't belong to an element Takes it off – never a state your website's scripts set, such as open or checked.
A label on an element that may not have one, for example a page builder that names its plain boxes after their module ("Separator", "Photo") Takes it off – never on an element with a role of its own or one the keyboard reaches.
A tabindex above 0 Sets it to 0, so the Tab key follows the order of the page.
A keyboard shortcut (accesskey) used twice Removes it from the first element.
An area that scrolls but can't be reached with the keyboard Makes it reachable with the Tab key.
Hidden content the Tab key still reaches, such as a slider's copies or a closed menu Keeps it out of the Tab order while nobody can see it.
A whole page hidden from screen readers, often by a pop-up or cookie script Shows it to screen readers again.
Headings that skip a level Announces such a heading one level below the heading it belongs to, on every page – also headings added later.
A language code browsers don't know Uses the code that was meant: "en_US" → "en-US", "german" → "de".
A table header direction that doesn't exist, a summary that repeats the caption, or cells pointing to missing headers Corrects the direction ("column" → "col") or removes what is wrong.
List items outside a list Makes their plain container the list.
A list whose items each sit in an extra box, for example the sharing buttons of a Wix shop Makes those boxes the list's items, so screen readers hear one list with all its items.
A note inside a list besides its items, for example a closing line after the steps of a guide Makes the note one of the list's items for screen readers.
An image description that repeats the text next to it, for example a logo link "Kivano" with an image described as "Kivano" Makes the image decoration, so screen reader users don't hear it twice.
An image that shows no picture because its address is empty, for example a team member without a photo Lets screen readers skip it while it has no picture. Once your website gives it one, the AI describes it.
A footer inside a quote or a figure, for example the quote's source, that browsers announce as a second footer of the page Lets screen readers read it as part of the quote – your page's own footer stays its only footer.
A side box inside another part of your content without a name of its own, such as a list of topics next to a docs page Marks it as a plain part of the page – what browsers already make of it.
An empty form label, or a form field whose only label is its placeholder Fills the label with the field's name as text only screen readers hear, or uses the placeholder as the field's label.
Text spacing your page locks with "!important" Keeps the same spacing without the lock, so visitors' own settings can change it.
A link or button too small to tap Makes its tap area bigger into free room around it, without anyone seeing it. Where there's no room, a size of at least 24 × 24 pixels waits for your OK.
A card that only acts like a button and holds one link Makes it stop acting like a button, so screen readers and the keyboard find the link once.
A "back to top" link without a name people see or without its target Gives it what's missing – a name in your page's language or a target at the top of the page – and takes the keyboard to the top with it.

Free, tried first and watched

  • Corrections use none of your AI fixes and don't count toward the daily limit, so allyWay makes them even when no AI fixes are left this month.
  • Before a correction can go live, allyWay tries it on your real page during a check: nothing visitors see may change – also with the mouse over the element or the keyboard focus on it – the problem must be gone, and no new problem may come up. Otherwise allyWay leaves the place to you, and the Report says why.
  • The widget changes exactly the wrong value and nothing else. If your website's own script later changes that value, allyWay lets go of it – except for a whole page hidden from screen readers. Every check also pauses a correction that would now change how something looks.
  • On the Report page, corrections count under Fixed by AI, like every fix allyWay makes by itself – even though no AI is involved.

Undo a correction

  1. Find the correction

    On the Report page, find the correction among what allyWay fixed. Its title says what allyWay corrected, for example "Corrected a role for screen readers", and the line below shows the change, for example "role “nav” → “navigation”".

  2. Click Change back

    allyWay's widget stops making it from the next page load on. A correction has no text, so there's no Edit. Its places count as open again, and allyWay doesn't make the correction again without your OK.

  3. Bring it back if you like

    Click Use AI version on the same row. Changing back and bringing back are free.

The heading levels and showing a whole page to screen readers are each one correction for every page: changing one back changes it back everywhere.

Check that it works

After a check with allyWay installed, the corrections show on the Report page under Fixed by AI. The lasting fix is still to correct the value in your website's code – the next check notices it.

Why does a place say "allyWay doesn’t correct this one"?

Trying the correction on your page – or, for a correction made on every page, on another page – showed that it isn't safe or isn't enough there; for example, your website draws a frame around a scroll area when it's clicked. The place stays with your website, with steps to fix it yourself, and every check that finds it tries again.

Why does the Report find more problems after a correction?

Once a page that was hidden from screen readers is readable for them, our check can read its content too. Problems in it now show up – they were there before; the correction didn't cause them. So your number of places can go up and your score down.

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