How to fix aria allowed role on Webflow
Remove or replace any ARIA `role` attribute that is not permitted on the HTML element it is applied to — in particular, do not add `role="textbox"` (or other interactive roles) to elements that already have a native semantic role which conflicts with it.
Steps for Webflow
- Open the Webflow Designer and select the element flagged by the scanner.
- In the right-hand settings panel, click the Element Settings gear icon and scroll to the Custom Attributes section.
- Find the `role` attribute entry and either delete it entirely (if the native element semantics are sufficient) or change its value to a role permitted for this element type.
- If the element type itself is wrong (e.g. a Div Block where an Input should be used), replace it with the correct Webflow element (Form → Text Input, etc.) and remove any conflicting ARIA attributes.
- Publish and re-audit with axe DevTools.
What is aria allowed role?
ARIA roles tell screen readers and other assistive technologies what kind of thing an element is — a button, a text field, a navigation landmark, and so on. Every HTML element already has a built-in (native) role, and the ARIA specification only allows certain roles to be layered on top of certain elements. When you attach a role that is not permitted — for example, adding `role="textbox"` to a `<select>` dropdown, a `<div>` that contains a native `<input>`, or any other element where that role is forbidden — the browser and assistive technology receive a contradictory or invalid instruction. The `aria-allowed-role` rule flags exactly these mismatches.
Screen-reader users (who navigate entirely by announced roles) may hear the wrong element type, skip the control entirely, or be unable to interact with it at all — blocking them from completing purchases, filling out forms, or accessing account features. This directly reduces conversions and exposes your store to legal risk under accessibility laws (ADA Title III in the US, EN 301 549 in the EU, AODA in Canada) that reference WCAG 2.x as the standard. Google's crawler also processes accessibility signals, and persistent WCAG violations can undermine your site's credibility in quality assessments. Fixing invalid ARIA is usually a quick code change with zero visible impact on design.
See the complete Aria allowed role guide for every platform and the full background.
Not sure if your Webflow store has this?
Run a free SEOLZ scan — we’ll find aria allowed role and every other issue across your whole site.
Scan my site free