How to fix aria required attr on Wix

Steps for Wix

1. Wix's standard drag-and-drop editor has limited direct HTML access. First check if the affected widget (e.g. a menu or accordion) is a native Wix component — if so, check Wix's support pages for any built-in accessibility settings or contact Wix support, as they occasionally push fixes via platform updates.
2. If using Wix Editor X / Wix Studio, open the page, select the element, go to the Settings or Accessibility panel in the right sidebar to see if aria properties can be set there.
3. For custom-coded elements, use Wix Velo (Dev Mode): enable Dev Mode from the top bar, select the element, and in the Properties & Events panel set the aria attributes via code: $w('#myButton').setAttribute('aria-expanded', 'false'); and update on click.
4. To dynamically toggle: in Wix Velo, write an onClick handler that reads the current value and toggles it: $w('#myButton').setAttribute('aria-expanded', currentState ? 'true' : 'false');
5. Preview and test with a browser-based accessibility checker such as the axe extension.

What is aria required attr?

ARIA (Accessible Rich Internet Applications) roles tell screen readers and other assistive technologies what kind of widget an element is — for example, a button that opens a dropdown, a tab panel, or an accordion. Each ARIA role has a defined set of required attributes that must also be present for the widget to make sense. For instance, a button that expands a menu must include `aria-expanded` (so the screen reader can announce "expanded" or "collapsed") and typically `aria-controls` (so it points to the element it controls). When those required attributes are missing, the role declaration is incomplete and the assistive technology cannot convey the correct state or relationship to the user.

Screen reader users — who often navigate by keyboard only — rely entirely on ARIA state attributes to know whether a menu is open, a tab is selected, or an accordion panel is visible. Without `aria-expanded`, a screen reader user has no way to know whether a dropdown they just activated is open or closed. Without `aria-controls`, they may not find the content that just appeared. This directly breaks the shopping experience for blind and low-vision customers. WCAG 2.x Success Criterion 4.1.2 (Name, Role, Value) is a Level AA requirement, meaning it is referenced in most accessibility laws worldwide (ADA, Section 508, EN 301 549, AODA). Failing it exposes your store to legal complaints and demand letters. It also signals to Google's quality systems that the site has usability issues, which can indirectly affect organic rankings.

See the complete Aria required attr guide for every platform and the full background.