From 03b41b5c26818bbc9021c73d4462d90064dda34a Mon Sep 17 00:00:00 2001
From: Bryan Mishkin <698306+bmish@users.noreply.github.com>
Date: Wed, 26 Oct 2022 20:06:32 -0500
Subject: [PATCH] docs: automate docs with eslint-doc-generator

---
 .eslintrc                                     |  14 --
 README.md                                     | 149 +++++++-----------
 docs/rules/accessible-emoji.md                |   6 +-
 docs/rules/alt-text.md                        |  26 ++-
 docs/rules/anchor-ambiguous-text.md           |  10 +-
 docs/rules/anchor-has-content.md              |   8 +-
 docs/rules/anchor-is-valid.md                 |   8 +-
 .../aria-activedescendant-has-tabindex.md     |   6 +-
 docs/rules/aria-props.md                      |   6 +-
 docs/rules/aria-proptypes.md                  |   6 +-
 docs/rules/aria-role.md                       |   8 +-
 docs/rules/aria-unsupported-elements.md       |   6 +-
 docs/rules/autocomplete-valid.md              |  12 +-
 docs/rules/click-events-have-key-events.md    |   6 +-
 docs/rules/control-has-associated-label.md    |   8 +-
 docs/rules/heading-has-content.md             |   8 +-
 docs/rules/html-has-lang.md                   |   6 +-
 docs/rules/iframe-has-title.md                |   6 +-
 docs/rules/img-redundant-alt.md               |   8 +-
 docs/rules/interactive-supports-focus.md      |  16 +-
 docs/rules/label-has-associated-control.md    |   8 +-
 docs/rules/label-has-for.md                   |  10 +-
 docs/rules/lang.md                            |   4 +-
 docs/rules/media-has-caption.md               |   8 +-
 docs/rules/mouse-events-have-key-events.md    |   6 +-
 docs/rules/no-access-key.md                   |   6 +-
 docs/rules/no-autofocus.md                    |   8 +-
 docs/rules/no-distracting-elements.md         |   8 +-
 ...eractive-element-to-noninteractive-role.md |  10 +-
 .../no-noninteractive-element-interactions.md |  14 +-
 ...interactive-element-to-interactive-role.md |  11 +-
 docs/rules/no-noninteractive-tabindex.md      |  14 +-
 docs/rules/no-onchange.md                     |   6 +-
 docs/rules/no-redundant-roles.md              |  12 +-
 docs/rules/no-static-element-interactions.md  |  13 +-
 docs/rules/prefer-tag-over-role.md            |   4 +-
 docs/rules/role-has-required-aria-props.md    |   6 +-
 docs/rules/role-supports-aria-props.md        |   6 +-
 docs/rules/scope.md                           |   6 +-
 docs/rules/tabindex-no-positive.md            |   6 +-
 markdown.config.js                            |  59 -------
 package.json                                  |   7 +-
 scripts/boilerplate/rule.js                   |   2 +-
 ...eractive-element-to-noninteractive-role.js |   1 -
 .../no-noninteractive-element-interactions.js |   1 -
 ...interactive-element-to-interactive-role.js |   1 -
 src/rules/no-noninteractive-tabindex.js       |   1 -
 src/rules/no-static-element-interactions.js   |   1 -
 src/rules/scope.js                            |   1 -
 49 files changed, 322 insertions(+), 241 deletions(-)
 delete mode 100644 markdown.config.js

diff --git a/.eslintrc b/.eslintrc
index a0623fd57..a94e7cb6a 100644
--- a/.eslintrc
+++ b/.eslintrc
@@ -28,20 +28,6 @@
         "eslint-plugin/require-meta-type": "off",
       },
     },
-    {
-      "files": ["markdown.config.js"],
-      "parserOptions": {
-        "sourceType": "script",
-      },
-      "rules": {
-        "no-console": 0,
-        "import/no-extraneous-dependencies":  [
-           "error",
-           { "devDependencies": true },
-        ],
-        "strict": ["error", "global"],
-      },
-    },
     {
       "files": ["__tests__/src/rules/*.js"],
       "extends": ["plugin:eslint-plugin/tests-recommended"],
diff --git a/README.md b/README.md
index 43411bbf4..d74fc210e 100644
--- a/README.md
+++ b/README.md
@@ -88,6 +88,7 @@ Add `plugin:jsx-a11y/recommended` or `plugin:jsx-a11y/strict` in `extends`:
   "extends": ["plugin:jsx-a11y/recommended"]
 }
 ```
+
 > As you are extending our configuration, you can omit `"plugins": ["jsx-a11y"]` from your `.eslintrc` configuration file.
 
 To enable your custom components to be checked as DOM elements, you can set global settings in your
@@ -110,95 +111,59 @@ configuration file by mapping each custom component name to a DOM element type.
 
 ## Supported Rules
 
-<!-- AUTO-GENERATED-CONTENT:START (LIST) -->
-
-- [alt-text](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/alt-text.md): Enforce all elements that require alternative text have meaningful information to relay back to end user.
-- [anchor-ambiguous-text](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/anchor-ambiguous-text.md): Enforce `<a>` text to not exactly match "click here", "here", "link", or "a link".
-- [anchor-has-content](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/anchor-has-content.md): Enforce all anchors to contain accessible content.
-- [anchor-is-valid](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/anchor-is-valid.md): Enforce all anchors are valid, navigable elements.
-- [aria-activedescendant-has-tabindex](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-activedescendant-has-tabindex.md): Enforce elements with aria-activedescendant are tabbable.
-- [aria-props](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-props.md): Enforce all `aria-*` props are valid.
-- [aria-proptypes](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-proptypes.md): Enforce ARIA state and property values are valid.
-- [aria-role](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-role.md): Enforce that elements with ARIA roles must use a valid, non-abstract ARIA role.
-- [aria-unsupported-elements](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-unsupported-elements.md): Enforce that elements that do not support ARIA roles, states, and properties do not have those attributes.
-- [autocomplete-valid](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/autocomplete-valid.md): Enforce that autocomplete attributes are used correctly.
-- [click-events-have-key-events](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/click-events-have-key-events.md): Enforce a clickable non-interactive element has at least one keyboard event listener.
-- [control-has-associated-label](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/control-has-associated-label.md): Enforce that a control (an interactive element) has a text label.
-- [heading-has-content](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/heading-has-content.md): Enforce heading (`h1`, `h2`, etc) elements contain accessible content.
-- [html-has-lang](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/html-has-lang.md): Enforce `<html>` element has `lang` prop.
-- [iframe-has-title](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/iframe-has-title.md): Enforce iframe elements have a title attribute.
-- [img-redundant-alt](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/img-redundant-alt.md): Enforce `<img>` alt prop does not contain the word "image", "picture", or "photo".
-- [interactive-supports-focus](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/interactive-supports-focus.md): Enforce that elements with interactive handlers like `onClick` must be focusable.
-- [label-has-associated-control](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/label-has-associated-control.md): Enforce that a `label` tag has a text label and an associated control.
-
-- [lang](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/lang.md): Enforce lang attribute has a valid value.
-- [media-has-caption](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/media-has-caption.md): Enforces that `<audio>` and `<video>` elements must have a `<track>` for captions.
-- [mouse-events-have-key-events](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/mouse-events-have-key-events.md): Enforce that `onMouseOver`/`onMouseOut` are accompanied by `onFocus`/`onBlur` for keyboard-only users.
-- [no-access-key](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-access-key.md): Enforce that the `accessKey` prop is not used on any element to avoid complications with keyboard commands used by a screenreader.
-- [no-autofocus](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-autofocus.md): Enforce autoFocus prop is not used.
-- [no-distracting-elements](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-distracting-elements.md): Enforce distracting elements are not used.
-- [no-interactive-element-to-noninteractive-role](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-interactive-element-to-noninteractive-role.md): Interactive elements should not be assigned non-interactive roles.
-- [no-noninteractive-element-interactions](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-noninteractive-element-interactions.md): Non-interactive elements should not be assigned mouse or keyboard event listeners.
-- [no-noninteractive-element-to-interactive-role](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-noninteractive-element-to-interactive-role.md): Non-interactive elements should not be assigned interactive roles.
-- [no-noninteractive-tabindex](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-noninteractive-tabindex.md): `tabIndex` should only be declared on interactive elements.
-- [no-onchange](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-onchange.md): Enforce usage of `onBlur` over `onChange` on select menus for accessibility.
-- [no-redundant-roles](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-redundant-roles.md): Enforce explicit role property is not the same as implicit/default role property on element.
-- [no-static-element-interactions](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-static-element-interactions.md): Enforce that non-interactive, visible elements (such as `<div>`) that have click handlers use the role attribute.
-
-- [role-has-required-aria-props](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/role-has-required-aria-props.md): Enforce that elements with ARIA roles must have all required attributes for that role.
-- [role-supports-aria-props](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/role-supports-aria-props.md): Enforce that elements with explicit or implicit roles defined contain only `aria-*` properties supported by that `role`.
-- [scope](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/scope.md): Enforce `scope` prop is only used on `<th>` elements.
-- [tabindex-no-positive](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/tabindex-no-positive.md): Enforce `tabIndex` value is not greater than zero.
-<!-- AUTO-GENERATED-CONTENT:END -->
-
-### Rule strictness in different modes
-
-<!-- AUTO-GENERATED-CONTENT:START (TABLE) -->
-| Rule | Recommended | Strict |
-| :--- | :--- | :--- |
-| [accessible-emoji](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/accessible-emoji.md) | off | off |
-| [alt-text](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/alt-text.md) | error | error |
-| [anchor-ambiguous-text](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/anchor-ambiguous-text.md) | off | off |
-| [anchor-has-content](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/anchor-has-content.md) | error | error |
-| [anchor-is-valid](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/anchor-is-valid.md) | error | error |
-| [aria-activedescendant-has-tabindex](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-activedescendant-has-tabindex.md) | error | error |
-| [aria-props](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-props.md) | error | error |
-| [aria-proptypes](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-proptypes.md) | error | error |
-| [aria-role](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-role.md) | error | error |
-| [aria-unsupported-elements](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/aria-unsupported-elements.md) | error | error |
-| [autocomplete-valid](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/autocomplete-valid.md) | error | error |
-| [click-events-have-key-events](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/click-events-have-key-events.md) | error | error |
-| [control-has-associated-label](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/control-has-associated-label.md) | off | off |
-| [heading-has-content](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/heading-has-content.md) | error | error |
-| [html-has-lang](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/html-has-lang.md) | error | error |
-| [iframe-has-title](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/iframe-has-title.md) | error | error |
-| [img-redundant-alt](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/img-redundant-alt.md) | error | error |
-| [interactive-supports-focus](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/interactive-supports-focus.md) | error | error |
-| [label-has-associated-control](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/label-has-associated-control.md) | error | error |
-| [label-has-for](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/label-has-for.md) | off | off |
-| [lang](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/lang.md) | off | off |
-| [media-has-caption](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/media-has-caption.md) | error | error |
-| [mouse-events-have-key-events](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/mouse-events-have-key-events.md) | error | error |
-| [no-access-key](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-access-key.md) | error | error |
-| [no-autofocus](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-autofocus.md) | error | error |
-| [no-distracting-elements](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-distracting-elements.md) | error | error |
-| [no-interactive-element-to-noninteractive-role](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-interactive-element-to-noninteractive-role.md) | error, with options | error |
-| [no-noninteractive-element-interactions](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-noninteractive-element-interactions.md) | error, with options | error |
-| [no-noninteractive-element-to-interactive-role](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-noninteractive-element-to-interactive-role.md) | error, with options | error |
-| [no-noninteractive-tabindex](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-noninteractive-tabindex.md) | error, with options | error |
-| [no-onchange](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-onchange.md) | off | off |
-| [no-redundant-roles](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-redundant-roles.md) | error | error |
-| [no-static-element-interactions](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-static-element-interactions.md) | error, with options | error |
-| [prefer-tag-over-role](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/prefer-tag-over-role.md) | off | off |
-| [role-has-required-aria-props](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/role-has-required-aria-props.md) | error | error |
-| [role-supports-aria-props](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/role-supports-aria-props.md) | error | error |
-| [scope](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/scope.md) | error, with options | error |
-| [tabindex-no-positive](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/tabindex-no-positive.md) | error | error |
-<!-- AUTO-GENERATED-CONTENT:END -->
+<!-- begin auto-generated rules list -->
+
+💼 Configurations enabled in.\
+☑️ Enabled in the `recommended` configuration.\
+🔒 Enabled in the `strict` configuration.\
+❌ Deprecated.
+
+| Name                                                                                                         | Description                                                                                                                        | 💼    | ❌  |
+| :----------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------- | :---- | :-- |
+| [accessible-emoji](docs/rules/accessible-emoji.md)                                                           |                                                                                                                                    |       | ❌  |
+| [alt-text](docs/rules/alt-text.md)                                                                           | Enforce all elements that require alternative text have meaningful information to relay back to end user.                          | ☑️ 🔒 |     |
+| [anchor-ambiguous-text](docs/rules/anchor-ambiguous-text.md)                                                 | Enforce `<a>` text to not exactly match "click here", "here", "link", or "a link".                                                 |       |     |
+| [anchor-has-content](docs/rules/anchor-has-content.md)                                                       | Enforce all anchors to contain accessible content.                                                                                 | ☑️ 🔒 |     |
+| [anchor-is-valid](docs/rules/anchor-is-valid.md)                                                             | Enforce all anchors are valid, navigable elements.                                                                                 | ☑️ 🔒 |     |
+| [aria-activedescendant-has-tabindex](docs/rules/aria-activedescendant-has-tabindex.md)                       | Enforce elements with aria-activedescendant are tabbable.                                                                          | ☑️ 🔒 |     |
+| [aria-props](docs/rules/aria-props.md)                                                                       | Enforce all `aria-*` props are valid.                                                                                              | ☑️ 🔒 |     |
+| [aria-proptypes](docs/rules/aria-proptypes.md)                                                               | Enforce ARIA state and property values are valid.                                                                                  | ☑️ 🔒 |     |
+| [aria-role](docs/rules/aria-role.md)                                                                         | Enforce that elements with ARIA roles must use a valid, non-abstract ARIA role.                                                    | ☑️ 🔒 |     |
+| [aria-unsupported-elements](docs/rules/aria-unsupported-elements.md)                                         | Enforce that elements that do not support ARIA roles, states, and properties do not have those attributes.                         | ☑️ 🔒 |     |
+| [autocomplete-valid](docs/rules/autocomplete-valid.md)                                                       | Enforce that autocomplete attributes are used correctly.                                                                           | ☑️ 🔒 |     |
+| [click-events-have-key-events](docs/rules/click-events-have-key-events.md)                                   | Enforce a clickable non-interactive element has at least one keyboard event listener.                                              | ☑️ 🔒 |     |
+| [control-has-associated-label](docs/rules/control-has-associated-label.md)                                   | Enforce that a control (an interactive element) has a text label.                                                                  |       |     |
+| [heading-has-content](docs/rules/heading-has-content.md)                                                     | Enforce heading (`h1`, `h2`, etc) elements contain accessible content.                                                             | ☑️ 🔒 |     |
+| [html-has-lang](docs/rules/html-has-lang.md)                                                                 | Enforce `<html>` element has `lang` prop.                                                                                          | ☑️ 🔒 |     |
+| [iframe-has-title](docs/rules/iframe-has-title.md)                                                           | Enforce iframe elements have a title attribute.                                                                                    | ☑️ 🔒 |     |
+| [img-redundant-alt](docs/rules/img-redundant-alt.md)                                                         | Enforce `<img>` alt prop does not contain the word "image", "picture", or "photo".                                                 | ☑️ 🔒 |     |
+| [interactive-supports-focus](docs/rules/interactive-supports-focus.md)                                       | Enforce that elements with interactive handlers like `onClick` must be focusable.                                                  | ☑️ 🔒 |     |
+| [label-has-associated-control](docs/rules/label-has-associated-control.md)                                   | Enforce that a `label` tag has a text label and an associated control.                                                             | ☑️ 🔒 |     |
+| [label-has-for](docs/rules/label-has-for.md)                                                                 |                                                                                                                                    |       | ❌  |
+| [lang](docs/rules/lang.md)                                                                                   | Enforce lang attribute has a valid value.                                                                                          |       |     |
+| [media-has-caption](docs/rules/media-has-caption.md)                                                         | Enforces that `<audio>` and `<video>` elements must have a `<track>` for captions.                                                 | ☑️ 🔒 |     |
+| [mouse-events-have-key-events](docs/rules/mouse-events-have-key-events.md)                                   | Enforce that `onMouseOver`/`onMouseOut` are accompanied by `onFocus`/`onBlur` for keyboard-only users.                             | ☑️ 🔒 |     |
+| [no-access-key](docs/rules/no-access-key.md)                                                                 | Enforce that the `accessKey` prop is not used on any element to avoid complications with keyboard commands used by a screenreader. | ☑️ 🔒 |     |
+| [no-autofocus](docs/rules/no-autofocus.md)                                                                   | Enforce autoFocus prop is not used.                                                                                                | ☑️ 🔒 |     |
+| [no-distracting-elements](docs/rules/no-distracting-elements.md)                                             | Enforce distracting elements are not used.                                                                                         | ☑️ 🔒 |     |
+| [no-interactive-element-to-noninteractive-role](docs/rules/no-interactive-element-to-noninteractive-role.md) | Interactive elements should not be assigned non-interactive roles.                                                                 | ☑️ 🔒 |     |
+| [no-noninteractive-element-interactions](docs/rules/no-noninteractive-element-interactions.md)               | Non-interactive elements should not be assigned mouse or keyboard event listeners.                                                 | ☑️ 🔒 |     |
+| [no-noninteractive-element-to-interactive-role](docs/rules/no-noninteractive-element-to-interactive-role.md) | Non-interactive elements should not be assigned interactive roles.                                                                 | ☑️ 🔒 |     |
+| [no-noninteractive-tabindex](docs/rules/no-noninteractive-tabindex.md)                                       | `tabIndex` should only be declared on interactive elements.                                                                        | ☑️ 🔒 |     |
+| [no-onchange](docs/rules/no-onchange.md)                                                                     | Enforce usage of `onBlur` over `onChange` on select menus for accessibility.                                                       |       | ❌  |
+| [no-redundant-roles](docs/rules/no-redundant-roles.md)                                                       | Enforce explicit role property is not the same as implicit/default role property on element.                                       | ☑️ 🔒 |     |
+| [no-static-element-interactions](docs/rules/no-static-element-interactions.md)                               | Enforce that non-interactive, visible elements (such as `<div>`) that have click handlers use the role attribute.                  | ☑️ 🔒 |     |
+| [prefer-tag-over-role](docs/rules/prefer-tag-over-role.md)                                                   |                                                                                                                                    |       |     |
+| [role-has-required-aria-props](docs/rules/role-has-required-aria-props.md)                                   | Enforce that elements with ARIA roles must have all required attributes for that role.                                             | ☑️ 🔒 |     |
+| [role-supports-aria-props](docs/rules/role-supports-aria-props.md)                                           | Enforce that elements with explicit or implicit roles defined contain only `aria-*` properties supported by that `role`.           | ☑️ 🔒 |     |
+| [scope](docs/rules/scope.md)                                                                                 | Enforce `scope` prop is only used on `<th>` elements.                                                                              | ☑️ 🔒 |     |
+| [tabindex-no-positive](docs/rules/tabindex-no-positive.md)                                                   | Enforce `tabIndex` value is not greater than zero.                                                                                 | ☑️ 🔒 |     |
+
+<!-- end auto-generated rules list -->
 
 The following rules have extra options when in _recommended_ mode:
 
-#### no-interactive-element-to-noninteractive-role
+### no-interactive-element-to-noninteractive-role
 
 ```js
 'jsx-a11y/no-interactive-element-to-noninteractive-role': [
@@ -209,7 +174,7 @@ The following rules have extra options when in _recommended_ mode:
 ]
 ```
 
-#### no-noninteractive-element-interactions
+### no-noninteractive-element-interactions
 
 ```js
 'jsx-a11y/no-noninteractive-element-interactions': [
@@ -227,7 +192,7 @@ The following rules have extra options when in _recommended_ mode:
 ]
 ```
 
-#### no-noninteractive-element-to-interactive-role
+### no-noninteractive-element-to-interactive-role
 
 ```js
 'jsx-a11y/no-noninteractive-element-to-interactive-role': [
@@ -258,7 +223,7 @@ The following rules have extra options when in _recommended_ mode:
 ]
 ```
 
-#### no-noninteractive-tabindex
+### no-noninteractive-tabindex
 
 ```js
 'jsx-a11y/no-noninteractive-tabindex': [
@@ -270,7 +235,7 @@ The following rules have extra options when in _recommended_ mode:
 ]
 ```
 
-#### no-static-element-interactions
+### no-static-element-interactions
 
 ```js
 'jsx-a11y/no-noninteractive-element-interactions': [
@@ -293,8 +258,8 @@ The following rules have extra options when in _recommended_ mode:
 If you are developing new rules for this project, you can use the `create-rule`
 script to scaffold the new files.
 
-```
-$ ./scripts/create-rule.js my-new-rule
+```sh
+./scripts/create-rule.js my-new-rule
 ```
 
 ## Some background on WAI-ARIA, the AX Tree and Browsers
diff --git a/docs/rules/accessible-emoji.md b/docs/rules/accessible-emoji.md
index 51b13ded5..73db0fe51 100644
--- a/docs/rules/accessible-emoji.md
+++ b/docs/rules/accessible-emoji.md
@@ -1,4 +1,8 @@
-# [Deprecated] accessible-emoji
+# jsx-a11y/accessible-emoji
+
+❌ This rule is deprecated.
+
+<!-- end auto-generated rule header -->
 
 Emoji have become a common way of communicating content to the end user. To a person using a screenreader, however, they may not be aware that this content is there at all. By wrapping the emoji in a `<span>`, giving it the `role="img"`, and providing a useful description in `aria-label`, the screenreader will treat the emoji as an image in the accessibility tree with an accessible name for the end user.
 
diff --git a/docs/rules/alt-text.md b/docs/rules/alt-text.md
index 8e3b4e17f..40c90c779 100644
--- a/docs/rules/alt-text.md
+++ b/docs/rules/alt-text.md
@@ -1,9 +1,15 @@
-# alt-text
+# jsx-a11y/alt-text
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce that all elements that require alternative text have meaningful information to relay back to the end user. This is a critical component of accessibility for screen reader users in order for them to understand the content's purpose on the page. By default, this rule checks for alternative text on the following elements: `<img>`, `<area>`, `<input type="image">`, and `<object>`.
 
 ## How to resolve
+
 ### `<img>`
+
 An `<img>` must have the `alt` prop set with meaningful text or as an empty string to indicate that it is an image for decoration.
 
 For images that are being used as icons for a button or control, the `alt` prop should be set to an empty string (`alt=""`).
@@ -12,20 +18,25 @@ For images that are being used as icons for a button or control, the `alt` prop
 <button>
   <img src="icon.png" alt="" />
   Save
+
 </button>
 ```
+
 The content of an `alt` attribute is used to calculate the accessible label of an element, whereas the text content is used to produce a label for the element. For this reason, adding a label to an icon can produce a confusing or duplicated label on a control that already has appropriate text content.
 
 ### `<object>`
+
 Add alternative text to all embedded `<object>` elements using either inner text, setting the `title` prop, or using the `aria-label` or `aria-labelledby` props.
 
 ### `<input type="image">`
+
 All `<input type="image">` elements must have a non-empty `alt` prop set with a meaningful description of the image or have the `aria-label` or `aria-labelledby` props set.
 
 ### `<area>`
+
 All clickable `<area>` elements within an image map have an `alt`, `aria-label` or `aria-labelledby` prop that describes the purpose of the link.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
@@ -66,12 +77,14 @@ return (
   <header>
     <Image alt="Logo" src="logo.jpg" />
   </header>
+
 );
 ```
 
 Note that passing props as spread attribute without explicitly the necessary accessibility props defined will cause this rule to fail. Explicitly pass down the set of props needed for rule to pass. Use `Image` component above as a reference for destructuring and applying the prop. **It is a good thing to explicitly pass props that you expect to be passed for self-documentation.** For example:
 
 #### Bad
+
 ```jsx
 function Foo(props) {
   return <img {...props} />
@@ -79,6 +92,7 @@ function Foo(props) {
 ```
 
 #### Good
+
 ```jsx
 function Foo({ alt, ...props}) {
     return <img alt={alt} {...props} />
@@ -89,6 +103,7 @@ function Foo({ alt, ...props}) {
 function Foo(props) {
     const {
         alt,
+
         ...otherProps
     } = props;
 
@@ -97,6 +112,7 @@ function Foo(props) {
 ```
 
 ### Succeed
+
 ```jsx
 <img src="foo" alt="Foo eating a sandwich." />
 <img src="foo" alt={"Foo eating a sandwich."} />
@@ -111,6 +127,7 @@ function Foo(props) {
 
 <area aria-label="foo" />
 <area aria-labelledby="id1" />
+
 <area alt="This is descriptive!" />
 
 <input type="image" alt="This is descriptive!" />
@@ -120,6 +137,7 @@ function Foo(props) {
 ```
 
 ### Fail
+
 ```jsx
 <img src="foo" />
 <img {...props} />
@@ -127,19 +145,23 @@ function Foo(props) {
 <img {...props} alt={undefined} /> // Has no value
 <img {...props} alt={`${undefined}`} /> // Has no value
 <img src="foo" role="presentation" /> // Avoid ARIA if it can be achieved without
+
 <img src="foo" role="none" /> // Avoid ARIA if it can be achieved without
 
 <object {...props} />
 
+
 <area {...props} />
 
 <input type="image" {...props} />
 ```
 
 ## Accessibility guidelines
+
 - [WCAG 1.1.1](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html)
 
 ### Resources
+
 - [axe-core, object-alt](https://dequeuniversity.com/rules/axe/3.2/object-alt)
 - [axe-core, image-alt](https://dequeuniversity.com/rules/axe/3.2/image-alt)
 - [axe-core, input-image-alt](https://dequeuniversity.com/rules/axe/3.2/input-image-alt)
diff --git a/docs/rules/anchor-ambiguous-text.md b/docs/rules/anchor-ambiguous-text.md
index 0a14fb45c..92c8a9971 100644
--- a/docs/rules/anchor-ambiguous-text.md
+++ b/docs/rules/anchor-ambiguous-text.md
@@ -1,8 +1,12 @@
-# anchor-ambiguous-text
+# jsx-a11y/anchor-ambiguous-text
+
+☑️ This rule is _disabled_ in the `recommended` config.
+
+<!-- end auto-generated rule header -->
 
 Enforces `<a>` values are not exact matches for the phrases "click here", "here", "link", "a link", or "learn more". Screenreaders announce tags as links/interactive, but rely on values for context. Ambiguous anchor descriptions do not provide sufficient context for users.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument with the parameter `words`.
 
@@ -33,6 +37,7 @@ Note that this rule still disallows ambiguous `aria-label` or `alt` values.
 Note that this rule is case-insensitive, trims whitespace, and ignores certain punctuation (`[,.?¿!‽¡;:]`). It only looks for **exact matches**.
 
 ### Succeed
+
 ```jsx
 <a>read this tutorial</a> // passes since it is not one of the disallowed words
 <a>${here}</a> // this is valid since 'here' is a variable name
@@ -40,6 +45,7 @@ Note that this rule is case-insensitive, trims whitespace, and ignores certain p
 ```
 
 ### Fail
+
 ```jsx
 <a>here</a>
 <a>HERE</a>
diff --git a/docs/rules/anchor-has-content.md b/docs/rules/anchor-has-content.md
index 73f29a7ed..f49937e57 100644
--- a/docs/rules/anchor-has-content.md
+++ b/docs/rules/anchor-has-content.md
@@ -1,8 +1,12 @@
-# anchor-has-content
+# jsx-a11y/anchor-has-content
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce that anchors have content and that the content is accessible to screen readers. Accessible means that it is not hidden using the `aria-hidden` prop. Refer to the references to learn about why this is important.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/anchor-is-valid.md b/docs/rules/anchor-is-valid.md
index 31d4b5583..77b1965c9 100644
--- a/docs/rules/anchor-is-valid.md
+++ b/docs/rules/anchor-is-valid.md
@@ -1,4 +1,8 @@
-# anchor-is-valid
+# jsx-a11y/anchor-is-valid
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 The HTML `<a>` element, with a valid `href` attribute, is formally defined as representing a **hyperlink**. That is, a link between one HTML document and another, or between one location inside an HTML document and another location inside the same document.
 
@@ -159,7 +163,7 @@ This button element can now also be used inline in text.
 
 Once again we stress that this is an inferior implementation and some users will encounter difficulty to use your website, however, it will allow a larger group of people to interact with your website than the alternative of ignoring the rule's warning.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/aria-activedescendant-has-tabindex.md b/docs/rules/aria-activedescendant-has-tabindex.md
index d3499335d..c6a37213a 100644
--- a/docs/rules/aria-activedescendant-has-tabindex.md
+++ b/docs/rules/aria-activedescendant-has-tabindex.md
@@ -1,4 +1,8 @@
-# aria-activedescendant-has-tabindex
+# jsx-a11y/aria-activedescendant-has-tabindex
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 `aria-activedescendant` is used to manage focus within a [composite widget](https://www.w3.org/TR/wai-aria/#composite).
 The element with the attribute `aria-activedescendant` retains the active document
diff --git a/docs/rules/aria-props.md b/docs/rules/aria-props.md
index cde013322..2ed051a80 100644
--- a/docs/rules/aria-props.md
+++ b/docs/rules/aria-props.md
@@ -1,4 +1,8 @@
-# aria-props
+# jsx-a11y/aria-props
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Elements cannot use an invalid ARIA attribute. This will fail if it finds an `aria-*` property that is not listed in [WAI-ARIA States and Properties spec](https://www.w3.org/WAI/PF/aria-1.1/states_and_properties).
 
diff --git a/docs/rules/aria-proptypes.md b/docs/rules/aria-proptypes.md
index ca98a5a54..c4e596a9a 100644
--- a/docs/rules/aria-proptypes.md
+++ b/docs/rules/aria-proptypes.md
@@ -1,4 +1,8 @@
-# aria-proptypes
+# jsx-a11y/aria-proptypes
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 ARIA state and property values must be valid.
 
diff --git a/docs/rules/aria-role.md b/docs/rules/aria-role.md
index 0167752b0..b9646dc27 100644
--- a/docs/rules/aria-role.md
+++ b/docs/rules/aria-role.md
@@ -1,8 +1,12 @@
-# aria-role
+# jsx-a11y/aria-role
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Elements with ARIA roles must use a valid, non-abstract ARIA role. A reference to role definitions can be found at [WAI-ARIA](https://www.w3.org/TR/wai-aria/#role_definitions) site.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/aria-unsupported-elements.md b/docs/rules/aria-unsupported-elements.md
index 8f13ad852..a759f0088 100644
--- a/docs/rules/aria-unsupported-elements.md
+++ b/docs/rules/aria-unsupported-elements.md
@@ -1,4 +1,8 @@
-# aria-unsupported-elements
+# jsx-a11y/aria-unsupported-elements
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 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 `role` and/or `aria-*` props.
 
diff --git a/docs/rules/autocomplete-valid.md b/docs/rules/autocomplete-valid.md
index 19c38d9d1..9e29af759 100644
--- a/docs/rules/autocomplete-valid.md
+++ b/docs/rules/autocomplete-valid.md
@@ -1,8 +1,12 @@
-# autocomplete-valid
+# jsx-a11y/autocomplete-valid
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Ensure the autocomplete attribute is correct and suitable for the form field it is used with.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
@@ -22,7 +26,7 @@ This rule takes one optional object argument of type object:
 <input type="text" autocomplete="name" />
 
 <!-- Good: MyInput is not listed in inputComponents -->
-<MyInput autocomplete="incorrect" /> 
+<MyInput autocomplete="incorrect" />
 ```
 
 ### Fail
@@ -34,7 +38,7 @@ This rule takes one optional object argument of type object:
 <input type="email" autocomplete="url" />
 
 <!-- Bad: MyInput is listed in inputComponents -->
-<MyInput autocomplete="incorrect" /> 
+<MyInput autocomplete="incorrect" />
 ```
 
 ## Accessibility guidelines
diff --git a/docs/rules/click-events-have-key-events.md b/docs/rules/click-events-have-key-events.md
index d60e6ae03..613a099dd 100644
--- a/docs/rules/click-events-have-key-events.md
+++ b/docs/rules/click-events-have-key-events.md
@@ -1,4 +1,8 @@
-# click-events-have-key-events
+# jsx-a11y/click-events-have-key-events
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce `onClick` is accompanied by at least one of the following: `onKeyUp`, `onKeyDown`, `onKeyPress`. Coding for the keyboard is important for users with physical disabilities who cannot use a mouse, AT compatibility, and screenreader users. This does not apply for interactive or hidden elements.
 
diff --git a/docs/rules/control-has-associated-label.md b/docs/rules/control-has-associated-label.md
index 344407ecf..b0f016d6b 100644
--- a/docs/rules/control-has-associated-label.md
+++ b/docs/rules/control-has-associated-label.md
@@ -1,4 +1,8 @@
-# control-has-associated-label
+# jsx-a11y/control-has-associated-label
+
+💼 This rule is _disabled_ in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce that a control (an interactive element) has a text label.
 
@@ -50,7 +54,7 @@ You can configure the rule to be aware of your custom components. Refer to the R
 <CustomInput label="Surname" type="text" value={value} />
 ```
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/heading-has-content.md b/docs/rules/heading-has-content.md
index a575ac2d1..9599e13a8 100644
--- a/docs/rules/heading-has-content.md
+++ b/docs/rules/heading-has-content.md
@@ -1,8 +1,12 @@
-# heading-has-content
+# jsx-a11y/heading-has-content
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce that heading elements (`h1`, `h2`, etc.) have content and that the content is accessible to screen readers. Accessible means that it is not hidden using the `aria-hidden` prop. Refer to the references to learn about why this is important.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/html-has-lang.md b/docs/rules/html-has-lang.md
index 9ba9763ec..dee57eb32 100644
--- a/docs/rules/html-has-lang.md
+++ b/docs/rules/html-has-lang.md
@@ -1,4 +1,8 @@
-# html-has-lang
+# jsx-a11y/html-has-lang
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 <html> elements must have the lang prop. This rule is largely superseded by the [`lang` rule](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/lang.md).
 
diff --git a/docs/rules/iframe-has-title.md b/docs/rules/iframe-has-title.md
index fac618527..0015944dd 100644
--- a/docs/rules/iframe-has-title.md
+++ b/docs/rules/iframe-has-title.md
@@ -1,4 +1,8 @@
-# iframe-has-title
+# jsx-a11y/iframe-has-title
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 `<iframe>` elements must have a unique title property to indicate its content to the user.
 
diff --git a/docs/rules/img-redundant-alt.md b/docs/rules/img-redundant-alt.md
index d06aaa79f..1b8ebcba1 100644
--- a/docs/rules/img-redundant-alt.md
+++ b/docs/rules/img-redundant-alt.md
@@ -1,8 +1,12 @@
-# img-redundant-alt
+# jsx-a11y/img-redundant-alt
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce img alt attribute does not contain the word image, picture, or photo. Screenreaders already announce `img` elements as an image. There is no need to use words such as *image*, *photo*, and/or *picture*.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/interactive-supports-focus.md b/docs/rules/interactive-supports-focus.md
index d7cd0e671..2e896b0e3 100644
--- a/docs/rules/interactive-supports-focus.md
+++ b/docs/rules/interactive-supports-focus.md
@@ -1,4 +1,8 @@
-# interactive-supports-focus
+# jsx-a11y/interactive-supports-focus
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Elements with an interactive role and interaction handlers (mouse or key press) must be focusable.
 
@@ -24,7 +28,7 @@ Generally buttons, links and form elements should be reachable via tab key press
 
 ### Case: I got the error "Elements with the '${role}' interactive role must be focusable". How can I fix this?
 
-This element is part of a group of buttons, links, menu items, etc. Or this element is part of a composite widget. Composite widgets prescribe standard [keyboard interaction patterns](https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_generalnav). Within a group of similar elements -- like a button bar -- or within a composite widget, elements that can be focused are given a tabindex of -1. This makes the element *focusable* but not *tabbable*. Generally one item in a group should have a tabindex of zero so that a user can tab to the component. Once an element in the component has focus, your key management behaviors will control traversal within the component's pieces. As the UI author, you will need to implement the key handling behaviors such as listening for traversal key (up/down/left/right) presses and moving the page focus between the focusable elements in your widget.
+This element is part of a group of buttons, links, menu items, etc. Or this element is part of a composite widget. Composite widgets prescribe standard [keyboard interaction patterns](https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_generalnav). Within a group of similar elements -- like a button bar -- or within a composite widget, elements that can be focused are given a tabindex of -1. This makes the element _focusable_ but not _tabbable_. Generally one item in a group should have a tabindex of zero so that a user can tab to the component. Once an element in the component has focus, your key management behaviors will control traversal within the component's pieces. As the UI author, you will need to implement the key handling behaviors such as listening for traversal key (up/down/left/right) presses and moving the page focus between the focusable elements in your widget.
 
 ```jsx
 <div role="menu">
@@ -50,7 +54,7 @@ If your element is catching bubbled click or key events from descendant elements
 
 Marking an element with the role `presentation` indicates to assistive technology that this element should be ignored; it exists to support the web application and is not meant for humans to interact with directly.
 
-## Rule details
+## Rule options
 
 This rule takes an options object with the key `tabbable`. The value is an array of interactive ARIA roles that should be considered tabbable, not just focusable. Any interactive role not included in this list will be flagged as needing to be focusable (tabindex of -1).
 
@@ -117,6 +121,7 @@ The list of possible values includes:
 ```
 
 ### Succeed
+
 ```jsx
 <!-- Good: div with onClick attribute is hidden from screen reader -->
 <div aria-hidden onClick={() => void 0} />
@@ -131,6 +136,7 @@ The list of possible values includes:
 ```
 
 ### Fail
+
 ```jsx
 <!-- Bad: span with onClick attribute has no tabindex -->
 <span onclick="submitForm();" role="button">Submit</span>
@@ -139,10 +145,12 @@ The list of possible values includes:
 ```
 
 ## Accessibility guidelines
+
 - [WCAG 2.1.1](https://www.w3.org/WAI/WCAG21/Understanding/keyboard)
 
 ### Resources
-- [Chrome Audit Rules, AX_FOCUS_02](https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#ax_focus_02) 
+
+- [Chrome Audit Rules, AX_FOCUS_02](https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#ax_focus_02)
 - [Mozilla Developer Network - ARIA Techniques](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_button_role#Keyboard_and_focus)
 - [Fundamental Keyboard Navigation Conventions](https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_generalnav)
 - [WAI-ARIA Authoring Practices Guide - Design Patterns and Widgets](https://www.w3.org/TR/wai-aria-practices-1.1/#aria_ex)
diff --git a/docs/rules/label-has-associated-control.md b/docs/rules/label-has-associated-control.md
index 7037f07e1..5a3efa48d 100644
--- a/docs/rules/label-has-associated-control.md
+++ b/docs/rules/label-has-associated-control.md
@@ -1,4 +1,8 @@
-# label-has-associated-control
+# jsx-a11y/label-has-associated-control
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce that a label tag has a text label and an associated control.
 
@@ -81,7 +85,7 @@ IDs shouldn't be generated in the browser, so that server and client rendering a
 
 To restate, **every ID needs to be deterministic**, on the server and the client, and guaranteed to be unique on the page. EG: For each input, a required ID prop can be passed down from as far up the tree as possible to guarantee uniqueness.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/label-has-for.md b/docs/rules/label-has-for.md
index 77a3beeda..34d7d91d1 100644
--- a/docs/rules/label-has-for.md
+++ b/docs/rules/label-has-for.md
@@ -1,4 +1,10 @@
-# [Deprecated] label-has-for
+# jsx-a11y/label-has-for
+
+❌ This rule is deprecated.
+
+💼 This rule is _disabled_ in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 *This rule was deprecated in v6.1.0. It will no longer be maintained. Please use [`label-has-associated-control`](label-has-associated-control.md) instead.*
 
@@ -11,7 +17,7 @@ There are two supported ways to associate a label with a control:
 
 To fully cover 100% of assistive devices, you're encouraged to validate for both nesting and id.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/lang.md b/docs/rules/lang.md
index 66ac44f53..ace4b2356 100644
--- a/docs/rules/lang.md
+++ b/docs/rules/lang.md
@@ -1,4 +1,6 @@
-# lang
+# jsx-a11y/lang
+
+<!-- end auto-generated rule header -->
 
 The `lang` prop on the `<html>` element must be a valid IETF's BCP 47 language tag.
 
diff --git a/docs/rules/media-has-caption.md b/docs/rules/media-has-caption.md
index 3c7b020ad..be29a7e5c 100644
--- a/docs/rules/media-has-caption.md
+++ b/docs/rules/media-has-caption.md
@@ -1,10 +1,14 @@
-# media-has-caption
+# jsx-a11y/media-has-caption
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Providing captions for media is essential for deaf users to follow along. Captions should be a transcription or translation of the dialogue, sound effects, relevant musical cues, and other relevant audio information. Not only is this important for accessibility, but can also be useful for all users in the case that the media is unavailable (similar to `alt` text on an image when an image is unable to load).
 
 The captions should contain all important and relevant information to understand the corresponding media. This may mean that the captions are not a 1:1 mapping of the dialogue in the media content. However, captions are *not* necessary for video components with the `muted` attribute.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/mouse-events-have-key-events.md b/docs/rules/mouse-events-have-key-events.md
index 53bd10c79..c3a1ff233 100644
--- a/docs/rules/mouse-events-have-key-events.md
+++ b/docs/rules/mouse-events-have-key-events.md
@@ -1,4 +1,8 @@
-# mouse-events-have-key-events
+# jsx-a11y/mouse-events-have-key-events
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce onmouseover/onmouseout are accompanied by onfocus/onblur. Coding for the keyboard is important for users with physical disabilities who cannot use a mouse, AT compatibility, and screenreader users.
 
diff --git a/docs/rules/no-access-key.md b/docs/rules/no-access-key.md
index 452ee9d09..962f71357 100644
--- a/docs/rules/no-access-key.md
+++ b/docs/rules/no-access-key.md
@@ -1,4 +1,8 @@
-# no-access-key
+# jsx-a11y/no-access-key
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce no accessKey prop 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 screenreaders and keyboard-only users create accessibility complications so to avoid complications, access keys should not be used.
 
diff --git a/docs/rules/no-autofocus.md b/docs/rules/no-autofocus.md
index 8b01ad3d5..d91469b3f 100644
--- a/docs/rules/no-autofocus.md
+++ b/docs/rules/no-autofocus.md
@@ -1,8 +1,12 @@
-# no-autofocus
+# jsx-a11y/no-autofocus
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce that autoFocus prop is not used on elements. Autofocusing elements can cause usability issues for sighted and non-sighted users, alike.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/no-distracting-elements.md b/docs/rules/no-distracting-elements.md
index 148ee9811..9e986bd6b 100644
--- a/docs/rules/no-distracting-elements.md
+++ b/docs/rules/no-distracting-elements.md
@@ -1,8 +1,12 @@
-# no-distracting-elements
+# jsx-a11y/no-distracting-elements
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforces that no distracting elements are used. Elements that can be visually distracting can cause accessibility issues with visually impaired users. Such elements are most likely deprecated, and should be avoided. By default, the following elements are visually distracting: `<marquee>` and `<blink>`.
 
-## Rule details
+## Rule options
 
 This rule takes one optional object argument of type object:
 
diff --git a/docs/rules/no-interactive-element-to-noninteractive-role.md b/docs/rules/no-interactive-element-to-noninteractive-role.md
index 5eda0a6de..c3cadae67 100644
--- a/docs/rules/no-interactive-element-to-noninteractive-role.md
+++ b/docs/rules/no-interactive-element-to-noninteractive-role.md
@@ -1,4 +1,8 @@
-# no-interactive-element-to-noninteractive-role
+# jsx-a11y/no-interactive-element-to-noninteractive-role
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Interactive HTML elements indicate _controls_ in the user interface. Interactive elements include `<a href>`, `<button>`, `<input>`, `<select>`, `<textarea>`.
 
@@ -32,7 +36,7 @@ Put the content inside your interactive element.
 </div>
 ```
 
-## Rule details
+## Rule options
 
 The recommended options for this rule allow the `tr` element to be given a role of `presentation` (or its semantic equivalent `none`). Under normal circumstances, an element with an interactive role should not be semantically neutralized with `presentation` (or `none`).
 
@@ -56,9 +60,11 @@ Under the recommended options, the following code is valid. It would be invalid
 ```
 
 ## Accessibility guidelines
+
 - [WCAG 4.1.2](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value)
 
 ### Resources
+
 - [ARIA Spec, States and Properties](https://www.w3.org/TR/wai-aria/#states_and_properties)
 - [Chrome Audit Rules, AX_ARIA_04](https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#ax_aria_04)
 - [WAI-ARIA roles](https://www.w3.org/TR/wai-aria-1.1/#usage_intro)
diff --git a/docs/rules/no-noninteractive-element-interactions.md b/docs/rules/no-noninteractive-element-interactions.md
index 0b6424948..c14f298f8 100644
--- a/docs/rules/no-noninteractive-element-interactions.md
+++ b/docs/rules/no-noninteractive-element-interactions.md
@@ -1,10 +1,14 @@
-# no-noninteractive-element-interactions
+# jsx-a11y/no-noninteractive-element-interactions
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Non-interactive HTML elements and non-interactive ARIA roles indicate _content_ and _containers_ in the user interface. A non-interactive element does not support event handlers (mouse and key handlers). Non-interactive elements include `<main>`, `<area>`, `<h1>` (,`<h2>`, etc), `<p>`, `<img>`, `<li>`, `<ul>` and `<ol>`. Non-interactive [WAI-ARIA roles](https://www.w3.org/TR/wai-aria-1.1/#usage_intro) include `article`, `banner`, `complementary`, `img`, `listitem`, `main`, `region` and `tooltip`.
 
 ## How do I resolve this error?
 
-### Case: This element acts like a button, link, menuitem, etc.
+### Case: This element acts like a button, link, menuitem, etc
 
 Move the event handler function to an inner element that is either a semantically interactive element (`<button>`, `<a href>`) or that has an interactive role. This leaves the _content_ or _container_ semantic value of this element intact.
 
@@ -89,7 +93,7 @@ If your user interface has a table-like layout, but is filled with interactive c
 
 You can also put the interactive content inside the grid cell. This maintains the semantic distinction between the cell and the interaction content, although a grid cell can be interactive.
 
-## Rule details
+## Rule options
 
 You may configure which handler props should be taken into account when applying this rule. The recommended configuration includes the following 6 handlers.
 
@@ -112,6 +116,7 @@ You may configure which handler props should be taken into account when applying
 Adjust the list of handler prop names in the handlers array to increase or decrease the coverage surface of this rule in your codebase.
 
 ### Succeed
+
 ```jsx
 <div onClick={() => void 0} role="button" />
 <div onClick={() => void 0} role="presentation" />
@@ -122,15 +127,18 @@ Adjust the list of handler prop names in the handlers array to increase or decre
 ```
 
 ### Fail
+
 ```jsx
 <li onClick={() => void 0} />
 <div onClick={() => void 0} role="listitem" />
 ```
 
 ## Accessibility guidelines
+
 - [WCAG 4.1.2](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value)
 
 ### Resources
+
 - [WAI-ARIA roles](https://www.w3.org/TR/wai-aria-1.1/#usage_intro)
 - [WAI-ARIA Authoring Practices Guide - Design Patterns and Widgets](https://www.w3.org/TR/wai-aria-practices-1.1/#aria_ex)
 - [Fundamental Keyboard Navigation Conventions](https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_generalnav)
diff --git a/docs/rules/no-noninteractive-element-to-interactive-role.md b/docs/rules/no-noninteractive-element-to-interactive-role.md
index 60c6e37bd..c4d5fe81b 100644
--- a/docs/rules/no-noninteractive-element-to-interactive-role.md
+++ b/docs/rules/no-noninteractive-element-to-interactive-role.md
@@ -1,10 +1,13 @@
-# no-noninteractive-element-to-interactive-role
+# jsx-a11y/no-noninteractive-element-to-interactive-role
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Non-interactive HTML elements indicate _content_ and _containers_ in the user interface. Non-interactive elements include `<main>`, `<area>`, `<h1>` (,`<h2>`, etc), `<img>`, `<li>`, `<ul>` and `<ol>`.
 
 Interactive HTML elements indicate _controls_ in the user interface. Interactive elements include `<a href>`, `<button>`, `<input>`, `<select>`, `<textarea>`.
 
-
 [WAI-ARIA roles](https://www.w3.org/TR/wai-aria-1.1/#usage_intro) should not be used to convert a non-interactive element to an interactive element. Interactive ARIA roles include `button`, `link`, `checkbox`, `menuitem`, `menuitemcheckbox`, `menuitemradio`, `option`, `radio`, `searchbox`, `switch` and `textbox`.
 
 ## How do I resolve this error?
@@ -36,7 +39,7 @@ Or wrap the content inside your interactive element.
 </div>
 ```
 
-## Rule details
+## Rule options
 
 The recommended options for this rule allow several common interactive roles to be applied to a non-interactive element. The options are provided as an object keyed by HTML element name; the value is an array of interactive roles that are allowed on the specified element.
 
@@ -62,9 +65,11 @@ Under the recommended options, the following code is valid. It would be invalid
 ```
 
 ## Accessibility guidelines
+
 - [WCAG 4.1.2](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value)
 
 ### Resources
+
 - [WAI-ARIA roles](https://www.w3.org/TR/wai-aria-1.1/#usage_intro)
 - [WAI-ARIA Authoring Practices Guide - Design Patterns and Widgets](https://www.w3.org/TR/wai-aria-practices-1.1/#aria_ex)
 - [Fundamental Keyboard Navigation Conventions](https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_generalnav)
diff --git a/docs/rules/no-noninteractive-tabindex.md b/docs/rules/no-noninteractive-tabindex.md
index 54e5bc5a9..6c900621a 100644
--- a/docs/rules/no-noninteractive-tabindex.md
+++ b/docs/rules/no-noninteractive-tabindex.md
@@ -1,4 +1,8 @@
-# no-noninteractive-tabindex
+# jsx-a11y/no-noninteractive-tabindex
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Tab key navigation should be limited to elements on the page that can be interacted with. Thus it is not necessary to add a tabindex to items in an unordered list, for example, to make them navigable through assistive technology. These applications already afford page traversal mechanisms based on the HTML of the page. Generally, we should try to reduce the size of the page's tab ring rather than increasing it.
 
@@ -55,7 +59,7 @@ If you know that a particular element will be scrollable, you might want to add
 </pre>
 ```
 
-## Rule details
+## Rule options
 
 The recommended options for this rule allow `tabIndex` on elements with the noninteractive `tabpanel` role. Adding `tabIndex` to a tabpanel is a recommended practice in some instances.
 
@@ -69,7 +73,9 @@ The recommended options for this rule allow `tabIndex` on elements with the noni
   },
 ]
 ```
+
 The `allowExpressionValues` option determines whether the `role` attribute is allowed to be assigned using an expression. For example, the following would pass in recommended mode if `allowExpressionValues` is set to be `true`:
+
 ```jsx
 <div role={ROLE_BUTTON} onClick={() => {}} tabIndex="0" />;
 // In case of a conditional expression, there should be literals on both sides of ternary operator
@@ -77,6 +83,7 @@ The `allowExpressionValues` option determines whether the `role` attribute is al
 ```
 
 ### Succeed
+
 ```jsx
 <div />
 <MyButton tabIndex={0} />
@@ -91,6 +98,7 @@ The `allowExpressionValues` option determines whether the `role` attribute is al
 ```
 
 ### Fail
+
 ```jsx
 <div tabIndex="0" />
 <div role="article" tabIndex="0" />
@@ -99,7 +107,9 @@ The `allowExpressionValues` option determines whether the `role` attribute is al
 ```
 
 ## Accessibility guidelines
+
 - [WCAG 2.1.1](https://www.w3.org/WAI/WCAG21/Understanding/keyboard)
 
 ### Resources
+
 - [Fundamental Keyboard Navigation Conventions](https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_generalnav)
diff --git a/docs/rules/no-onchange.md b/docs/rules/no-onchange.md
index a93f302cf..bc318f717 100644
--- a/docs/rules/no-onchange.md
+++ b/docs/rules/no-onchange.md
@@ -1,4 +1,8 @@
-# [Deprecated] no-onchange
+# jsx-a11y/no-onchange
+
+❌ This rule is deprecated.
+
+<!-- end auto-generated rule header -->
 
 ⚠️ **Deprecated:** This rule is based on reports of behavior of [old browsers (eg. IE 10 and below)](https://www.quirksmode.org/dom/events/change.html#t05). In the meantime, this behavior has been corrected, both in newer versions of browsers as well as [in the DOM spec](https://bugzilla.mozilla.org/show_bug.cgi?id=969068#c2).
 
diff --git a/docs/rules/no-redundant-roles.md b/docs/rules/no-redundant-roles.md
index 83d1f14ad..0506b6066 100644
--- a/docs/rules/no-redundant-roles.md
+++ b/docs/rules/no-redundant-roles.md
@@ -1,8 +1,12 @@
-# no-redundant-roles
+# jsx-a11y/no-redundant-roles
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Some HTML elements have native semantics that are implemented by the browser. This includes default/implicit ARIA roles. Setting an ARIA role that matches its default/implicit role is redundant since it is already set by the browser.
 
-## Rule details
+## Rule options
 
 The default options for this rule allow an implicit role of `navigation` to be applied to a `nav` element as is [advised by w3](https://www.w3.org/WAI/GL/wiki/Using_HTML5_nav_element#Example:The_.3Cnav.3E_element). The options are provided as an object keyed by HTML element name; the value is an array of implicit ARIA roles that are allowed on the specified element.
 
@@ -18,6 +22,7 @@ The default options for this rule allow an implicit role of `navigation` to be a
 ```
 
 ### Succeed
+
 ```jsx
 <div />
 <button role="presentation" />
@@ -25,13 +30,16 @@ The default options for this rule allow an implicit role of `navigation` to be a
 ```
 
 ### Fail
+
 ```jsx
 <button role="button" />
 <img role="img" src="foo.jpg" />
 ```
 
 ## Accessibility guidelines
+
 General best practice (reference resources)
 
 ### Resources
+
 - [ARIA Spec, ARIA Adds Nothing to Default Semantics of Most HTML Elements](https://www.w3.org/TR/using-aria/#aria-does-nothing)
diff --git a/docs/rules/no-static-element-interactions.md b/docs/rules/no-static-element-interactions.md
index 64069e1f2..fcfa47553 100644
--- a/docs/rules/no-static-element-interactions.md
+++ b/docs/rules/no-static-element-interactions.md
@@ -1,4 +1,8 @@
-# no-static-element-interactions
+# jsx-a11y/no-static-element-interactions
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 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>`, `<big>`, `<blockquote>`, `<footer>`, `<picture>`, `<strike>` and `<time>` -- to name a few -- have no semantic layer mapping. They are as void of meaning as `<div>`.
 
@@ -8,7 +12,7 @@ In order to add interactivity such as a mouse or key event listener to a static
 
 ## How do I resolve this error?
 
-### Case: This element acts like a button, link, menuitem, etc.
+### Case: This element acts like a button, link, menuitem, etc
 
 Indicate the element's role with the `role` attribute:
 
@@ -53,7 +57,7 @@ If your element is catching bubbled click or key events from descendant elements
 
 Do not use the role `presentation` on the element: it removes the element's semantics, and may also remove its children's semantics, creating big issues with assistive technology.
 
-## Rule details
+## Rule options
 
 You may configure which handler props should be taken into account when applying this rule. The recommended configuration includes the following 6 handlers and the `allowExpressionValues` option.
 
@@ -77,6 +81,7 @@ You may configure which handler props should be taken into account when applying
 Adjust the list of handler prop names in the handlers array to increase or decrease the coverage surface of this rule in your codebase.
 
 The `allowExpressionValues` option determines whether the `role` attribute is allowed to be assigned using an expression. For example, the following would pass in recommended mode if `allowExpressionValues` is set to be `true`:
+
 ```jsx
 <div role={ROLE_BUTTON} onClick={() => {}} />;
 // In case of a conditional expression, there should be literals on both sides of ternary operator
@@ -98,9 +103,11 @@ The `allowExpressionValues` option determines whether the `role` attribute is al
 ```
 
 ## Accessibility guidelines
+
 - [WCAG 4.1.2](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value)
 
 ### Resources
+
 - [WAI-ARIA `role` attribute](https://www.w3.org/TR/wai-aria-1.1/#usage_intro)
 - [WAI-ARIA Authoring Practices Guide - Design Patterns and Widgets](https://www.w3.org/TR/wai-aria-practices-1.1/#aria_ex)
 - [Fundamental Keyboard Navigation Conventions](https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_generalnav)
diff --git a/docs/rules/prefer-tag-over-role.md b/docs/rules/prefer-tag-over-role.md
index 3c1309ed8..994436b45 100644
--- a/docs/rules/prefer-tag-over-role.md
+++ b/docs/rules/prefer-tag-over-role.md
@@ -1,4 +1,6 @@
-# prefer-tag-over-role
+# jsx-a11y/prefer-tag-over-role
+
+<!-- end auto-generated rule header -->
 
 Enforces using semantic DOM elements over the ARIA `role` property.
 
diff --git a/docs/rules/role-has-required-aria-props.md b/docs/rules/role-has-required-aria-props.md
index e06c90235..2d153f0b1 100644
--- a/docs/rules/role-has-required-aria-props.md
+++ b/docs/rules/role-has-required-aria-props.md
@@ -1,4 +1,8 @@
-# role-has-required-aria-props
+# jsx-a11y/role-has-required-aria-props
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Elements with ARIA roles must have all required attributes for that role.
 
diff --git a/docs/rules/role-supports-aria-props.md b/docs/rules/role-supports-aria-props.md
index 287d0ff98..53c08ec45 100644
--- a/docs/rules/role-supports-aria-props.md
+++ b/docs/rules/role-supports-aria-props.md
@@ -1,4 +1,8 @@
-# role-supports-aria-props
+# jsx-a11y/role-supports-aria-props
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Enforce that elements with explicit or implicit roles defined contain only `aria-*` properties supported by that `role`. Many ARIA attributes (states and properties) can only be used on elements with particular roles. Some elements have implicit roles, such as `<a href="#" />`, which will resolve to `role="link"`.
 
diff --git a/docs/rules/scope.md b/docs/rules/scope.md
index 0290aa0b9..89df1bb65 100644
--- a/docs/rules/scope.md
+++ b/docs/rules/scope.md
@@ -1,4 +1,8 @@
-# scope
+# jsx-a11y/scope
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 The `scope` prop should be used only on `<th>` elements.
 
diff --git a/docs/rules/tabindex-no-positive.md b/docs/rules/tabindex-no-positive.md
index e0762de2b..93c387c2d 100644
--- a/docs/rules/tabindex-no-positive.md
+++ b/docs/rules/tabindex-no-positive.md
@@ -1,4 +1,8 @@
-# tabindex-no-positive
+# jsx-a11y/tabindex-no-positive
+
+💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
+
+<!-- end auto-generated rule header -->
 
 Avoid positive `tabIndex` property values to synchronize the flow of the page with keyboard tab order.
 
diff --git a/markdown.config.js b/markdown.config.js
deleted file mode 100644
index 6f9d0e5a9..000000000
--- a/markdown.config.js
+++ /dev/null
@@ -1,59 +0,0 @@
-'use strict';
-
-require('@babel/register');
-
-const {
-  configs: {
-    recommended: { rules: recommended },
-    strict: { rules: strict },
-  },
-  rules,
-} = require('./src');
-
-const ruleTableRows = Object.keys(rules)
-  .sort()
-  .map((id) => {
-    const { meta } = rules[id];
-    const { url, errorOptions } = meta.docs;
-
-    const recSev = [].concat(recommended[`jsx-a11y/${id}`] || 'off')[0];
-    const strictSev = [].concat(strict[`jsx-a11y/${id}`] || 'off')[0];
-
-    return [
-      `[${id}](${url})`,
-      recSev === 'error' ? (errorOptions ? 'error, with options' : 'error') : recSev, // eslint-disable-line no-nested-ternary
-      strictSev,
-    ].join(' | ');
-  });
-
-const buildRulesTable = (rows) => {
-  const header = 'Rule | Recommended | Strict';
-  const separator = ':--- | :--- | :---';
-
-  return [header, separator].concat(rows)
-    .map((row) => `| ${row} |`)
-    .join('\n');
-};
-
-const ruleList = Object.keys(rules)
-  .sort()
-  .map((id) => {
-    const { meta } = rules[id];
-    const { description, url } = meta.docs;
-    return description ? [`- [${id}](${url}): ${description}`] : null;
-  });
-
-const buildRuleList = (listItems) => listItems.join('\n');
-
-const LIST = () => buildRuleList(ruleList);
-const TABLE = () => buildRulesTable(ruleTableRows);
-
-module.exports = {
-  transforms: {
-    TABLE,
-    LIST,
-  },
-  callback: () => {
-    console.log('The auto-generating of rules finished!');
-  },
-};
diff --git a/package.json b/package.json
index a457d0204..cefda78f2 100644
--- a/package.json
+++ b/package.json
@@ -30,8 +30,9 @@
     "posttest": "aud --production",
     "test:ci": "npm run jest -- --ci --runInBand",
     "jest": "jest --coverage __tests__/**/*",
-    "generate-list-of-rules": "md-magic --path '**/*.md' --ignore 'node_modules'",
-    "generate-list-of-rules:check": "npm run generate-list-of-rules && git diff --exit-code README.md"
+    "pregenerate-list-of-rules": "npm run build",
+    "generate-list-of-rules": "eslint-doc-generator --rule-doc-title-format prefix-name --rule-doc-section-options false --config-emoji recommended,☑️",
+    "generate-list-of-rules:check": "npm run generate-list-of-rules -- --check"
   },
   "devDependencies": {
     "@babel/cli": "^7.19.3",
@@ -46,6 +47,7 @@
     "babel-preset-airbnb": "^5.0.0",
     "eslint": "^3 || ^4 || ^5 || ^6 || ^7 || ^8",
     "eslint-config-airbnb-base": "^15.0.0",
+    "eslint-doc-generator": "^0.16.0",
     "eslint-plugin-eslint-plugin": "^4.3.0",
     "eslint-plugin-flowtype": "^5.8.0 || ^8.0.3",
     "eslint-plugin-import": "^2.26.0",
@@ -55,7 +57,6 @@
     "in-publish": "^2.0.1",
     "jest": "^24.9.0",
     "jscodeshift": "^0.7.1",
-    "markdown-magic": "^2.6.1",
     "minimist": "^1.2.7",
     "npmignore": "^0.3.0",
     "object.assign": "^4.1.4",
diff --git a/scripts/boilerplate/rule.js b/scripts/boilerplate/rule.js
index b45252c39..8e2cb60da 100644
--- a/scripts/boilerplate/rule.js
+++ b/scripts/boilerplate/rule.js
@@ -13,7 +13,7 @@ import { generateObjSchema } from '../util/schemas';
 
 const errorMessage = '';
 
-const schema = generateObjSchema();
+const schema = generateObjSchema(); // TODO: remove this and use "schema: []" if no options.
 
 export default {
   meta: {
diff --git a/src/rules/no-interactive-element-to-noninteractive-role.js b/src/rules/no-interactive-element-to-noninteractive-role.js
index e817fb573..cc70b7cfb 100644
--- a/src/rules/no-interactive-element-to-noninteractive-role.js
+++ b/src/rules/no-interactive-element-to-noninteractive-role.js
@@ -34,7 +34,6 @@ export default ({
     docs: {
       url: 'https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-interactive-element-to-noninteractive-role.md',
       description: 'Interactive elements should not be assigned non-interactive roles.',
-      errorOptions: true,
     },
     schema: [{
       type: 'object',
diff --git a/src/rules/no-noninteractive-element-interactions.js b/src/rules/no-noninteractive-element-interactions.js
index 052a4a131..9fe8f8e63 100644
--- a/src/rules/no-noninteractive-element-interactions.js
+++ b/src/rules/no-noninteractive-element-interactions.js
@@ -47,7 +47,6 @@ export default ({
     docs: {
       url: 'https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-noninteractive-element-interactions.md',
       description: 'Non-interactive elements should not be assigned mouse or keyboard event listeners.',
-      errorOptions: true,
     },
     schema: [schema],
   },
diff --git a/src/rules/no-noninteractive-element-to-interactive-role.js b/src/rules/no-noninteractive-element-to-interactive-role.js
index 8c4b8aebc..601039aa1 100644
--- a/src/rules/no-noninteractive-element-to-interactive-role.js
+++ b/src/rules/no-noninteractive-element-to-interactive-role.js
@@ -32,7 +32,6 @@ export default ({
     docs: {
       url: 'https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-noninteractive-element-to-interactive-role.md',
       description: 'Non-interactive elements should not be assigned interactive roles.',
-      errorOptions: true,
     },
     schema: [{
       type: 'object',
diff --git a/src/rules/no-noninteractive-tabindex.js b/src/rules/no-noninteractive-tabindex.js
index 78f605ea0..796b44cd8 100644
--- a/src/rules/no-noninteractive-tabindex.js
+++ b/src/rules/no-noninteractive-tabindex.js
@@ -41,7 +41,6 @@ export default ({
     docs: {
       url: 'https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-noninteractive-tabindex.md',
       description: '`tabIndex` should only be declared on interactive elements.',
-      errorOptions: true,
     },
     schema: [schema],
   },
diff --git a/src/rules/no-static-element-interactions.js b/src/rules/no-static-element-interactions.js
index fc0a8a590..e48c4bd0f 100644
--- a/src/rules/no-static-element-interactions.js
+++ b/src/rules/no-static-element-interactions.js
@@ -46,7 +46,6 @@ export default ({
     docs: {
       url: 'https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/no-static-element-interactions.md',
       description: 'Enforce that non-interactive, visible elements (such as `<div>`) that have click handlers use the role attribute.',
-      errorOptions: true,
     },
     schema: [schema],
   },
diff --git a/src/rules/scope.js b/src/rules/scope.js
index a647ce792..ffef2fe0d 100644
--- a/src/rules/scope.js
+++ b/src/rules/scope.js
@@ -21,7 +21,6 @@ export default {
     docs: {
       url: 'https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/tree/HEAD/docs/rules/scope.md',
       description: 'Enforce `scope` prop is only used on `<th>` elements.',
-      errorOptions: true,
     },
     schema: [schema],
   },