Add mint a11y CLI command

installation.mdx

@@ -1,6 +1,6 @@
 ---
 title: "CLI installation"
 description: "Install the CLI to preview and develop your docs locally"
 ---
 
 <img
@@ -14,10 +14,10 @@
   alt="Decorative graphic representing the CLI."
 />
 
 ## Installing the CLI
 
 <Info>
   **Prerequisite**: Please install [Node.js](https://nodejs.org/en) before proceeding.
 </Info>
 
 <Steps>
@@ -36,7 +36,7 @@
 
   </Step>
   <Step title="Preview locally.">
     Navigate to your docs directory (where your `docs.json` file is located) and execute the following command:
 
     ```bash
     mint dev
@@ -46,7 +46,7 @@
   </Step>
 </Steps>
 
 Alternatively, if you do not want to install the CLI globally, you can run a one-time script:
 
 ```bash
 npx mint dev
@@ -54,13 +54,13 @@
 
 ## Updates
 
 If your local preview is out of sync with what you see on the web in the production version, update your local CLI:
 
 ```bash
 mint update
 ```
 
 If this `mint update` command is not available on your local version, re-install the CLI with the latest version:
 
  <CodeGroup>
     ```bash npm
@@ -74,13 +74,13 @@
 
 ## Custom ports
 
 By default, the CLI uses port 3000. You can customize the port using the `--port` flag. To run the CLI on port 3333, for instance, use this command:
 
 ```bash
 mint dev --port 3333
 ```
 
 If you attempt to run on a port that is already in use, it will use the next available port:
 
 ```mdx
 Port 3000 is already in use. Trying 3001 instead.
@@ -98,37 +98,43 @@
 
 ## Additional commands
 
-While `mint dev` is the most commonly used command, there are other commands you can use to manage your documentation.
+### Find broken links
 
-### Finding broken links
-
-The CLI can assist with validating reference links made in your documentation. To identify any broken links, use the following command:
+Identify any broken internal links with the following command:
 
 ```bash
 mint broken-links
 ```
 
-### Checking OpenAPI spec
+### Find accessibility issues
+
+Test the color contrast ratios and search for missing alt text on images and videos in your documentation with the following command:
+
+```bash
+mint a11y
+```
+
+### Check OpenAPI spec
 
-You can use the CLI to check your OpenAPI file for errors using the following command:
+Check your OpenAPI file for errors with the following command:
 
 ```bash
-mint openapi-check <openapiFilenameOrUrl>
+mint openapi-check <OpenAPI filename or URL>
 ```
 
-You can pass in a filename (for example, `./openapi.yaml`) or a URL (for example, `https://petstore3.swagger.io/api/v3/openapi.json`).
+Pass a filename (for example, `./openapi.yaml`) or a URL (for example, `https://petstore3.swagger.io/api/v3/openapi.json`).
 
-### Renaming files
+### Rename files
 
-You can rename and update all references to files using the following command:
+Rename and update all references to files with the following command:
 
 ```bash
-mint rename <oldFilename> <newFilename>
+mint rename <path/to/old-filename> <path/to/new-filename>
 ```
 
-### Migrating MDX endpoint pages
+### Migrate MDX endpoint pages
 
-You can migrate MDX endpoint pages to autogenerated pages from your OpenAPI specification using the following command:
+Migrate MDX endpoint pages to autogenerated pages from your OpenAPI specification with the following command:
 
 ```bash
 mint migrate-mdx
@@ -138,11 +144,11 @@
 
 ## Formatting
 
 While developing locally, we recommend using extensions in your IDE to recognize and format `MDX` files.
 
 If you use Cursor, Windsurf, or VS Code, we recommend the [MDX VS Code extension](https://marketplace.visualstudio.com/items?itemName=unifiedjs.vscode-mdx) for syntax highlighting, and [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) for code formatting.
 
 If you use JetBrains, we recommend the [MDX IntelliJ IDEA plugin](https://plugins.jetbrains.com/plugin/14944-mdx) for syntax highlighting, and setting up [Prettier](https://prettier.io/docs/webstorm) for code formatting.
 
 ## Troubleshooting
 
@@ -155,7 +161,7 @@
     3. Reinstall the mint CLI: `npm install -g mint`
   </Accordion>
   <Accordion title="Issue: Encountering an unknown error">
     **Solution**: Go to the root of your device and delete the `~/.mintlify` folder. Afterwards, run `mint dev` again.
   </Accordion>
   <Accordion title="Error: permission denied">
     This is due to not having the required permissions to globally install node packages.
@@ -163,12 +169,12 @@
     **Solution**: Try running `sudo npm i -g mint`. You will be prompted for your password, which is the one you use to unlock your computer.
   </Accordion>
   <Accordion title="The local preview doesn't look the same as my docs do on the web">
     This is likely due to an outdated version of the CLI.
 
    **Solution:** Run `mint update` to get the latest changes.
   </Accordion>
   <Accordion title="mintlify vs. mint package">
     If you have any problems with the CLI package, you should first run `npm ls -g`. This command shows what packages are globally installed on your machine.
 
     If you don't use npm or don't see it in the -g list, try `which mint` to locate the installation.