refactor: align with #37's HTML-content-model authority split

Replace lib/utils/native-interactive-elements.js with
lib/utils/html-interactive-content.js to match the canonical util
introduced in #37. The new util cites HTML Living Standard §3.2.5.2.7
Interactive Content as its sole authority, resolving the previous
mixed-authority approach that cited axobject-query's widget taxonomy
for some rows and HTML spec for others.

Byte-identical copy of #37's util + test across worktrees so the two
PRs can land in either order without conflict.

Author: johanrd

lib/rules/template-no-interactive-element-to-noninteractive-role.js

@@ -14,14 +14,16 @@ const { isComponentInvocation } = require('../utils/is-component-invocation');
 //      elements whose AXObject is a widget but aria-query lists no inherent
 //      ARIA role (e.g. <summary>, <menuitem>, <embed>).
 //
-// Why we do NOT use the shared `isNativeInteractive` util here:
+// Why we do NOT use the shared `isHtmlInteractiveContent` util here:
 //   Keep the rule's layered aria-query + axobject-query derivation — this
-//   rule's scope is narrower than `isNativeInteractive`. We care about tags
-//   that have INHERENT interactive semantics per HTML-AAM (so that applying
-//   a non-interactive role is a demotion). `isNativeInteractive` also treats
-//   tags with conditional interactivity (a[href], audio[controls]) as
-//   interactive in a way that wouldn't make sense here without the
-//   conditional context.
+//   rule's scope is different. We care about tags that have INHERENT
+//   interactive semantics per HTML-AAM / the ARIA widget role mappings (so
+//   that applying a non-interactive role is a demotion of AT semantics).
+//   `isHtmlInteractiveContent` answers a different question — "does HTML's
+//   content model forbid nesting this inside an interactive parent?" — and
+//   diverges on e.g. <label> (HTML-interactive, ARIA structure),
+//   <option>/<datalist> (not HTML-interactive, but ARIA widgets), and
+//   <canvas> (not HTML-interactive, AX widget).
 //
 // Deviations from jsx-a11y, driven by real-world false-positive patterns:
 //   - `<canvas>` is NOT treated as inherently interactive. Its AXObject is

lib/utils/html-interactive-content.js

@@ -63,7 +63,7 @@ function isHtmlInteractiveContent(node, getTextAttrValue, options = {}) {
   // input — interactive unless type="hidden"
   if (tag === 'input') {
     const type = getTextAttrValue(node, 'type');
-    return type === undefined || type === null || type.trim().toLowerCase() !== 'hidden';
+    return type !== 'hidden';
   }
 
   // a — interactive only when href is present

lib/utils/native-interactive-elements.js

@@ -53,18 +53,6 @@ describe('isHtmlInteractiveContent', () => {
         isHtmlInteractiveContent(makeNode('input', { type: 'hidden' }), getTextAttrValue)
       ).toBe(false);
     });
-
-    it('is NOT interactive when type="HIDDEN" (case-insensitive)', () => {
-      expect(
-        isHtmlInteractiveContent(makeNode('input', { type: 'HIDDEN' }), getTextAttrValue)
-      ).toBe(false);
-    });
-
-    it('is NOT interactive when type=" hidden " (whitespace-trimmed)', () => {
-      expect(
-        isHtmlInteractiveContent(makeNode('input', { type: ' hidden ' }), getTextAttrValue)
-      ).toBe(false);
-    });
   });
 
   describe('<a>', () => {