@ttsc/lint 0.13.0 → 0.14.0-dev.20250530.1

package/src/structures/rules/ITtscLintJestRules.ts

@@ -0,0 +1,209 @@
+import type { TtscLintRuleSetting } from "../TtscLintRuleSetting";
+
+/**
+ * Jest test source rules from `eslint-plugin-jest`.
+ *
+ * Apply to TypeScript test files that use the Jest runner (`describe`,
+ * `test`/`it`, `expect`, lifecycle hooks). They guard test-quality patterns the
+ * type system cannot detect — unended assertions, focused tests left behind,
+ * duplicate hook calls.
+ *
+ * @reference https://github.com/jest-community/eslint-plugin-jest
+ */
+export interface ITtscLintJestRules {
+  /**
+   * Require every Jest test body to contain at least one `expect(...)` call. A
+   * test with no expectations passes silently.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/expect-expect.md
+   */
+  "jest/expect-expect"?: TtscLintRuleSetting;
+
+  /**
+   * Limit the number of `expect(...)` calls inside a single Jest test body.
+   *
+   * A test packed with assertions usually verifies several behaviors at once,
+   * making failures ambiguous — splitting per scenario keeps each case
+   * diagnostic.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/max-expects.md
+   */
+  "jest/max-expects"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `expect(...)` calls under `if`/`try`/`catch` or other conditional
+   * branches in Jest tests.
+   *
+   * A branch that never executes turns the assertion into a silent no-op, so
+   * the test passes without verifying anything.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-conditional-expect.md
+   */
+  "jest/no-conditional-expect"?: TtscLintRuleSetting;
+
+  /**
+   * Reject conditional logic (`if`/`switch`/ternary) inside Jest test bodies.
+   *
+   * Each test should describe a single deterministic scenario; branching hides
+   * which path the runner took when reading a passing log.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-conditional-in-test.md
+   */
+  "jest/no-conditional-in-test"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `test.skip`, `xit`, `xdescribe`, and other disabled Jest tests.
+   *
+   * Skipped tests appear green in CI but quietly drop coverage for the feature
+   * they were meant to pin, so they rot unseen.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-disabled-tests.md
+   */
+  "jest/no-disabled-tests"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `done` callback parameters in Jest tests and hooks.
+   *
+   * The callback style predates async/await and makes error propagation easy to
+   * miss — forgetting `done()` hangs the test until timeout. Use
+   * `async`/`await` or return a Promise instead.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-done-callback.md
+   */
+  "jest/no-done-callback"?: TtscLintRuleSetting;
+
+  /**
+   * Reject duplicate setup/teardown hook calls (`beforeEach`/`beforeAll`/etc.)
+   * within the same `describe` block.
+   *
+   * Jest runs both copies in declaration order, which is almost always a
+   * copy-paste mistake.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-duplicate-hooks.md
+   */
+  "jest/no-duplicate-hooks"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `export` declarations in Jest test files.
+   *
+   * Tests are leaf consumers and should not expose helpers; the runner silently
+   * skips test files with any export, so a stray `export` can make a whole file
+   * disappear from the suite.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-export.md
+   */
+  "jest/no-export"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `test.only`, `fit`, `fdescribe`, and other focused Jest tests.
+   *
+   * A focused test silently skips every other test in the file, so a stray
+   * `.only` left from debugging hides the rest of the suite in CI.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-focused-tests.md
+   */
+  "jest/no-focused-tests"?: TtscLintRuleSetting;
+
+  /**
+   * Reject Jest setup/teardown hooks altogether.
+   *
+   * Promotes the style where each test arranges and tears down its own state
+   * inline, so a reader can understand it in isolation without scrolling to a
+   * distant `beforeEach`.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-hooks.md
+   */
+  "jest/no-hooks"?: TtscLintRuleSetting;
+
+  /**
+   * Reject duplicate test or `describe` titles at the same suite level — the
+   * runner cannot distinguish two tests with the same name in error output.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-identical-title.md
+   */
+  "jest/no-identical-title"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `expect(...)` calls outside the body of a Jest test or lifecycle
+   * hook.
+   *
+   * Top-level assertions execute at module load before any test starts, so
+   * failures never attach to a named case in the runner's report.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-standalone-expect.md
+   */
+  "jest/no-standalone-expect"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `xit`, `fit`, `xdescribe`, `fdescribe`, and the rest of the
+   * single-letter Jest test prefix aliases.
+   *
+   * They duplicate the `.only`/`.skip` variants but read as typos at a glance,
+   * making accidental focus or disable harder to spot in review.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-test-prefixes.md
+   */
+  "jest/no-test-prefixes"?: TtscLintRuleSetting;
+
+  /**
+   * Reject non-Promise `return` statements from Jest test bodies.
+   *
+   * Jest only awaits returned thenables, so a plain `return` value is dropped
+   * and following code becomes dead — usually a symptom of a missing `await` or
+   * an accidental early exit.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/no-test-return-statement.md
+   */
+  "jest/no-test-return-statement"?: TtscLintRuleSetting;
+
+  /**
+   * Prefer `expect(value).toHaveLength(n)` over asserting on `value.length`
+   * directly with `toBe`.
+   *
+   * The dedicated matcher reports the actual length on failure instead of a
+   * bare number mismatch with no context.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/prefer-to-have-length.md
+   */
+  "jest/prefer-to-have-length"?: TtscLintRuleSetting;
+
+  /**
+   * Require a message argument on `expect(...).toThrow(...)` so a regression
+   * with a different error type still surfaces clearly.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/require-to-throw-message.md
+   */
+  "jest/require-to-throw-message"?: TtscLintRuleSetting;
+
+  /**
+   * Validate the shape of Jest `describe` callbacks.
+   *
+   * The callback must be synchronous and take no arguments — Jest ignores
+   * returned Promises and `done`-style parameters at the describe level,
+   * silently swallowing setup errors.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/valid-describe-callback.md
+   */
+  "jest/valid-describe-callback"?: TtscLintRuleSetting;
+
+  /**
+   * Validate `expect(...)` arity and matcher chaining: exactly one argument,
+   * terminated by a matcher call, and async matchers properly awaited.
+   *
+   * Malformed expects either throw at runtime or pass without asserting
+   * anything.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/valid-expect.md
+   */
+  "jest/valid-expect"?: TtscLintRuleSetting;
+
+  /**
+   * Require non-empty static Jest test and `describe` titles.
+   *
+   * Empty or dynamically-built titles produce unreadable failure output and
+   * break filter-by-name flags like `--testNamePattern`.
+   *
+   * @reference https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/valid-title.md
+   */
+  "jest/valid-title"?: TtscLintRuleSetting;
+}

package/src/structures/rules/ITtscLintJsdocRules.ts

@@ -0,0 +1,146 @@
+import type { TtscLintRuleSetting } from "../TtscLintRuleSetting";
+
+/**
+ * Documentation-comment validation rules.
+ *
+ * Bundles `eslint-plugin-jsdoc` content checks (tag names, parameter coverage,
+ * descriptions) with the lone `eslint-plugin-tsdoc` syntax check
+ * (`jsdoc/tsdoc-syntax`) — both target `/** ... *\/` comments and are too small
+ * in upstream-tsdoc's case to justify a dedicated family.
+ *
+ * Formatting concerns (alignment, indentation) are configured through the
+ * top-level `format` block, not here.
+ *
+ * @reference https://github.com/gajus/eslint-plugin-jsdoc
+ */
+export interface ITtscLintJsdocRules {
+  /**
+   * Reject unknown JSDoc block-tag names. Catches typos like `@returs` or
+   * `@parm`.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/check-tag-names.md
+   */
+  "jsdoc/check-tag-names"?: TtscLintRuleSetting;
+
+  /**
+   * Validate `@access` values against the closed set `public`, `protected`,
+   * `private`, `package`. (Upstream extends to
+   * `@version`/`@since`/`@license`/`@kind`/`@import` value checks; those shapes
+   * are not yet implemented in the native engine.)
+   *
+   * Catches typos and stale enum members that slip past doc tooling.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/check-values.md
+   */
+  "jsdoc/check-values"?: TtscLintRuleSetting;
+
+  /**
+   * Reject content on marker-only JSDoc tags (`@async`, `@public`, `@override`,
+   * ...) — these tags take no value.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/empty-tags.md
+   */
+  "jsdoc/empty-tags"?: TtscLintRuleSetting;
+
+  /**
+   * Reject JSDoc type braces in TypeScript sources, since the surrounding
+   * TypeScript already carries the type.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/no-types.md
+   */
+  "jsdoc/no-types"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `any` and `*` inside JSDoc type braces — these escape the documented
+   * type system the same way TypeScript `any` does.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/reject-any-type.md
+   */
+  "jsdoc/reject-any-type"?: TtscLintRuleSetting;
+
+  /**
+   * Reject the unsafe `Function` type inside JSDoc type braces.
+   *
+   * Mirrors the `typescript/no-unsafe-function-type` rule from
+   * {@link ITtscLintTypeScriptRules} for JSDoc comments.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/reject-function-type.md
+   */
+  "jsdoc/reject-function-type"?: TtscLintRuleSetting;
+
+  /**
+   * Require JSDoc blocks to include a leading block-level description — every
+   * documented identifier should explain itself.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/require-description.md
+   */
+  "jsdoc/require-description"?: TtscLintRuleSetting;
+
+  /**
+   * Require every `@param` tag that names a parameter to also carry a
+   * description after the name.
+   *
+   * A name-only `@param` adds nothing beyond the signature, so the rule pushes
+   * authors to either describe the parameter or drop the tag.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/require-param-description.md
+   */
+  "jsdoc/require-param-description"?: TtscLintRuleSetting;
+
+  /**
+   * Require every `@param` tag to include the parameter name it documents.
+   *
+   * A bare `@param` cannot be linked to a signature position, so doc tooling
+   * silently drops it.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/require-param-name.md
+   */
+  "jsdoc/require-param-name"?: TtscLintRuleSetting;
+
+  /**
+   * Require every `@property` tag that names a property to also carry a
+   * description.
+   *
+   * Mirrors `require-param-description` for typedef and object-shape comments,
+   * where a name-only entry adds nothing the surrounding type doesn't convey.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/require-property-description.md
+   */
+  "jsdoc/require-property-description"?: TtscLintRuleSetting;
+
+  /**
+   * Require every `@property` tag to include the property name it documents.
+   *
+   * Without the name the tag cannot be linked to a member of the surrounding
+   * typedef, and doc generators discard it.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/require-property-name.md
+   */
+  "jsdoc/require-property-name"?: TtscLintRuleSetting;
+
+  /**
+   * Require every `@returns` tag to carry a description of the returned value.
+   *
+   * The TypeScript signature already states the return type, so the tag earns
+   * its keep only when it explains what the value means, not its shape.
+   *
+   * @reference https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/require-returns-description.md
+   */
+  "jsdoc/require-returns-description"?: TtscLintRuleSetting;
+
+  /**
+   * Detect structural TSDoc problems in documentation comments: malformed
+   * top-level block tags (`@` followed by non-letter) and malformed or unclosed
+   * inline tags (`{@link ...}`). The broader TSDoc grammar — closed-set tag
+   * names, escape sequences, `{Type}`-annotation rejection, fenced-code rules —
+   * is not yet implemented.
+   *
+   * TSDoc is Microsoft's curated dialect that powers API Extractor and the rest
+   * of the Microsoft TypeScript documentation pipeline. Upstream
+   * `eslint-plugin-tsdoc` ships exactly one rule; it lives here rather than in
+   * a one-rule `tsdoc/*` family.
+   *
+   * @reference https://github.com/microsoft/tsdoc/blob/main/eslint-plugin/README.md
+   */
+  "jsdoc/tsdoc-syntax"?: TtscLintRuleSetting;
+}

package/src/structures/rules/ITtscLintJsxA11yRules.ts

@@ -0,0 +1,331 @@
+import type { TtscLintRuleSetting } from "../TtscLintRuleSetting";
+
+/**
+ * JSX accessibility rules from `eslint-plugin-jsx-a11y`, applied to TSX (and
+ * JSX-in-TS) sources.
+ *
+ * Checks the static structure of JSX elements against WAI-ARIA authoring
+ * guidance — interactive controls should be focusable, labels should reference
+ * a control, ARIA properties should match the element role, and so on. Runtime
+ * accessibility issues require live audits; this family catches the
+ * statically-decidable subset.
+ *
+ * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y
+ */
+export interface ITtscLintJsxA11yRules {
+  /**
+   * Require image-like JSX elements (`<img>`, `<input type="image">`,
+   * `<object>`, `<area>`) to expose alt text or an ARIA label.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/alt-text.md
+   */
+  "jsx-a11y/alt-text"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `<a>` elements whose visible text is one of a small set of phrases
+   * that carry no information out of context. Screen-reader users navigate by
+   * listing links — "click here" / "more" / "read more" turn that list into
+   * noise.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/anchor-ambiguous-text.md
+   */
+  "jsx-a11y/anchor-ambiguous-text"?: TtscLintRuleSetting;
+
+  /**
+   * Reject empty JSX anchors with no accessible content (text, `aria-label`, or
+   * labelled child).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/anchor-has-content.md
+   */
+  "jsx-a11y/anchor-has-content"?: TtscLintRuleSetting;
+
+  /**
+   * Reject anchors with missing, `#`-only, empty, or `javascript:` `href`
+   * values, all of which break navigation semantics.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/anchor-is-valid.md
+   */
+  "jsx-a11y/anchor-is-valid"?: TtscLintRuleSetting;
+
+  /**
+   * Require `tabIndex` on any element carrying `aria-activedescendant` unless
+   * the tag is already focusable by default (`<input>`, etc.) — the
+   * composite-widget host must keep document focus for the descendant id to do
+   * anything.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-activedescendant-has-tabindex.md
+   */
+  "jsx-a11y/aria-activedescendant-has-tabindex"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `aria-*` JSX attribute names that are not part of the WAI-ARIA
+   * States and Properties spec — catches typos such as `aria-labeledby`
+   * (missing second `l`) that silently disable assistive-tech support.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-props.md
+   */
+  "jsx-a11y/aria-props"?: TtscLintRuleSetting;
+
+  /**
+   * Validate literal values supplied to ARIA properties against the type the
+   * spec declares for them — e.g. `aria-checked` must be one of `true`,
+   * `false`, `"mixed"`, and `aria-hidden="yes"` is rejected because the type is
+   * boolean.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-proptypes.md
+   */
+  "jsx-a11y/aria-proptypes"?: TtscLintRuleSetting;
+
+  /**
+   * Require `role` values to be a concrete, non-abstract WAI-ARIA role
+   * (`"button"`, `"checkbox"`, ...). Rejects misspellings and abstract roles
+   * like `"range"`; computed values are skipped because the concrete role
+   * cannot be checked statically.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-role.md
+   */
+  "jsx-a11y/aria-role"?: TtscLintRuleSetting;
+
+  /**
+   * Reject ARIA roles and attributes on elements that do not support them (e.g.
+   * `aria-checked` on a `<meta>` tag).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/aria-unsupported-elements.md
+   */
+  "jsx-a11y/aria-unsupported-elements"?: TtscLintRuleSetting;
+
+  /**
+   * Validate the literal `autocomplete` token against the HTML spec vocabulary
+   * and against the `type` of the surrounding input — e.g. `autocomplete="url"`
+   * on `<input type="email">` is rejected because the two sets do not overlap.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/autocomplete-valid.md
+   */
+  "jsx-a11y/autocomplete-valid"?: TtscLintRuleSetting;
+
+  /**
+   * Require keyboard handlers alongside `onClick` on non-interactive JSX
+   * elements so the element is also reachable by keyboard.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/click-events-have-key-events.md
+   */
+  "jsx-a11y/click-events-have-key-events"?: TtscLintRuleSetting;
+
+  /**
+   * Require interactive controls to have an accessible label (visible text,
+   * `aria-label`, or `aria-labelledby`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/control-has-associated-label.md
+   */
+  "jsx-a11y/control-has-associated-label"?: TtscLintRuleSetting;
+
+  /**
+   * Reject empty JSX headings (`<h1>{}</h1>`) — assistive technology cannot
+   * announce content that does not exist.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/heading-has-content.md
+   */
+  "jsx-a11y/heading-has-content"?: TtscLintRuleSetting;
+
+  /**
+   * Require `<html>` JSX elements to declare a non-empty `lang` attribute so
+   * screen readers can pick the correct pronunciation. Largely superseded by
+   * `jsx-a11y/lang`, which also validates the tag value.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/html-has-lang.md
+   */
+  "jsx-a11y/html-has-lang"?: TtscLintRuleSetting;
+
+  /**
+   * Require every `<iframe>` JSX element to declare a non-empty, unique `title`
+   * so assistive tech can announce the embedded content. Empty strings,
+   * booleans, numbers, and `{...spread}` without a literal title are all
+   * flagged.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/iframe-has-title.md
+   */
+  "jsx-a11y/iframe-has-title"?: TtscLintRuleSetting;
+
+  /**
+   * Reject redundant words such as _image_, _photo_, or _picture_ inside the
+   * `alt` attribute of an `<img>` — the role already conveys "this is an
+   * image".
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/img-redundant-alt.md
+   */
+  "jsx-a11y/img-redundant-alt"?: TtscLintRuleSetting;
+
+  /**
+   * Require elements with interactive ARIA roles (`role="button"`,
+   * `role="link"`, ...) to be focusable.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/interactive-supports-focus.md
+   */
+  "jsx-a11y/interactive-supports-focus"?: TtscLintRuleSetting;
+
+  /**
+   * Require `<label>` elements to either wrap a form control or reference one
+   * via `htmlFor`.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/label-has-associated-control.md
+   */
+  "jsx-a11y/label-has-associated-control"?: TtscLintRuleSetting;
+
+  /**
+   * Deprecated predecessor of `label-has-associated-control`. Checks the same
+   * nesting / `htmlFor` association requirement and supports configuring which
+   * custom components count as labels. Off in `recommended`; kept only for
+   * legacy configs.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/label-has-for.md
+   */
+  "jsx-a11y/label-has-for"?: TtscLintRuleSetting;
+
+  /**
+   * Require the `<html lang>` value to be a valid IETF BCP-47 tag (`"en"`,
+   * `"en-US"`, ...). Superset of `html-has-lang`, since it also catches
+   * present-but-invalid tags like `lang="foo"`.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/lang.md
+   */
+  "jsx-a11y/lang"?: TtscLintRuleSetting;
+
+  /**
+   * Require `<audio>` and `<video>` elements to provide a `<track
+   * kind="captions">` child.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/media-has-caption.md
+   */
+  "jsx-a11y/media-has-caption"?: TtscLintRuleSetting;
+
+  /**
+   * Require `onMouseOver` / `onMouseOut` handlers to have `onFocus` / `onBlur`
+   * parity so keyboard users get the same interaction.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/mouse-events-have-key-events.md
+   */
+  "jsx-a11y/mouse-events-have-key-events"?: TtscLintRuleSetting;
+
+  /**
+   * Reject the `accessKey` JSX attribute — it conflicts with
+   * assistive-technology keyboard shortcuts.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-access-key.md
+   */
+  "jsx-a11y/no-access-key"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `aria-hidden` on focusable JSX elements — focus would land on an
+   * element hidden from assistive tech.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-aria-hidden-on-focusable.md
+   */
+  "jsx-a11y/no-aria-hidden-on-focusable"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `autoFocus` / `autofocus` JSX attributes — they steal focus on page
+   * load and disorient keyboard users.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-autofocus.md
+   */
+  "jsx-a11y/no-autofocus"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `<blink>` and `<marquee>` — moving content cannot be paused and
+   * harms users with cognitive or visual impairments (WCAG 2.2.2). The list is
+   * closed: extra elements cannot be added.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-distracting-elements.md
+   */
+  "jsx-a11y/no-distracting-elements"?: TtscLintRuleSetting;
+
+  /**
+   * Reject non-interactive ARIA roles applied to natively interactive elements
+   * (e.g. `<button role="presentation">`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-interactive-element-to-noninteractive-role.md
+   */
+  "jsx-a11y/no-interactive-element-to-noninteractive-role"?: TtscLintRuleSetting;
+
+  /**
+   * Reject interaction event handlers (`onClick`, `onKeyDown`) placed on known
+   * non-interactive elements without a role override.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-noninteractive-element-interactions.md
+   */
+  "jsx-a11y/no-noninteractive-element-interactions"?: TtscLintRuleSetting;
+
+  /**
+   * Reject interactive ARIA roles applied to non-interactive elements (e.g.
+   * `<li role="button">`); use the matching interactive tag.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-noninteractive-element-to-interactive-role.md
+   */
+  "jsx-a11y/no-noninteractive-element-to-interactive-role"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `tabIndex` on non-interactive JSX elements that have no interactive
+   * role.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-noninteractive-tabindex.md
+   */
+  "jsx-a11y/no-noninteractive-tabindex"?: TtscLintRuleSetting;
+
+  /**
+   * Reject explicit `role` attributes that duplicate the native semantics of
+   * the element (e.g. `<button role="button">`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-redundant-roles.md
+   */
+  "jsx-a11y/no-redundant-roles"?: TtscLintRuleSetting;
+
+  /**
+   * Require static elements with interaction handlers to declare an interactive
+   * `role`.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-static-element-interactions.md
+   */
+  "jsx-a11y/no-static-element-interactions"?: TtscLintRuleSetting;
+
+  /**
+   * Prefer native JSX tags over `div` / `span` plus an equivalent `role` (e.g.
+   * `<button>` over `<div role="button">`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/prefer-tag-over-role.md
+   */
+  "jsx-a11y/prefer-tag-over-role"?: TtscLintRuleSetting;
+
+  /**
+   * Require ARIA properties that the chosen role mandates (e.g. `aria-checked`
+   * on `role="checkbox"`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/role-has-required-aria-props.md
+   */
+  "jsx-a11y/role-has-required-aria-props"?: TtscLintRuleSetting;
+
+  /**
+   * Reject ARIA properties that the role does not support (e.g. `aria-checked`
+   * on `role="link"`).
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/role-supports-aria-props.md
+   */
+  "jsx-a11y/role-supports-aria-props"?: TtscLintRuleSetting;
+
+  /**
+   * Restrict the `scope` attribute to `<th>` cells. On any other tag (`<div
+   * scope="col">`, `<td scope="row">`) the attribute is ignored by browsers and
+   * confuses table-aware assistive tech.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/scope.md
+   */
+  "jsx-a11y/scope"?: TtscLintRuleSetting;
+
+  /**
+   * Reject `tabIndex` values greater than zero. Positive indices jump the
+   * keyboard focus order out of document order and almost always desynchronize
+   * from later DOM changes; `0` and `-1` remain allowed.
+   *
+   * @reference https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/tabindex-no-positive.md
+   */
+  "jsx-a11y/tabindex-no-positive"?: TtscLintRuleSetting;
+}