no-redundant-roles

Elements come with roles already. Writing one that matches changes nothing:

Button({ role: "button" }); // <button> is already a button
Nav({ role: "navigation" }); // <nav> is already navigation
Ul({ role: "list" }); // <ul> is already a list

All the role rules want element-props position; this one wants the element named as well, since an implicit role is a fact about the tag. So it fires on core's element helpers — Button, Nav, Ul imported from @implementjs/core — and on a component("nav", { … }) that writes its tag out, and nowhere else. A DialogTrigger that eventually renders a <button> is three files away, and no rule here can follow it. Aliasing on import is handled: the imported name decides the tag, not the local one.

Elements whose role depends on an attribute are resolved from the props beside them, so Input({ type: "checkbox", role: "checkbox" }) is reported while Input({ type: "text", role: "checkbox" }) is not.