You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/rules/template-no-aria-hidden-on-focusable.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,10 @@ Per [WAI-ARIA 1.2 — aria-hidden](https://www.w3.org/TR/wai-aria-1.2/#aria-hidd
12
12
13
13
The phrase "may receive focus" is interpreted to include focusable descendants: `aria-hidden` cascades to hide the entire subtree from assistive tech, while any focusable descendant within that subtree remains reachable via Tab — landing keyboard users on AT-invisible content.
14
14
15
+
### What counts as `aria-hidden="true"`
16
+
17
+
Only explicit truthy values trigger the rule: `aria-hidden="true"`, `aria-hidden={{true}}`, `aria-hidden="{{true}}"`, and case-insensitive variants. Valueless `<div aria-hidden>` and `aria-hidden="false"` / `{{false}}` are NOT treated as hidden — the author's signal must be explicit. See the shared spec-divergence rationale in `template-no-invalid-interactive` for the broader reasoning on valueless `aria-hidden` handling across this plugin.
0 commit comments