role="menu" incorrectly marked as rendundant and no-interactive-to-interactive when used on menu element

[raythurnvoid]

Describe the bug

Has per MDN docs the menu element is like the ul element but more semantically correct for interactive content, and the implicit role is list not menu.

Reproduction URL

N/A

Reproduction

No response

Logs

No response

System Info

System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 AMD Ryzen 9 4900H with Radeon Graphics
    Memory: 16.49 GB / 31.42 GB
  Binaries:
    Node: 18.14.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.3.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1555.0), Chromium (112.0.1722.58)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @sveltejs/adapter-static: ^2.0.1 => 2.0.2 
    @sveltejs/kit: ^1.15.2 => 1.15.5 
    svelte: ^3.58.0 => 3.58.0 
    vite: ^4.2.1 => 4.2.1

[ngtr6788]

I tried testing similar markup in React JSX instead of Svelte + jsx-eslint (which Svelte's a11y checks are based on), and this is what I see

You are correct for seeing that menu's implicit role is list. As for the no-noninteractive-element-to-interactive-role, I'm not too sure what to do, because the statement seems a bit contradictory, doesn't it? Maybe we could ask jsx-eslint?

[raythurnvoid]

I tried testing similar markup in React JSX instead of Svelte + jsx-eslint (which Svelte's a11y checks are based on), and this is what I see You are correct for seeing that menu's implicit role is list. As for the no-noninteractive-element-to-interactive-role, I'm not too sure what to do, because the statement seems a bit contradictory, doesn't it? Maybe we could ask jsx-eslint?

yeah, I'm not very familiar with it but as a general thought I think that as long as a role is marked as "permitted" on MDN, I don't see why eslint should tell me not to use it and MDN doesn't distinguish between interactive and non-interactive roles.