Accessibility attributes the Wix user configures for a component, mapping to ARIA attributes and related HTML. Use it for a field that carries a component's role, labels, states, and the tag it renders as. At runtime it's an object whose fields you spread onto the rendered element. Every field is optional, so read only the ones your component applies.
In your component code, import the A11y type from @wix/editor-react-types:
An A11y object has the following properties:
The aria-atomic attribute. Indicates whether assistive technologies should present the entire region as a whole.
The aria-autocomplete attribute. Indicates the type of autocomplete behavior for an input.
The aria-busy attribute. Indicates the component is being modified and assistive technologies should wait.
The aria-controls attribute. Identifies the element whose contents or presence are controlled by this component.
The aria-current attribute. Indicates the component that represents the current item within a container or set.
The aria-describedby attribute. Identifies the element that describes this component.
The aria-disabled attribute. Indicates that the component is perceivable but disabled.
The aria-errormessage attribute. Identifies the element that provides an error message for this component.
The aria-expanded attribute. Indicates whether a collapsible component is expanded or collapsed.
The aria-haspopup attribute. Indicates the availability and type of an interactive popup component.
The aria-hidden attribute. Hides the component from assistive technologies.
The aria-invalid attribute. Indicates the entered value does not conform to the expected format.
The aria-label attribute. Defines a string value that labels the component.
The aria-labelledby attribute. Identifies the element that labels this component.
The aria-level attribute. Defines the hierarchical level of a component within a structure.
The aria-live attribute. Indicates that the component will be updated and describes the types of updates.
The aria-multiline attribute. Indicates whether a text box accepts multiple lines of input.
The aria-owns attribute. Identifies a component to define a visual, functional, or contextual parent/child relationship.
The aria-pressed attribute. Indicates the current pressed state of a toggle button.
The aria-relevant attribute. Indicates what notifications the user agent triggers when the accessibility tree is modified.
The aria-roledescription attribute. Defines a human-readable description for the role of the component.
Whether the component supports multiline input.
The role attribute. Defines the semantic role of the component.
The tabindex attribute. Controls the component's position in keyboard focus order.
The HTML tag to render the component as, such as 'h1' or 'button'.
Your code either consumes a value of type A11y or produces one:
In your manifest, declare the field with the a11y dataType:
Declare an a11y field in one of these ways, depending on where the value comes from:
Last updated: 2 November 2026