Wix Accessibility: Run the Wizard and Check Your Enquiry Form

A Wix accessibility check should include both the Accessibility Wizard and a hands-on test of the page people use to contact you. Run the scan, work through its manual tasks, then follow the enquiry route with a keyboard. Pay particular attention to visible focus, field labels, error messages and confirmation after submission.
The mistake to avoid is treating a completed scan as the end of the job. Wix explains that the Wizard has coverage limits, including Velo features and some shopping components. Its results guide improvements, but they do not certify legal compliance. Bring in an accessibility specialist when you need a formal evaluation.
CodeMasters' website design service includes accessibility checks. If a form or custom component is difficult to use, bring the page URL and the exact step that fails to a free 30-minute consultation. We can discuss the setup and development work involved.
Run the Wizard in your Wix editor
Wix's current Wizard instructions distinguish Studio Editor from Wix Editor.
In Studio Editor:
Open Site Checker on the left.
Choose Fix Accessibility Issues.
If the DOM-order option appears, review it before scanning. Selecting it allows the Wizard to reorganize the underlying content order.
Select Scan Site.
Review both Detected issues and Manual tasks, including the relevant page sections.
DOM means Document Object Model, the structure the browser uses to organize page elements. It helps determine reading and navigation order. If you allow the Wizard to change it, retest the page afterwards. Wix says the checkbox may be absent on newer sites, sites previously organized by the Wizard, or sites with auto DOM disabled.
In Wix Editor, begin with Settings at the top, then Accessibility Wizard and Scan Site. Use the instructions for your editor rather than looking for identical controls in both.

Keep the scan, manual checks and retest results in one maintenance record.
Work through the detected items that apply to your site. Then complete the manual checks. Keep the page URL, problem, change and retest result in a short handover record. That is more useful to the next person maintaining the site than a note saying only “scan complete”.
Test the route from the service page to the form
Open the public page in a browser and put the mouse aside. Press Tab to move between interactive controls and Shift+Tab to move backwards. Activate the enquiry link with the keyboard, then continue through the form.
Watch for the visible outline or highlight that identifies the current control. You should be able to tell where you are as you move. W3C's first accessibility review explains keyboard access and visible focus checks.
Check the sequence as well as the appearance. Can someone reach the enquiry button, enter the fields, correct a mistake and get to the submit button in a sensible order? A visually tidy layout can still have an awkward underlying navigation order.
Check | What to look for | What to record |
Service-page action | Enquiry link can be reached and activated | URL and button or link text |
Form navigation | Focus stays visible and moves sensibly | The control where the sequence fails |
Invalid entry | Error explains what needs correcting | Field and message shown |
Successful submission | Confirmation is clear | What the visitor sees after sending |
Use test details clearly marked for your team and remove unnecessary personal information from screenshots. Check the receiving submission too. A usable form and a delivered enquiry are separate parts of the same business process. Our enquiry troubleshooting guide covers saving, notifications and follow-up checks.
Keep focus visible in the published design
Wix's newer focus-indicator guide says indicators are always enabled in Studio. You still need to check their visibility against the actual colours and backgrounds on your page.
For a Wix Editor site with missing indicators, the current route is Accessibility Wizard, Scan Site, Detected issues, Site level, then Show focus indicators. Enable Include visual indicators and apply the change. Publish and test the page again.
Avoid removing a focus outline to make a button look cleaner. It tells a keyboard user which action they are about to activate.
Give each form field a lasting, clear title
Placeholder text inside an empty input can disappear once someone begins typing. A visible field title keeps the purpose of the field available while they enter or review information. W3C's form-label guidance also explains the need to associate the label with its control so assistive technology can identify it.
For new Wix Forms, follow Wix's field-title instructions: select the form, open Edit Form, select a field and open Settings. Use the title's More actions control to show the field title when it is hidden. Enter a specific title in Field title and save.
Review every field rather than fixing only the first one. “Email address” is clearer than “Details”. Keep any required format or instruction close to the relevant input. Then test an invalid entry and check that the correction is understandable without relying on a red border alone.

Check labels and feedback throughout the task, including error and success states.
Wix currently advises moving from old Wix Forms to new Wix Forms for accessibility. Confirm which form version you have before following its setup instructions. A custom Velo form needs its own review of labels, keyboard behaviour, validation and feedback. Changing to custom code does not remove those responsibilities.
Check the parts a scan cannot settle
Open the page at increased browser zoom and look for text, controls or messages that become obscured. Test the complete form, not just its first screen. If a booking tool, embedded widget or custom component is part of the route, include it in the hands-on check.
For a multilingual site, repeat the practical checks in each published language. Wix says the Wizard currently supports the primary language only. Translated field titles, longer button labels and error messages still need attention on secondary-language pages.
After changing the layout, adding a field or replacing a component, repeat the affected checks. Keep any unresolved issue assigned to someone, with enough detail for them to reproduce it. For custom controls or assistive-technology problems, ask the developer or accessibility specialist to assess the actual implementation.
Common questions
Will replacing a form affect the enquiry workflow?
It can change the setup your team relies on. Before replacing an old form, list its fields, confirmation, notifications and integrations. Test the replacement through to receipt by the team. Our Wix Forms and Velo comparison explains how to choose the form approach.
Should I buy an accessibility overlay before fixing the page?
Start with the underlying content and controls. A toolbar or overlay does not replace checking whether someone can navigate, understand and submit your form. Ask for evidence of the specific problem any proposed tool addresses, then retest that behaviour.
What should a useful issue report include?
Record the URL, browser, starting point, keys or actions used, expected behaviour and actual result. Include a screenshot or short recording when it helps, with personal details removed. This gives the person fixing it a reproducible task.
If you need help with the Wix setup or a custom component, book a free 30-minute consultation with that record, or send the details in writing. The first decision is which changes belong in native settings and which need development or specialist testing.


