Svelte Vitals

svelte-vitals

When to use

Use this whenever you are writing or reviewing SvelteKit route files (+page.svelte, +layout.svelte) or components in this project — svelte-vitals statically checks SEO, performance, correctness, security, architecture, and accessibility patterns.

Playbook

1. After writing or editing code, run npx svelte-vitals . --diff --reporter agent and fix any findings it reports.
2. Before committing, run npx svelte-vitals . --staged as a pre-commit gate.
3. For a rule's full rationale, configurable options and fix examples, run npx svelte-vitals explain <rule-id> (add --json for a structured object) or open its docs link below. The fix text for a specific finding comes from the run itself, not from explain — see the note above the rule digest.
4. When a finding is correct by design — a reviewed {@html} that is already sanitized, a deliberate $effect — clear it with an inline directive instead of changing the code: <!-- svelte-vitals-disable-next-line <rule-id> --> on the line above in markup, or // svelte-vitals-disable-next-line <rule-id> inside <script>. Review it first; never suppress a finding you have not read.
5. Exit codes: 0 nothing failing, 1 a critical finding (or your --fail-on/--min-health threshold), 2 the run itself failed — a 2 says nothing about the code, so never read it as a clean or dirty result.
6. For anything else — reporters, the config file, scoping to a change, CI, monorepos — run npx svelte-vitals docs list and then npx svelte-vitals docs show <name>. Those guides ship inside the CLI, so they match the version installed here; prefer them over searching the web.

Rule digest

A Fix: below is the rule's canonical fix, the same for every occurrence. A line without one is not a rule without a fix — those rules word their fix per finding, so take it from the finding itself: recommendation on each issue in --reporter json, printed as Fix: by --reporter agent.

SEO

• seo/title-presence — Title presence (critical): A unique, non-empty is the single strongest on-page SEO signal and the text shown in search results and browser tabs. Fix: Add a inside svelte:head (a dynamic title is fine). (docs)
• seo/description-presence — Description presence (warning): A meta description is the snippet search engines show under your title; without one they invent one from page text, often poorly. Fix: Add a inside svelte:head, or set description on your meta component. (docs)
• seo/canonical-url — Canonical URL (warning): A canonical URL tells search engines which URL is authoritative, preventing duplicate-content dilution across query-string variants of the same page. Fix: Add inside svelte:head, or set the canonical prop on your meta component. (docs)
• seo/og-image — Open Graph image (warning): og:image is the preview thumbnail shown when the page is shared on social platforms; without it links render bare and get fewer clicks. Fix: Add , or set openGraph.images on your meta component. (docs)
• seo/og-title — Open Graph title (warning): og:title controls the headline shown when the page is shared on social platforms, independent of the document . Fix: Add , or set openGraph.title on your meta component. (docs)
• seo/robots-txt — robots.txt (warning): robots.txt tells crawlers which paths they may fetch and points them to your sitemap; missing it leaves crawl behaviour to defaults. Fix: Create static/robots.txt (or a src/routes/robots.txt/+server endpoint). (docs)
• seo/sitemap-xml — sitemap.xml (warning): A sitemap.xml lists your URLs so search engines can discover and prioritise them, especially pages not well linked internally. Fix: Create static/sitemap.xml (or a src/routes/sitemap.xml/+server endpoint). (docs)
• seo/json-ld — JSON-LD structured data (info): JSON-LD structured data lets search engines render rich results (breadcrumbs, articles, products) for the page. Fix: Add a JSON-LD inside svelte:head with literal JSON (Svelte emits the script body as-is). (docs)
• seo/html-lang — (warning): The attribute tells screen readers how to pronounce the page, browsers whether to offer translation, and other assistive tools how to handle the content — Google has said it does not use lang for ranking. Fix: Set the lang attribute on in src/app.html. (docs)
• seo/indexability — Indexability (info): A noindex directive removes the page from search results; an accidental noindex on a public route silently deindexes it. Fix: If this route should be indexed, drop noindex from its . (docs)
• seo/twitter-card — Twitter Card (info): twitter:card selects how the page renders when shared on X/Twitter; without it the platform falls back to a basic link (Open Graph tags are used as fallbacks for the rest). Fix: Add a twitter:card meta tag in svelte:head. (docs)
• seo/og-description — Open Graph description (info): og:description is the summary shown under the title in social previews; without it platforms guess or show nothing, lowering click-through. The Open Graph protocol lists it as an optional property. Fix: Add an og:description meta tag in svelte:head. (docs)
• seo/og-url — Open Graph URL (warning): og:url tells social platforms the canonical address to attribute shares and likes to, consolidating engagement on one URL. The Open Graph protocol lists it as a required property. Fix: Add an og:url meta tag in svelte:head. (docs)
• seo/viewport — Viewport (warning): Without a viewport meta tag mobile browsers render the page at a fixed ~980px layout viewport and scale it to fit, so text and controls end up too small to read or tap without pinch-zooming. Fix: Add the viewport meta tag (typically in src/app.html ). (docs)
• seo/sitemap-in-robots — Sitemap referenced in robots.txt (info): A Sitemap: line in robots.txt helps crawlers discover your sitemap; without it discovery relies on manual submission. Fix: Add a Sitemap: line to static/robots.txt. (docs)
• seo/json-ld-validity — JSON-LD validity (warning): Invalid JSON-LD — unparseable, missing @context/@type, or declaring a @type that is not a real schema.org type — is silently ignored by search engines, so the structured data does nothing. Fix: Make the JSON-LD valid: parseable JSON with both @context (schema.org) and @type. (docs)
• seo/json-ld-deprecated-type — Deprecated structured-data type (info): Some schema types no longer produce rich results, so the markup adds weight without the SERP benefit. (docs)
• seo/json-ld-relative-url — JSON-LD relative URL (warning): Search engines need absolute URLs in structured data; a relative URL cannot be resolved reliably. Fix: Replace relative URLs in JSON-LD with absolute URLs. (docs)
• seo/json-ld-date-format — JSON-LD date format (info): Schema.org date properties expect ISO-8601; other formats may be ignored or misparsed. Fix: Format JSON-LD date properties as ISO-8601. (docs)
• seo/json-ld-placeholder — JSON-LD placeholder text (info): Leftover placeholder text (e.g. "Your Company Name", "lorem ipsum") ships misleading structured data. (docs)
• seo/json-ld-required-props — JSON-LD required properties (warning): A recognized @type missing its required properties is ineligible for the corresponding rich result. (docs)
• seo/title-length — Title length (info): A title that is too short wastes the strongest on-page signal; one that is too long is truncated in the SERP. (docs)
• seo/description-length — Description length (info): A description that is too short under-uses the SERP snippet; one that is too long is truncated by search engines. (docs)
• seo/charset — Character encoding (warning): Without a declared character encoding the browser must guess, which can render text as mojibake; is the standard declaration. Fix: Add the charset meta tag (typically the first line of in src/app.html). (docs)
• seo/image-alt — Image alt text (warning): An with no alt attribute is invisible to image search and assistive technology; a descriptive alt is an image-SEO signal. Fix: Add a descriptive alt attribute to the (or alt="" if purely decorative). (docs)
• seo/hreflang — hreflang validity (warning): A malformed hreflang code breaks international targeting outright. A missing x-default is a Google recommendation for language-selector or auto-redirecting pages, not a defect on every multilingual site. (docs)
• seo/single-h1 — Heading hierarchy (warning): A page should have a primary heading naming its main topic. Zero leaves the page without one; a single, clear is the conventional signal, though multiple s are tolerated by modern heading algorithms. (docs)
• seo/duplicate-title — Duplicate title (warning): Duplicate titles across pages make them compete in search results and weaken each page’s relevance signal. (docs)
• seo/duplicate-description — Duplicate description (warning): Duplicate meta descriptions give search engines no per-page summary, so they are often ignored or rewritten. (docs)
• seo/heading-level-skip — Heading order (info): Skipping a heading level breaks the document outline that assistive tech relies on to navigate page structure, and that search engines use as a structural signal. (docs)
• seo/ssr-disabled — SSR disabled (warning): SvelteKit's SEO guidance is to leave SSR on unless there is a good reason not to: server-rendered content is indexed more frequently and reliably, and SPA mode costs an extra network round trip before anything renders. (docs)

Performance

• performance/image-dimensions — Image dimensions (warning): An without explicit width and height can trigger layout shift (CLS) as it loads, hurting Core Web Vitals and visual stability — unless the box is reserved another way, e.g. CSS aspect-ratio. Fix: Add explicit width and height attributes to the . (docs)
• performance/image-loading-hint — Image loading hint (info): A loading attribute lets the browser defer offscreen images; without it images load eagerly and can delay more important content. Static analysis cannot tell which image is the LCP, so this is advisory. Fix: Add loading="lazy" to offscreen elements (leave the LCP/hero image eager). (docs)
• performance/preload-missing-as — Preload missing as (warning): A <link rel="preload"> without an as attribute is ignored by the browser (or fetched a second time), wasting the preload. Fix: Add an as attribute matching the resource type to the preload link. (docs)
• performance/font-preload-crossorigin — Font preload missing crossorigin (warning): A font preload without crossorigin does not match the actual (CORS) font request, so the preloaded file is never used and the font downloads twice. Fix: Add the crossorigin attribute to the font preload link. (docs)
• performance/lcp-image — LCP image eager loading (warning): Lazy-loading the LCP (first/above-the-fold) image delays the largest paint and hurts Core Web Vitals. The first image is the best static proxy for the LCP candidate. Fix: Remove loading="lazy" from the first/LCP image; consider fetchpriority="high". (docs)
• performance/responsive-image — Responsive image (info): An without srcset ships one fixed-size asset to every device, wasting bytes on small screens. Static analysis cannot measure intended display size, so this is advisory. Fix: Add a srcset (and sizes) to the for responsive delivery. (docs)
• performance/render-blocking-script — Render-blocking script (warning): A synchronous in blocks HTML parsing until it downloads and runs, delaying first paint. defer, async, or type="module" avoids the block. Fix: Add defer (or type="module") / async to the head . (docs)
• performance/preconnect — Preconnect third-party origin (info): Connecting to a third-party origin (DNS + TCP + TLS) is costly; a preconnect/dns-prefetch hint starts it early so the resource arrives sooner. Fix: Add a preconnect hint for the third-party origin. (docs)
• performance/heavy-import — Heavy dependency import (info): Importing a large, non-tree-shakeable package pulls its whole weight into the bundle even when only a fraction is used, slowing load. (docs)
• performance/namespace-import — Namespace import (info): A namespace import (import * as X) is only tree-shakeable while every access to X stays static; passing X around or indexing it dynamically forces the bundler to keep the whole module. Named imports are reliably shakeable and make the dependency surface explicit. (docs)
• performance/minify-disabled — Minification disabled (warning): Disabling minification ships unminified JS/CSS to production, inflating bundle size several-fold and slowing every page load; the override is usually a leftover from debugging. Fix: Remove the minify: false override from vite.config (Vite minifies by default), or scope it to non-production builds. (docs)
• performance/load-waterfall — Load waterfall (warning): In a universal load, every await that depends on a previous result costs a full network round trip from the browser on client-side navigation; chains multiply latency on every page visit. A server load runs the same hops server-side. Fix: Move the dependent await chain into a server load (+page.server.ts), where hops run server-to-server. (docs)
• performance/sequential-awaits — Sequential independent awaits (info): Awaits that do not use each other's results still run one after another, adding their latencies; starting them together costs nothing and bounds the wait to the slowest request. Fix: Start the independent requests together and await them with Promise.all. (docs)
• performance/state-raw — Raw state opportunity (info): Objects and arrays in $state are made deeply reactive through proxying, which taxes every property access. A binding that is only ever reassigned — API responses are the canonical case — never uses that machinery; Svelte's own guidance is to use $state.raw for it. Fix: Replace $state(...) with $state.raw(...); keep the same initializer. (docs)
• performance/iframe-loading — Iframe loading attribute (info): An iframe without a loading attribute loads eagerly, and an offscreen iframe (embedded video player, map, ad slot) typically loads an entire third-party document — scripts, fonts, media — so its bandwidth and main-thread cost is usually larger than an offscreen image’s. loading="lazy" defers it until the viewport approaches. Static analysis cannot tell whether the iframe is above the fold, so this is advisory. Fix: Add loading="lazy" to iframes that can be offscreen on load. (docs)

Correctness

• correctness/each-key — Keyed each block (warning): An unkeyed {#each} adds/removes nodes at the end and rewrites the data of the DOM nodes in between when the list reorders, so element state/focus sticks to positions instead of items; a key lets Svelte insert, move, and delete the right nodes instead. (docs)
• correctness/each-index-key — Index used as each key (warning): Svelte's guidance is explicit: the key must uniquely identify the object — do not use the index. An index key gives items position-based identity, so element state (focus, inputs, transitions) sticks to positions when the list reorders or items are inserted or removed, exactly like an unkeyed block — but the visible key masks the problem. (docs)
• correctness/effect-as-derived — Effect used to derive state (warning): An $effect whose body only assigns to $state is the "useEffect → $effect" anti-pattern: it reruns after render and can cause extra passes or loops. $derived expresses the same dependency declaratively. (docs)
• correctness/effect-as-onmount — Effect used as onMount (warning): An $effect whose body reads no reactive value visible to this analysis runs once after mount and never re-runs on the paths it can see — usually a sign the code belongs in an event handler, {@attach}, or onMount instead of $effect. This can't see a reactive value reached only through a plain function's return value, so a genuinely reactive effect built that way can still be flagged. (docs)
• correctness/unmutated-state — Unmutated $state (info): A $state that is never mutated pays for reactivity (deep proxying, tracking) it never uses; const (or $state.raw) is clearer and cheaper. (docs)
• correctness/prop-mutation — Mutated non-bindable prop (warning): Svelte's docs say plainly: don't mutate props unless they are $bindable. A plain-object prop mutation is a silent no-op (the object isn't a state proxy); a reactive-state-proxy prop mutation works but triggers the ownership_invalid_mutation dev warning only when that code path actually runs. In legacy mode, mutating methods like .push()/.splice() never trigger an update on their own — Svelte's reactivity there is based on assignments, not mutations. Neither case is caught by the compiler, so this rule catches both statically. (docs)
• correctness/stale-prop-derivation — Stale prop derivation (warning): Svelte's guidance is to treat props as though they will change: a plain let color = type === 'danger' ? 'red' : 'green' freezes the first render's value, so the UI silently stops tracking the parent when the prop changes. In runes mode, $derived keeps the computation live at no cost; in legacy mode (export let props), a $: reactive statement does the same job. Fix: Wrap the prop-derived computation in $derived(...) (or $derived.by(() => ...) for a function body) in runes mode, or prefix the assignment with $: in legacy mode, keeping the same expression. (docs)
• correctness/nonreactive-builtin-state — Non-reactive built-in in $state (warning): $state deep-proxies plain objects and arrays only; built-in collection, date, and URL instances stay untracked, so property-level changes never reach effects, deriveds, or the template. Svelte's own answer is the drop-in classes in svelte/reactivity. Fix: Import Svelte from 'svelte/reactivity' and replace new (...) with new Svelte(...) — the API is identical. (docs)
• correctness/checkable-bind-value — bind:value on a checkable input (warning): bind:value binds the DOM value property. A checkbox/radio's user interaction toggles checkedness, which bind:value never observes. On a checkbox this throws bind_invalid_checkbox_value in a development build; in production the check is skipped and the binding silently tracks the value attribute instead of checkedness. On a radio it throws nothing in either build — it renders once with the initial value, then silently never updates. Svelte's checked/grouped bindings (bind:checked, bind:group) are built for exactly this. Fix: For a single checkbox, replace bind:value={x} with bind:checked={x} (x becomes a boolean). For a checkbox list or radio group, replace bind:value={x} with bind:group={x} on every input sharing the group, keeping each input's static value attribute to identify the option. (docs)
• correctness/autoplay-muted — Autoplay video without muted (warning): Browser autoplay policies block autoplay with audio: Chrome and Safari only honour autoplay when the video is muted (or the site has earned an autoplay allowance; a video with no audio track may also be allowed). A blocked autoplay does not throw — the video just never starts, so the page ships with a frozen poster frame for real visitors while working in development, where prior interaction often unlocks autoplay for the session. Adding muted is harmless even where autoplay would have been allowed. Fix: Add the muted attribute (and typically playsinline) to the autoplaying video. (docs)
• correctness/orphan-effect — Orphan $effect (critical): An $effect created outside component initialisation throws effect_orphan at runtime. The compiler does not catch it — the server compiler deletes $effect calls entirely, so SSR renders without error — and the crash happens client-side, when the module evaluates in the browser, breaking hydration rather than producing a server error. (docs)
• correctness/orphan-lifecycle — Lifecycle call outside component initialisation (critical): Svelte lifecycle and context functions require an active component context; called at module scope, in a shared-state class constructor, or in a load/handler they throw lifecycle_outside_component at runtime — the compiler does not catch it, and it surfaces as a production crash. Exception: in a Kit module that only ever runs on the server (+page.server.ts, +server.ts, hooks.server.ts), onMount/beforeUpdate/afterUpdate/createEventDispatcher are silent no-ops there instead, and onDestroy throws a plain TypeError rather than lifecycle_outside_component — only getContext/setContext/hasContext/getAllContexts still throw in that channel. (docs)
• correctness/base-path-navigation — Root-relative navigation under a base path (warning): A root-relative literal resolves against the domain root, not kit.paths.base, so navigation lands outside an app served from a sub-path. The break only appears once the app is deployed under its base — locally base is usually empty, so every such link works. Fix: Import { resolve } from '$app/paths' and wrap the path: href={resolve('/about')}, goto(resolve('/about')), redirect(303, resolve('/login')). (docs)
• correctness/server-browser-global — Browser global in server module code (critical): window, document, localStorage and friends do not exist on the server; a read in module scope or a load/handler crashes SSR with a ReferenceError — the compiler does not catch it, and it surfaces as a production 500. (docs)
• correctness/instance-browser-global — Browser global during component initialisation (warning): A component instance script runs on the server on every SSR render, where window/document/localStorage do not exist. Warning, not critical: a component rendered only behind a parent {#if browser} (or a client-only dynamic import) is a legitimate pattern that static analysis cannot prove cross-file. (docs)

Security

• security/raw-html — Raw HTML render (warning): {@html} renders its value as unescaped HTML; if the value can contain user input and is not sanitized, it is a cross-site-scripting (XSS) vector. (docs)
• security/javascript-url — javascript: URL (warning): A javascript: URL in href/src/action/formaction breaks under a strict Content-Security-Policy and turns what should be a real navigation into inline script execution on activation — use an event handler on a instead (the same shape is also a classic XSS vector, though detection here is literal-only, so every flagged URL is author-written, not injected). (docs)
• security/handler-state-write — Handler writes imported state (critical): SvelteKit's docs mark this NEVER-DO-THIS: the server is one long-lived process shared by every user, so module state written during a request is visible to ALL later requests. (docs)
• security/server-module-state — Server module-scope state (warning): Module scope on the server is one shared, long-lived instance (SvelteKit docs: "Avoid shared state on the server"): a value reassigned during one user's request is served to every other user, and it silently resets on every deploy or restart. (docs)
• security/shared-state-import — Shared runes-state import on the server (warning): A .svelte.ts module with module-scope $state is one shared instance on the server: mutated, it leaks data between users; read-only, every request sees the same boot-time value instead of per-user data. (docs)

Architecture

• architecture/component-size — Component size (info): A very large component is hard to read, test, and reuse, and is a common sign that several responsibilities should be split out. (docs)
• architecture/prop-count — Prop count (info): A component taking many props is usually doing too much; grouping or splitting keeps its API understandable. (docs)
• architecture/private-scope-import — Private-scope import (info): A unit placed inside a private directory is written for one owner; importing it from elsewhere couples two parts of the tree that were meant to move independently, and the unit belongs higher up instead. Fix: Move this unit out of its private scope, to the directory shared by all of its importers, and update this import. (inert until configured) (docs)
• architecture/unit-entry-file — Unit entry file (info): A directory named after a unit but missing that unit's entry file is either an incomplete unit or a grouping wearing the wrong name; either way the tree no longer says what it means, and tooling that resolves by convention starts guessing. Fix: Make the directory and its entry file agree — add the entry file, or stop declaring this directory a unit. (inert until configured) (docs)
• architecture/directory-naming — Directory naming (info): A directory whose name breaks the convention its location declares stops carrying the meaning the convention gave it, and every reader — human or agent — has to open the directory to learn what it is. Fix: Rename the directory to the declared casing, or narrow the declaration that governs it. (inert until configured) (docs)
• architecture/reserved-directory-names — Reserved directory names (info): A closed set of directory names is only worth writing down if it stays closed: one directory outside it and the table stops describing the tree, so every reader has to open a directory to learn what it holds. Fix: Rename the directory to a declared name, move it under one of them, or add its name to the declaration. (inert until configured) (docs)
• architecture/reserved-name-placement — Reserved name placement (info): A name reserved for one kind of place stops carrying that meaning the moment it appears somewhere else: a reader who has met one exception has to open the directory to learn what it holds. Fix: Move the directory to one of the places declared for its name, rename it, or declare this place for the name. (inert until configured) (docs)
• architecture/route-component-import — Route component import (info): A route entry is written on the assumption that SvelteKit renders it: Kit hands a page its data and params, and an error page its page.error and page.status. Imported from somewhere else it receives none of that and renders against nothing, or against the importing page data standing in for its own. (docs)
• architecture/doc-link-target — Documentation link target (info): A documentation link written in a comment is invisible to type checking, module resolution and the test runner, so a convention-driven rename leaves it pointing at nothing and only human review notices. (inert until configured) (docs)

Accessibility

• a11y/invalid-role — Invalid ARIA role (warning): A role that does not exist in WAI-ARIA (or is abstract, reserved for the spec itself) is ignored or misread by assistive technology, silently breaking the element’s announced semantics. (docs)
• a11y/unknown-aria-attribute — Unknown ARIA attribute (warning): An aria-* name that does not exist in WAI-ARIA is not recognized by assistive technology, so the attribute is silently ignored instead of doing what the author intended. (docs)
• a11y/required-aria-props — Missing required ARIA props (warning): Some WAI-ARIA roles are unusable to assistive technology without their required state/property attributes — a role="checkbox" with no way to know checked/unchecked announces a control with no discoverable state. (docs)
• a11y/invalid-aria-value — Invalid ARIA attribute value (warning): An aria-* attribute whose value does not match its spec-defined type (e.g. a boolean given a non-true/false literal) is misread or ignored by assistive technology. (docs)
• a11y/interactive-nesting — Interactive element nested in an interactive element (warning): A control nested inside another interactive element is announced and operated inconsistently across browsers and assistive technology, and inside an <a href> or a <button> it also violates the HTML content model, which forbids interactive descendants. (docs)
• a11y/aria-hidden-focus — Focusable element hidden by aria-hidden (warning): An element inside aria-hidden="true" stays keyboard-reachable while assistive technology announces nothing for it — a screen reader user lands on a control that does not exist for them. The author cannot see this defect: aria-hidden changes nothing visually, so only assistive-technology users ever encounter it. (docs)
• a11y/accessible-name — Interactive element has no accessible name (warning): A button, link, or image button with no accessible name is announced by assistive technology as its bare role ("button", "link") with nothing to distinguish it from any other control on the page; an iframe without one is announced as an unnamed frame, with no way to tell an embedded video from an ad slot before entering it. (docs)
• a11y/label-has-control — has no associated control (warning): A <label> with no associated control is announced by assistive technology as plain text — clicking or tapping it does not focus the field, and a screen reader gives no relationship between the label and its control. (docs)
• a11y/use-list — Bullet text should be a list (info): A screen reader announces a real <ul>/<ol> as a list — item count, position, and boundaries. A bullet character typed into plain text carries none of that, so the visual structure is lost on assistive technology. (docs)
• a11y/placeholder-label-option — Missing placeholder label option (warning): A required, single-selection <select> initially shows its first option as the chosen value — if that option is not an empty placeholder, users can submit the form without ever having made a real choice, and assistive technology announces a value as already selected. (docs)
• a11y/require-datetime — Missing datetime attribute (info): A <time> element with no datetime attribute exposes its text content as the machine-readable value, and the HTML spec requires that text to be a valid date/time string. Text like "last Tuesday" reads fine but is not one, so the element exposes no standardized date — a consumer that wants it is left guessing at prose instead of reading a value. (docs)
• a11y/positive-tabindex — Positive tabindex (warning): A tabindex greater than 0 puts the element ahead of every naturally-ordered element on the page — a single tabindex="1" reorders keyboard navigation for the whole document, and the damage compounds with every element added later. The tab order can then diverge from the visual order, which WCAG 2.4.3 (Focus Order) requires to stay meaningful. Fix: Replace the positive tabindex with tabindex="0" and move the element into DOM order, or tabindex="-1" if it is only focused programmatically. (docs)
• a11y/no-accesskey — Accesskey attribute (warning): The accesskey attribute assigns a page-level shortcut key, but the actual key combination varies by browser and OS, is undiscoverable to users, and routinely conflicts with screen reader and browser keyboard bindings. Long-standing accessibility guidance is to not use it. Fix: Remove the accesskey attribute. (docs)
• a11y/no-autofocus — Autofocus outside a dialog (warning): autofocus moves focus on page load without the user asking, skipping everything before the target — screen reader users lose the page context they were building, and keyboard users are dropped mid-page. Inside a or a popover it is the correct tool (their focusing steps run on show, not on load); anywhere else it is almost always a usability bug. Fix: Remove the autofocus attribute, or move the element inside the /popover container it is meant to focus. (docs)
• a11y/no-duplicate-dt — Duplicate names in a (info): Within a single dl element, there should not be more than one dt element for each name — the HTML spec calls this out explicitly, and a duplicated term usually means a copy-paste error where two descriptions were meant to share one dt. Fix: Merge the duplicated terms into one followed by both descriptions, or rename one of them. (docs)
• a11y/abbr-title — Abbreviation without an expansion (info): marks an abbreviation, but without a title giving the expansion the element adds no information — visual users get no tooltip and assistive technology has nothing to expand. The spec keeps title optional (an expansion in the surrounding text is also fine), so this is a nudge toward the common case, not a conformance requirement. Fix: Add a title attribute with the expansion, or spell the term out at first use. (docs)
• a11y/pattern-title — Pattern input without a format description (info): When an has a pattern attribute, the spec says a

…(truncated)