src/content/docs/linter/rules/no-static-element-interactions.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JavaScript (and super languages)" icon="seti:javascript"> ## Summary - Rule available since: `v1.9.0` - Diagnostic Category: [`lint/a11y/noStaticElementInteractions`](/reference/diagnostics#diagnostic-category) - This rule is **recommended**, meaning it is enabled by default. - This rule doesn't have a fix. - The default severity of this rule is [**error**](/reference/diagnostics#error). - Sources: - Same as [`jsx-a11y/no-static-element-interactions`](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-static-element-interactions.md){
"linter": {
"rules": {
"a11y": {
"noStaticElementInteractions": "error"
}
}
}
}
Enforce that static, visible elements (such as <div>) that have click handlers use the valid role attribute.
Static HTML elements do not have semantic meaning. This is clear in the case of <div> and <span>. It is less so clear in the case of elements that seem semantic, but that do not have a semantic mapping in the accessibility layer. For example <a> without href attribute, <meta>, <script>, <picture>, <section>, and <colgroup> -- to name a few -- have no semantic layer mapping. They are as void of meaning as <div>.
The WAI-ARIA role attribute confers a semantic mapping to an element. The semantic value can then be expressed to a user via assistive technology. In order to add interactivity such as a mouse or key event listener to a static element, that element must be given a role value as well.
Source: jsx-a11y/no-static-element-interactions
<div onClick={() => {}}></div>;
<span onClick={() => {}}></span>;
When <a> does not have "href" attribute, that is non-interactive.
<a onClick={() => {}}></a>
<>
<div role="button" onClick={() => {}}></div>
<span role="scrollbar" onClick={() => {}}></span>
<a href="http://example.com" onClick={() => {}}></a>
</>
Custom components are not checked.
<TestComponent onClick={doFoo} />