Free, tests the published page

Wix Accessibility Checker

Scan a published Wix page and see which accessibility issues come from your template, your editor elements, your apps or your images, and where in the Wix Editor to fix each one.

Templates
Text and heading tags
Images and galleries
Buttons and menus
Forms
Apps and widgets

Each page is rendered in a real browser and tested with axe-core against the machine-testable WCAG 2.2 Level A and AA success criteria. Automated testing does not replace a manual accessibility review.

The same checker, for Wix sites

This page runs the free TagPipes Website Accessibility Checker: one page address, loaded in a real browser, tested with axe-core against the machine-testable WCAG 2.2 Level A and AA success criteria, reported in plain language. What is different here is the explanation around it, written for Wix sites.

Where accessibility issues come from on a Wix site

A Wix page is a template plus every element, app and image added in the editor. The scan sees the published page; knowing the layers tells you what to change.

1. The template

Header, menu, footer, fonts and the color palette. A template chosen for its look can carry low-contrast text, decorative headings in the wrong order and icon-only social and menu buttons onto every page.

2. Elements added in the editor

Text elements each carry an HTML tag (paragraph or heading level) set in the text settings. Buttons, image links and containers need names and, where they act as landmarks, the right tag. Free placement can also make the visual order and the reading order disagree.

3. Apps from the Wix App Market and third parties

Bookings, stores, events, forms, chat, reviews and embedded widgets each render their own markup. Findings inside them are configured in the app's settings or reported to its developer, not fixed in the editor.

4. Images, galleries and media

Every image and gallery item has an alt text field. Uploaded media, slideshows and video boxes need descriptions and controls that do not rely on hovering.

What the scan finds on a Wix page

The published page is loaded in a real browser exactly as a visitor gets it, apps and all, and tested with axe-core against the machine-testable WCAG 2.2 A and AA criteria.

What this scan finds

Images, gallery items and image links with no alt text
Text elements tagged as headings out of order, and pages with no h1
Buttons and links with no accessible name, including icon and social buttons
Text, button and overlay colors that do not contrast enough with their background
Form fields without labels, and submit buttons without names
Missing landmarks and content outside them
Slideshows, lightboxes and scrolling strips that keyboard users cannot reach
ARIA misuse in app widgets, such as roles with missing required attributes

What needs a person

Whether the alt text describes the image well, or should be empty
Whether freely placed elements read in a sensible order with a screen reader
Whether the menu, lightboxes and slideshows work with a keyboard from start to finish
Whether animations can be paused and respect reduced-motion settings
Whether a form's error messages explain what to fix
Whether bookings, checkout and member areas can be completed with a screen reader

Automated testing does not replace a manual accessibility review.

Where to fix common findings in Wix

Most findings are a setting on the selected element.

1. Alt text

Select the image, open its settings and fill in the alt text field. Gallery items have their own alt text in the gallery's Manage Media panel. Leave it empty on purpose for decorative images.

2. Heading tags on text

Select the text element, open the text settings and choose its tag: H1 for the page's main heading (one per page), H2 for sections, H3 beneath them, P for paragraphs. Choose the tag for the outline and the theme style for the look.

3. Names on buttons and links

Icon buttons and image links need text. Add it in the element's settings, or as accessible-name text where the element offers one. Make link text say where the link goes.

4. Colors and contrast

Adjust the text, button and background colors in the design settings or the site's theme palette until the report's measured ratio meets 4.5:1 for normal text and 3:1 for large text.

5. Forms

In the form's settings, keep the label switched on for every field; placeholder text is not a label. Name the submit button for what it does, and give error and success messages real text.

6. Site-level accessibility settings

The Wix Editor's accessibility settings can switch on visual focus indicators and a skip-to-content link, and the Accessibility Wizard walks through some of the same checks inside the editor. Turn those on, then scan again to see what remains on the published page.

Which Wix pages to check

Check the home page, a page with a form, a page that uses a gallery or slideshow, and any page an app renders, such as a services, booking or store page. Findings in the header, menu and footer repeat on every page, so fixing them once fixes them everywhere. Findings in text and images are page by page.

The scan tests the published page as a visitor receives it. Wix's own Accessibility Wizard works inside the editor and is worth running too; this scan is the one that sees apps, embeds and the page as finally rendered. Scan the published address, not the editor preview.

Frequently asked questions

TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.

One checker, the same real-browser scan, explained for the question you came with. Every report opens at the same place.

Check a published Wix page now.

Free, no signup, usually ready in a couple of minutes.

Check My Wix Site