fix: first-recognized-token for presentation/none escape-hatch; fix helper name consistency

Author: johanrd

docs/rules/template-no-invalid-interactive.md

@@ -51,7 +51,7 @@ Examples of **correct** code for this rule:
 An element opts out of this rule's handler-on-non-interactive check in two cases:
 
 - **`aria-hidden="true"`** (including valueless / empty / `{{true}}` / `{{"true"}}` forms) — the author has explicitly removed the element from the accessibility tree, so a "non-interactive element with handler" is moot; AT users won't encounter it either way. Explicit `aria-hidden="false"` / `{{false}}` still flags.
-- **`role="presentation"` / `role="none"`** — the author asserts the element is decorative. We accept `role="presentation"` and `role="none"` (case-insensitive, first-token of a space-separated role list) — a deliberate superset of [jsx-a11y's exact-match `isPresentationRole`](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/src/util/hasPresentationRole.js) for consistency with [WAI-ARIA 1.2 §4.1](https://www.w3.org/TR/wai-aria-1.2/#host_general_role) role-fallback semantics.
+- **`role="presentation"` / `role="none"`** — the author asserts the element is decorative. We accept `role="presentation"` and `role="none"` (case-insensitive, first recognized token of a space-separated role list per WAI-ARIA first-recognized-token rule) — a deliberate superset of [jsx-a11y's exact-match `hasPresentationRole`](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/src/util/hasPresentationRole.js) for consistency with [WAI-ARIA 1.2 §4.1](https://www.w3.org/TR/wai-aria-1.2/#host_general_role) role-fallback semantics.
 
 The valueless `aria-hidden` case (e.g. `<div aria-hidden>`) is [genuinely contested](https://www.scottohara.me/blog/2018/05/05/hidden-vs-none.html) — jsx-a11y, vue-a11y, axe-core, and the WAI-ARIA spec take four different positions on whether it counts as "hidden". This rule leans toward fewer false positives: flagging a handler on an author-decorated element creates friction more often than it catches real bugs.
 

lib/rules/template-no-invalid-interactive.js

@@ -1,5 +1,4 @@
-'use strict';
-
+const { roles } = require('aria-query');
 const { isNativeElement } = require('../utils/is-native-element');
 const { isHtmlInteractiveContent } = require('../utils/html-interactive-content');
 const { INTERACTIVE_ROLES } = require('../utils/interactive-roles');
@@ -23,8 +22,11 @@ function getTextAttr(node, name) {
 // Does this element carry a non-interactive escape hatch that opts it out
 // of the interactive-handler check?
 //   - role="presentation" or role="none": author asserts the element is
-//     decorative. We accept the first token of a space-separated role list
-//     (a superset of jsx-a11y's exact-match `isPresentationRole`).
+//     decorative. We find the first recognized ARIA role token in the
+//     space-separated list (per WAI-ARIA first-recognized-token rule) and
+//     check whether it is "presentation" or "none" — matching jsx-a11y's
+//     hasPresentationRole semantics while correctly handling unknown leading
+//     tokens such as role="foo none".
 //   - aria-hidden in any plausibly-"hide" form — valueless, empty-string,
 //     "true" (case-insensitive), `{{true}}`, `{{"true"}}`.
 //
@@ -36,8 +38,11 @@ function getTextAttr(node, name) {
 function hasNonInteractiveEscapeHatch(node) {
   const roleAttr = findAttr(node, 'role');
   if (roleAttr?.value?.type === 'GlimmerTextNode') {
-    const token = roleAttr.value.chars.trim().toLowerCase().split(/\s+/u)[0];
-    if (token === 'presentation' || token === 'none') {
+    const tokens = roleAttr.value.chars.trim().toLowerCase().split(/\s+/u);
+    // WAI-ARIA first-recognized-token: skip unknown tokens, use the first
+    // one that aria-query recognizes as a valid role.
+    const firstRecognized = tokens.find((t) => roles.get(t) !== undefined);
+    if (firstRecognized === 'presentation' || firstRecognized === 'none') {
       return true;
     }
   }