ARIA
presentation-role-conflict
WCAG 4.1.2 Name, Role, Value Level A
Who this affects
An element is marked as presentational but is still focusable or has a global ARIA attribute, so the roles conflict.
How to fix it
Remove role="presentation", or remove the focusability and ARIA attributes from the element.
How much work is it?
Usually a template or design change. That is a rough guide for planning, not an estimate for your codebase. A single content edit repeated across a template is a template change.
What a person still has to check
Passing this rule does not mean 4.1.2 passes. Automation checks part of the criterion, and the rest is a judgement:
Use a screen reader on each custom control and confirm its name, role, and state are announced.
Read 4.1.2 Name, Role, Value in plain language
Where this check comes from
This is an axe-core rule. We run axe in a real browser on every page we scan. Deque’s reference for presentation-role-conflict
Find out whether your site does this
A scan checks this rule on every page it visits, and shows you the code and a screenshot of each place it fires.