How to fix tabindex on Wix

Steps for Wix

1. Open your site in the Wix Editor.
2. Click on any element you suspect has a custom tab order set — in the Wix Editor, right-click the element and look for 'Accessibility Settings' or 'Settings'.
3. In the element's settings panel, look for a 'Tab Order' or 'Keyboard Focus' field and ensure it is not set to a custom positive number.
4. For Wix Studio or sites using Velo (Wix's developer platform): open the Velo Dev Mode panel, search your page code and site code files for 'tabIndex' (capital I), and change any value above 0 to 0 or -1 as appropriate.
5. Wix does not expose direct HTML editing for most elements, so if a widget or App Market component is the source, contact the app developer or replace the component.
6. Publish your site and verify keyboard tab order by testing with the Tab key in a browser.

What is tabindex?

The `tabindex` attribute controls the order in which keyboard users move through interactive elements on a page using the Tab key. A value of `tabindex="0"` means an element joins the natural tab order based on where it appears in the HTML. A value of `tabindex="-1"` removes the element from the tab order but still allows it to receive focus via JavaScript. A positive value — like `tabindex="1"`, `tabindex="5"`, or any number above zero — forces a custom tab order that almost always creates a confusing, broken experience for keyboard and screen-reader users. This accessibility rule flags any element with a tabindex value greater than 0.

Positive tabindex values hijack the natural reading and navigation order, causing keyboard-only users and screen-reader users to jump around the page unpredictably — often skipping important links, buttons, or form fields entirely, or hitting them in an illogical sequence. This directly violates WCAG 2.1 Success Criterion 2.4.3 (Focus Order) and can expose your store to legal accessibility complaints or lawsuits, which are increasingly common in e-commerce. Beyond legal risk, a broken keyboard experience means customers who rely on keyboard navigation (including many users with motor disabilities) may be unable to complete checkout, contact forms, or product searches — directly costing you conversions and revenue. Fixing this is also a signal of overall code quality that can indirectly support SEO through improved Core Web Vitals and reduced bounce rates from frustrated users.

See the complete Tabindex guide for every platform and the full background.