Svelte warns you at compile time if it catches potential mistakes, such as writing inaccessible markup.
Some warnings may be incorrect in your concrete use case. You can disable such false positives by placing a `` comment above the line that causes the warning. Example:
```svelte
```
You can list multiple rules in a single comment (separated by commas), and add an explanatory note (in parentheses) alongside them:
```svelte
...
```
### a11y\_accesskey
```
Avoid using accesskey
```
Enforce no `accesskey` on element. Access keys are HTML attributes that allow web developers to assign keyboard shortcuts to elements. Inconsistencies between keyboard shortcuts and keyboard commands used by screen reader and keyboard-only users create accessibility complications. To avoid complications, access keys should not be used.
```svelte
```
### a11y\_aria\_activedescendant\_has\_tabindex
```
An element with an aria-activedescendant attribute should have a tabindex value
```
An element with `aria-activedescendant` must be tabbable, so it must either have an inherent `tabindex` or declare `tabindex` as an attribute.
```svelte
```
### a11y\_aria\_attributes
```
`<%name%>` should not have aria-* attributes
```
Certain reserved DOM elements do not support ARIA roles, states and properties. This is often because they are not visible, for example `meta`, `html`, `script`, `style`. This rule enforces that these DOM elements do not contain the `aria-*` props.
```svelte
```
### a11y\_autocomplete\_valid
```
'%value%' is an invalid value for 'autocomplete' on ``
```
### a11y\_autofocus
```
Avoid using autofocus
```
Enforce that `autofocus` is not used on elements. Autofocusing elements can cause usability issues for sighted and non-sighted users alike.
```svelte
```
### a11y\_click\_events\_have\_key\_events
```
Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `