Merge branch 'master' into fix/invalid-role-aria-query

Author: johanrd

.github/workflows/bench-compare.yml

@@ -26,7 +26,7 @@ jobs:
           # (github.head_ref is a branch name that only exists on the fork remote).
           ref: ${{ github.event.pull_request.head.sha }}
 
-      - uses: wyvox/action-setup-pnpm@v3
+      - uses: wyvox/action-setup-pnpm@v4
 
       - name: Run benchmark comparison
         env:

.release-plan.json

@@ -1,5 +1,42 @@
 # Changelog
 
+## Release (2026-04-25)
+
+* eslint-plugin-ember 13.1.1 (patch)
+
+#### :bug: Bug Fix
+* `eslint-plugin-ember`
+  * [#2735](https://github.com/ember-cli/eslint-plugin-ember/pull/2735) Update ember-eslint-parser to 0.11 ([@NullVoxPopuli](https://github.com/NullVoxPopuli))
+  * [#2736](https://github.com/ember-cli/eslint-plugin-ember/pull/2736) fix: ignore comment + whitespace nodes in template-no-yield-only ([@johanrd](https://github.com/johanrd))
+  * [#2722](https://github.com/ember-cli/eslint-plugin-ember/pull/2722) refactor(template-require-presentational-children): source role list from aria-query ([@johanrd](https://github.com/johanrd))
+  * [#2719](https://github.com/ember-cli/eslint-plugin-ember/pull/2719) BUGFIX: template-no-aria-unsupported-elements — source the reserved-element list from aria-query ([@johanrd](https://github.com/johanrd))
+  * [#2718](https://github.com/ember-cli/eslint-plugin-ember/pull/2718) BUGFIX: template-require-media-caption — compare kind="captions" case-insensitively ([@johanrd](https://github.com/johanrd))
+  * [#2714](https://github.com/ember-cli/eslint-plugin-ember/pull/2714) BUGFIX: accept tabindex="-1" in template-require-aria-activedescendant-tabindex ([@johanrd](https://github.com/johanrd))
+
+#### :house: Internal
+* `eslint-plugin-ember`
+  * [#2733](https://github.com/ember-cli/eslint-plugin-ember/pull/2733) test: cover {{! eslint-disable-* }} directives inside <template> in .gts ([@johanrd](https://github.com/johanrd))
+  * [#2721](https://github.com/ember-cli/eslint-plugin-ember/pull/2721) refactor(template-no-abstract-roles): source abstract-role list from aria-query ([@johanrd](https://github.com/johanrd))
+
+#### Committers: 2
+- [@NullVoxPopuli](https://github.com/NullVoxPopuli)
+- [@johanrd](https://github.com/johanrd)
+
+## Release (2026-04-21)
+
+* eslint-plugin-ember 13.1.0 (minor)
+
+#### :rocket: Enhancement
+* `eslint-plugin-ember`
+  * [#2715](https://github.com/ember-cli/eslint-plugin-ember/pull/2715) feat: re-export hbs parser and document HBS flat-config setup ([@johanrd](https://github.com/johanrd))
+
+#### :bug: Bug Fix
+* `eslint-plugin-ember`
+  * [#2713](https://github.com/ember-cli/eslint-plugin-ember/pull/2713) BUGFIX: false positive: interactive flow content inside <details> ([@johanrd](https://github.com/johanrd))
+
+#### Committers: 1
+- [@johanrd](https://github.com/johanrd)
+
 ## Release (2026-04-20)
 
 * eslint-plugin-ember 13.0.0 (major)

CHANGELOG.md

@@ -174,6 +174,36 @@ export default [
 
 `template-lint-migration` mirrors the ember-template-lint `recommended` preset.
 
+### Linting `.hbs` files
+
+ESLint flat config only picks up `.hbs` files when a `files` glob names them. Add a dedicated block so they route to the Handlebars parser:
+
+```js
+// eslint.config.mjs
+import { hbsParser, plugin as emberPlugin } from 'eslint-plugin-ember/recommended';
+
+export default [
+  // ...other blocks...
+  {
+    files: ['app/**/*.hbs'],
+    languageOptions: { parser: hbsParser },
+    plugins: { ember: emberPlugin },
+    rules: {
+      'ember/template-no-bare-strings': 'error',
+      // ...other template rules...
+    },
+  },
+];
+```
+
+Make sure no earlier `@typescript-eslint/parser` block's `files` glob reaches `.hbs` — narrow it to `['**/*.{js,ts,gjs,gts}']` (or similar). Flat config merges rules across every matching block, so even if our HBS block overrides the parser, type-info rules from a matching TS block still layer on and fail with errors like:
+
+> Parsing error: `…` was not found by the project service because the extension for the file (`.hbs`) is non-standard.
+
+or
+
+> Error while loading rule `@typescript-eslint/await-thenable`: You have used a rule which requires type information.
+
 ### Replacing `template-lint-disable` comments
 
 Inline disable directives need to be rewritten to ESLint's syntax, prefixed with `ember/template-`. For now, only two scopes are supported: the next line, or the rest of the file. For example, replace:

README.md

@@ -40,6 +40,34 @@ Examples of **correct** code for this rule:
 </template>
 ```
 
+Explicit opt-out via a mustache boolean `false` is allowed — this is the
+only form that statically guarantees no rendered `autofocus` attribute
+(Glimmer VM normalizes `{{false}}` to attribute removal). The string
+`autofocus="false"` is still flagged per HTML boolean-attribute semantics
+(any attribute presence, including the string `"false"`, enables autofocus).
+
+```gjs
+<template>
+  <input autofocus={{false}} />
+  {{!-- element syntax: the mustache-boolean form --}}
+
+  {{input autofocus=false}}
+  {{!-- mustache syntax: the hash-pair form --}}
+</template>
+```
+
+`<dialog>` and its descendants are exempt. A dialog is expected to focus its
+initial element on open, per
+[MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/dialog):
+
+```gjs
+<template>
+  <dialog>
+    <button autofocus>Close</button>
+  </dialog>
+</template>
+```
+
 ## When Not To Use It
 
 If you need to autofocus for specific accessibility or UX requirements and have thoroughly tested with assistive technologies, you may disable this rule for those specific cases.

docs/rules/template-no-autofocus-attribute.md

@@ -50,6 +50,14 @@ This rule **allows** the following:
 
 If violations are found, remediation should be planned to ensure text content is present and visible and/or screen-reader accessible. Setting `aria-hidden="false"` or removing `hidden` attributes from the element(s) containing heading text may serve as a quickfix.
 
+## Notes on `aria-hidden` semantics
+
+This rule follows [WAI-ARIA 1.2 §`aria-hidden`](https://www.w3.org/TR/wai-aria-1.2/#aria-hidden) verbatim: only an explicit truthy value hides the element. Ambiguous shapes — valueless `aria-hidden`, empty string, and mustache literals that resolve to an empty / whitespace-only string — all resolve to the default `undefined` and do NOT exempt the heading from the empty-content check.
+
+- `aria-hidden="true"` / `aria-hidden={{true}}` / `aria-hidden={{"true"}}` (any case, whitespace-trimmed) → hidden, exempts the heading.
+- `aria-hidden="false"` / `aria-hidden={{false}}` / `aria-hidden={{"false"}}` → not hidden, the empty-content check applies.
+- `<h1 aria-hidden>` / `aria-hidden=""` / `aria-hidden={{""}}` / `aria-hidden={{" "}}` → spec-default `undefined`, the empty-content check applies.
+
 ## References
 
 - [WCAG SC 2.4.6 Headings and Labels](https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-descriptive.html)

docs/rules/template-no-empty-headings.md

@@ -6,11 +6,11 @@
 
 <!-- end auto-generated rule header -->
 
-This rule requires all non-interactive HTML elements using the `aria-activedescendant` attribute to declare a `tabindex` of zero.
+This rule requires non-interactive HTML elements using the `aria-activedescendant` attribute to declare a `tabindex` of `0` or `-1`.
 
 The `aria-activedescendant` attribute identifies the active descendant element of a composite widget, textbox, group, or application with document focus. This attribute is placed on the container element of the input control, and its value is set to the ID of the active child element. This allows screen readers to communicate information about the currently active element as if it has focus, while actual focus of the DOM remains on the container element.
 
-Elements with `aria-activedescendant` must have a `tabindex` of zero in order to support keyboard navigation. Besides interactive elements, which are inherently keyboard-focusable, elements using the `aria-activedescendant` attribute must declare a `tabIndex` of zero with the `tabIndex` attribute.
+Elements with `aria-activedescendant` must be focusable to support keyboard navigation. `tabindex="0"` puts the element in the natural tab order; `tabindex="-1"` makes it focusable programmatically (e.g. via roving focus) but skips it in the tab order. Both are valid patterns for composite widgets — see the [W3C APG — Managing focus in composites using aria-activedescendant](https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#kbd_focus_activedescendant).
 
 ## Examples
 
@@ -19,8 +19,8 @@ This rule **forbids** the following:
 ```gjs
 <template>
   <div aria-activedescendant='some-id'></div>
-  <div aria-activedescendant='some-id' tabindex='-1'></div>
-  <input aria-activedescendant={{some-id}} tabindex='-1' />
+  <div aria-activedescendant='some-id' tabindex='-2'></div>
+  <input aria-activedescendant={{some-id}} tabindex='-100' />
 </template>
 ```
 
@@ -32,9 +32,11 @@ This rule **allows** the following:
   <CustomComponent aria-activedescendant={{some-id}} />
   <CustomComponent aria-activedescendant={{some-id}} tabindex={{0}} />
   <div aria-activedescendant='some-id' tabindex='0'></div>
+  <div aria-activedescendant='some-id' tabindex='-1'></div>
   <input />
   <input aria-activedescendant={{some-id}} />
   <input aria-activedescendant={{some-id}} tabindex={{0}} />
+  <input aria-activedescendant={{some-id}} tabindex={{-1}} />
 </template>
 ```
 

docs/rules/template-require-aria-activedescendant-tabindex.md

@@ -6,9 +6,11 @@
 
 ## `<iframe>`
 
-`<iframe>` elements must have a unique title property to indicate its content to the user.
-
-This rule takes no arguments.
+`<iframe>` elements must have a unique title property so assistive
+technology can convey their content to the user. The normative
+requirement is [WCAG SC 4.1.2 (Name, Role, Value)](https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html);
+the `title` attribute is _one sufficient technique_ for meeting it
+(sufficient technique [H64](https://www.w3.org/WAI/WCAG21/Techniques/html/H64)).
 
 ## Examples
 
@@ -27,12 +29,21 @@ This rule **forbids** the following:
 <template>
   <iframe />
   <iframe title='' />
+  <iframe title='   ' />
+  <iframe title={{null}} />
+  <iframe title={{undefined}} />
+  <iframe title={{true}} />
+  <iframe title={{false}} />
+  <iframe title={{42}} />
 </template>
 ```
 
 ## References
 
-- [Deque University](https://dequeuniversity.com/rules/axe/1.1/frame-title)
-- [Technique H65: Using the title attribute of the frame and iframe elements](https://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140408/H64)
-- [WCAG Success Criterion 2.4.1 - Bypass Blocks](https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html)
-- [WCAG Success Criterion 4.1.2 - Name, Role, Value](https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html)
+- [WCAG SC 4.1.2 — Name, Role, Value](https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html)
+  — the normative requirement.
+- [WCAG Technique H64 — Using the title attribute of the iframe element](https://www.w3.org/WAI/WCAG21/Techniques/html/H64)
+  — a sufficient technique for SC 4.1.2, not itself normative.
+- [WCAG Success Criterion 2.4.1 — Bypass Blocks](https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html)
+- [ACCNAME 1.2 — accessible-name computation](https://www.w3.org/TR/accname-1.2/)
+- [axe-core rule `frame-title`](https://dequeuniversity.com/rules/axe/4.10/frame-title)

docs/rules/template-require-iframe-title.md

@@ -31,9 +31,40 @@ This rule **allows** the following:
   <div role="option" aria-selected="false" />
   <CustomComponent role="checkbox" aria-required="true" aria-checked="false" />
   {{some-component role="heading" aria-level="2"}}
+
+  {{! Native inputs supply required ARIA state for matching roles. Lookup is
+      based on axobject-query's elementAXObjects + AXObjectRoles (see below). }}
+  <input type="checkbox" role="switch" />
+  <input type="checkbox" role="checkbox" />
+  <input type="radio" role="radio" />
+  <input type="range" role="slider" />
 </template>
 ```
 
+## Semantic-role exemptions
+
+When the role attribute explicitly declares a role that the native element already provides, the native element supplies the required ARIA state and the rule does not flag missing attributes. The exemption is looked up via [axobject-query](https://github.com/A11yance/axobject-query)'s `elementAXObjects` + `AXObjectRoles` maps, matching the approach used by `eslint-plugin-jsx-a11y` and `@angular-eslint/template`.
+
+Exempt pairings include (non-exhaustive):
+
+| Element                   | Role                 | Required ARIA state supplied by                  |
+| ------------------------- | -------------------- | ------------------------------------------------ |
+| `<input type="checkbox">` | `checkbox`, `switch` | native `checked` state                           |
+| `<input type="radio">`    | `radio`              | native `checked` state                           |
+| `<input type="range">`    | `slider`             | native `value` / `min` / `max`                   |
+| `<input type="number">`   | `spinbutton`         | native `value` (spinbutton has no required ARIA) |
+| `<input type="text">`     | `textbox`            | no required ARIA                                 |
+| `<input type="search">`   | `searchbox`          | no required ARIA                                 |
+
+Undocumented pairings (e.g. `<input type="checkbox" role="menuitemcheckbox">` — axobject-query does not list this) remain flagged.
+
 ## References
 
-- [WAI-ARIA Roles - Accessibility \_ MDN](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles)
+- [WAI-ARIA Roles](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles)
+- [WAI-ARIA APG — Switch pattern](https://www.w3.org/WAI/ARIA/apg/patterns/switch/)
+- [HTML-AAM — `<input type="checkbox">` → `checkbox` role mapping](https://www.w3.org/TR/html-aam-1.0/#el-input-checkbox)
+  — primary-spec source: HTML-AAM maps the native element to the
+  `checkbox` role and derives `aria-checked` from the element's
+  checkedness (and `indeterminate` for `mixed`). axobject-query
+  encodes that mapping for tooling.
+- [axobject-query](https://github.com/A11yance/axobject-query) — AX-tree data source for the exemption lookup (secondary, encodes HTML-AAM)

docs/rules/template-require-mandatory-role-attributes.md

@@ -224,7 +224,7 @@ module.exports = [
       'import/default': 'off',
       'import/no-named-as-default': 'off',
       'import/no-named-as-default-member': 'off',
-      'import/no-unresalved': 'off',
+      'import/no-unresolved': 'off',
       'import/no-missing-import': 'off',
 
       // vite config format does not match regex