Improve alt text on images (docker#16484)

Author: aevesdocker

atomist/get-started.md

@@ -81,7 +81,7 @@ with the appropriate condition on the IAM role statement.
    > this stack requires a capability. This stack creates a role that will grant
    > Atomist read-only access to ECR resources.
    >
-   > ![confirm](./images/ecr/capability.png)
+   > ![Confirm read-only access to ECR resources](./images/ecr/capability.png)
 
    <div style="text-align: center">
      <table>
@@ -185,7 +185,7 @@ with the appropriate condition on the IAM role statement.
    Atomist tests the connection with your ECR registry. A green check mark
    displays beside the integration if a successful connection is made.
 
-   ![integration list showing a successful ECR integration](./images/ecr/connection-successful.png){:
+   ![Integration list showing a successful ECR integration](./images/ecr/connection-successful.png){:
    width="700px"}
 
 </div>

atomist/integrate/github.md

@@ -24,7 +24,7 @@ repositories for your Docker images.
    the
    [Atomist GitHub App](https://github.com/apps/atomist "Atomist GitHub App"){: target="blank" rel="noopener" class=""}.
 
-   ![install the GitHub app](images/gh-install.png){: width="700px" }
+   ![Install the GitHub app view](images/gh-install.png){: width="700px" }
 
 4. Install the app.
 
@@ -39,7 +39,7 @@ repositories for your Docker images.
 5. In the repository selection menu, select what repositories you want Atomist
    to start watching.
 
-   ![activate repositories](images/activate-repos.png){: width="500px" }
+   ![Activate repositories view](images/activate-repos.png){: width="500px" }
 
    If you are just looking to evaluate Atomist, start by selecting a few
    repositories during evaluation. Once you are comfortable using Atomist, you

atomist/try-atomist.md

@@ -77,20 +77,20 @@ rel="noopener" class=""}.
    target="blank" rel="noopener" class=""}, where you should see the image in
    the list.
 
-   ![indexed image in the image overview list](./images/images-overview.png){:
+   ![Indexed image in the image overview list](./images/images-overview.png){:
    width="700px"}
 
 6. Select the image name. This gets you to the list of image tags.
 
-   ![list of image tags](./images/tags-list.png){: width="700px"}
+   ![List of image tags](./images/tags-list.png){: width="700px"}
 
    Since this is your first time indexing this image, the list only has one tag
    for now. When you integrate Atomist with your container registry, images and
    tags show up in this list automatically.
 
 7. Select the tag name. This shows you the insights for this tag.
 
-   ![vulnerability breakdown view](./images/vulnerabilities-overview.png){:
+   ![Vulnerability breakdown view](./images/vulnerabilities-overview.png){:
    width="700px"}
 
    In this view, you can see how many vulnerabilities this image has, their

desktop/containerd/index.md

@@ -145,7 +145,7 @@ CONTAINER ID   IMAGE     COMMAND                  CREATED         STATUS
 
 You can also check from the browser that Nginx is running:
 
-![containerd_feature_nginx](../images/containerd_feature_nginx.png){:width="750px"}
+![Containerd setting in Docker Desktop](../images/containerd_feature_nginx.png){:width="750px"}
 
 ## Building multi-platform images
 

desktop/dev-environments/index.md

@@ -13,7 +13,7 @@ It uses tools built into code editors that allows Docker to access code mounted
 
 You can use Dev Environments through the intuitive GUI in Docker Dashboard or straight from you terminal with the new [`docker dev` CLI plugin](dev-cli.md).
 
-![Dev environment intro](../images/dev-env.PNG){:width="700px"}
+![Dev environments tab in Docker Desktop](../images/dev-env.PNG){:width="700px"}
 
 ## How does it work?
 

desktop/extensions-sdk/architecture/index.md

@@ -13,7 +13,7 @@ Extensions can be composed of 3 (optional) components:
 - a backend: one or many containerised services running in the Docker Desktop VM
 - executables: shell scripts or binaries that Docker Desktop copies on the host when installing the extension
 
-![Overview](./images/overview.svg)
+![Overview of the three components of an extension](./images/overview.svg)
 
 An extension doesn't necessarily need to have all these components, but at least one of them depending on the extension features. 
 To configure and run those components, Docker Desktop uses a `metadata.json` file. See the

desktop/extensions-sdk/build/frontend-extension-tutorial.md

@@ -209,7 +209,7 @@ provide you with type definitions for the extension APIs and auto-completion in
 npm install @docker/extension-api-client-types --save-dev
 ```
 
-![types auto complete](images/types-autocomplete.png)
+![Auto completion in an IDE](images/types-autocomplete.png)
 
 For example, you can use the `docker.cli.exec` function to get the list of all the containers via the `docker ps --all`
 command and display the result in a table.

desktop/extensions-sdk/build/minimal-frontend-extension.md

@@ -100,7 +100,7 @@ To preview the extension in Docker Desktop, close and open Docker Dashboard once
 
 The left-hand menu displays a new tab with the name of your extension.
 
-![minimal-frontend-extension](images/ui-minimal-extension.png)
+![Minimal frontend extension](images/ui-minimal-extension.png)
 
 ## What's next?
 

desktop/extensions-sdk/design/design-guidelines.md

@@ -18,39 +18,39 @@ Use the [Docker Material UI Theme](https://www.npmjs.com/package/@docker/docker-
 
 - Ensure the extension has both a light and dark theme. Using the components and styles as per the Docker style guide ensures that your extension meets the [level AA accessibility standard.](https://www.w3.org/WAI/WCAG2AA-Conformance){:target="_blank" rel="noopener" class="_"}.
 
-![light and dark mode](images/light_dark_mode.png)
+![Light and dark mode](images/light_dark_mode.png)
 
 - Ensure that your extension icon is visible both in light and dark mode.
 
-![icon colors](images/icon_colors.png)
+![Icon colors in light and dark mode](images/icon_colors.png)
 
 - Ensure that the navigational behavior is consistent with the rest of Docker Desktop. Add a header to set the context for the extension.
 
-![header](images/header.png)
+![Header that sets the context](images/header.png)
 
 - Avoid embedding terminal windows. The advantage we have with Docker Desktop over the CLI is that we have the opportunity to provide rich information to users. Make use of this interface as much as possible. 
 
-![terminal window dont](images/terminal_window_dont.png){:height="=50%" width="50%"}
+![Terminal window used incorrectly](images/terminal_window_dont.png){:height="=50%" width="50%"}
 
-![terminal window do](images/terminal_window_do.png)
+![Terminal window used correctly](images/terminal_window_do.png)
 
 ## Build Features Natively
 
 - In order not to disrupt the flow of users, avoid scenarios where the user has to navigate outside Docker Desktop, to the CLI or a webpage for example, in order to carry out certain functionalities. Instead, build features that are native to Docker Desktop.
 
-![switch context dont](images/switch_context_dont.png){:height="=50%" width="50%"}
+![Incorrect way to switch context](images/switch_context_dont.png){:height="=50%" width="50%"}
 
-![switch context do](images/switch_context_do.png)
+![Correct way to switch context](images/switch_context_do.png)
 
 ## Break Down Complicated User Flows
 
 - If a flow is too complicated or the concept is abstract, break down the flow into multiple steps with one simple call-to-action in each step. This helps when onboarding novice users to your extension
 
-![complicated flow](images/complicated_flows.png)
+![A complicated flow](images/complicated_flows.png)
 
 - Where there are multiple call-to-actions, ensure you use the primary (filled button style) and secondary buttons (outline button style) to convey the importance of each action.
 
-![call to action](images/cta.png)
+![Call to action](images/cta.png)
 
 ## Onboarding New Users
 

desktop/extensions-sdk/extensions/labels.md

@@ -8,7 +8,7 @@ Extensions use image labels to provide additional information like title, descri
 
 These information allow to display an overview of the extension to users so they can choose to install it:
 
-![List preview](images/marketplace-details.png)
+![Extension preview](images/marketplace-details.png)
 
 You can define [Image labels](../../../engine/reference/builder.md#label) in the extension's `Dockerfile`.
 

desktop/extensions-sdk/guides/oauth2-flow.md

@@ -20,7 +20,7 @@ The Authorization Code grant type is used by confidential and public clients to
 
 After the user returns to the client via the redirect URL, the application gets the authorization code from the URL and uses it to request an access token.
 
-![oauth2-flow](images/oauth2-flow.png){: style=width:80% }
+![Flow for OAuth 2.0](images/oauth2-flow.png){: style=width:80% }
 
 The image above shows that:
 - The Docker Extension asks the user to authorize access to their data.

desktop/extensions/index.md

@@ -16,7 +16,7 @@ You can seamlessly connect your favorite development tools to your application d
 
 Anyone can use Docker Extensions and there is no limit to the number of extensions you can install. 
 
-![extenstions](../images/extensions-marketplace.PNG){:width="750px"}
+![Extensions Marketplace](../images/extensions-marketplace.PNG){:width="750px"}
 
 ## What extensions are available?
 

desktop/hardened-desktop/settings-management/configure.md

@@ -141,4 +141,4 @@ Docker doesn't automatically mandate that developers re-launch and sign in once
 
 In Docker Desktop, developers see the relevant settings grayed out and the message **Locked by your administrator**.
 
-![Proxy settings grayed out](/assets/images/grayed-setting.png){:width="350px"}
+![Proxy settings grayed out with Settings Management](/assets/images/grayed-setting.png){:width="350px"}

desktop/install/windows-install.md

@@ -176,7 +176,7 @@ Docker Desktop does not start automatically after installation. To start Docker
 
 1. Search for Docker, and select **Docker Desktop** in the search results.
 
-   ![search for Docker app](images/docker-app-search.png){:width="300px"}
+   ![Search for Docker app](images/docker-app-search.png){:width="300px"}
 
 2. The Docker menu (![whale menu](images/whale-x.svg){: .inline}) displays the Docker Subscription Service Agreement window.
 

desktop/troubleshoot/overview.md

@@ -30,7 +30,7 @@ To navigate to **Troubleshoot** either:
 - Select the Docker menu ![whale menu](../images/whale-x.svg){: .inline} and then **Troubleshoot**
 - Select the **Troubleshoot** icon from the Docker Dashboard
 
-![Troubleshoot Docker Desktop](../images/troubleshoot.png){:width="600px"}
+![Troubleshoot menu in Docker Desktop](../images/troubleshoot.png){:width="600px"}
 
 The Troubleshoot page contains the following options:
 

desktop/use-desktop/index.md

@@ -8,7 +8,7 @@ redirect_from:
 
 When you open Docker Desktop, the Docker Dashboard displays.
 
-![dashboard](../images/dashboard.PNG){:width="750px"}
+![Docker Dashboard on Containers view](../images/dashboard.PNG){:width="750px"}
 
 The **Containers** view provides a runtime view of all your containers and applications. It allows you to interact with containers and applications, and manage the lifecycle of your applications directly from your machine. This view also provides an intuitive interface to perform common actions to inspect, interact with, and manage your Docker objects including containers and Docker Compose-based applications. For more information, see [Explore running containers and applications](container.md).
 

docker-hub/2fa/disable-2fa.md

@@ -18,11 +18,11 @@ To disable two-factor authentication, log in to your Docker Hub account. Click
 on your username and select **Account Settings**. Go to Security and click on
 **Disable 2FA**.
 
-![Disable 2fa button](../images/2fa-disable-2fa.png)
+![Disable 2FA button](../images/2fa-disable-2fa.png)
 
 You will be prompted to input your Docker ID password. Enter your password and
 click **Disable 2FA**.
 
-![Enter your password](../images/2fa-enter-pw-disable-2fa.png){:width="250px"}
+![Enter your password view](../images/2fa-enter-pw-disable-2fa.png){:width="250px"}
 
 You have successfully disabled two-factor authentication.

docker-hub/2fa/index.md

@@ -52,7 +52,7 @@ entering a text code into your authenticator app. Once you have linked your
 authenticator app, it will give you a six-digit code to enter in text field.
 Click **Next**.
 
-![Enter special code](../images/2fa-enter-code.png)
+![Enter special code view](../images/2fa-enter-code.png)
 
 You have successfully enabled two-factor authentication. The next time you log
 in to your Docker Hub account, you will be asked for a security code.

docker-hub/2fa/new-recovery-code.md

@@ -20,7 +20,7 @@ on your username and select **Account Settings**. Go to **Security** and **Click
 
 Enter your password.
 
-![Enter your password](../images/2fa-pw-new-code.png){:width="250px"}
+![Enter your password view](../images/2fa-pw-new-code.png){:width="250px"}
 
 Your new recovery code will be displayed. Remember to save your recovery code
 and store it somewhere safe.

docker-hub/access-tokens.md

@@ -50,7 +50,7 @@ To create your access token:
    will be used, or set a purpose for the token. You can view the following access
    permissions from the drop-down:
 
-      ![PAT Menu](images/hub-create-token.png){:width="700px"}
+      ![New access token menu](images/hub-create-token.png){:width="700px"}
 
    The access permissions are scopes that set restrictions in your
    repositories. For example, for Read & Write permissions, an automation
@@ -60,7 +60,7 @@ To create your access token:
 5. Copy the token that appears on the screen and save it. You will not be able
    to retrieve the token once you close this prompt.
 
-      ![Copy Token](images/hub-copy-token.png){:width="700px"}
+      ![Copy access token view](images/hub-copy-token.png){:width="700px"}
 
 ## Use an access token
 
@@ -85,12 +85,12 @@ You can rename, activate, deactivate, or delete a token as needed.
    This page shows an overview of all your tokens. You can also view the number
    of tokens that are activated and deactivated in the toolbar.
 
-   ![Delete or Edit](images/hub-delete-edit-token.png){:width="700px"}
+   ![Delete or edit and access token](images/hub-delete-edit-token.png){:width="700px"}
 
 2. Select a token and click **Delete** or **Edit**, or use the menu on
    the far right of a token row to bring up the edit screen. You can also
    select multiple tokens to delete at once.
 
-      ![Modify Token](images/hub-edit-token.png){:width="700px"}
+      ![Modify an access token](images/hub-edit-token.png){:width="700px"}
 
 3. After modifying the token, click the **Save** button to save your changes.

docker-hub/audit-log.md

@@ -41,7 +41,7 @@ By default, all activities that occur at organization and repository levels are
 
 Click the **All Activities** drop-down list to view activities that are specific to an organization or a repository. After choosing **Organization** or **Repository**, you can further refine the results using the **All Actions** drop-down list. If you select the **Activities** tab from the **Repository** view, you can only filter repository-level activities.
 
-![Refine org activities](images/org-all-actions.png){:width="600px"}
+![Refine organization activities](images/org-all-actions.png){:width="600px"}
 
 
 ## Audit logs event definitions

docker-hub/builds/index.md

@@ -179,7 +179,7 @@ bar chart of the build queue times and durations. Both views display the
 pending, in progress, successful, and failed builds for any tag of the
 repository.
 
-![Active Builds](images/index-active.png)
+![Active builds](images/index-active.png)
 
 From either location, you can select a build job to view its build report. The
 build report shows information about the build job. This includes the source
@@ -191,7 +191,7 @@ repository and branch (or tag), the build logs, the build duration, creation tim
 > refresh the Builds page. With the in-progress build logs, you can debug your
 > builds before they're finished.
 
-![Build Report](/docker-hub/images/index-report.png)
+![Build report](/docker-hub/images/index-report.png)
 
 ## Cancel or retry a build
 
@@ -200,7 +200,7 @@ report link on the General tab and on the Builds tab. You can also click the
 **Cancel** on the build report page, or from the Timeline tab's logs
 display for the build.
 
-![list of builds showing the cancel icon](images/build-cancelicon.png)
+![List of builds showing the cancel icon](images/build-cancelicon.png)
 
 ## Failing builds
 

docker-hub/orgs.md

@@ -166,7 +166,7 @@ To give a team access to a repository
 4. Choose a permission from the **Permissions** drop-down list and click
    **Add**.
 
-    ![Team Repo Permissions](images/team-repo-permission.png){:width="700px"}
+    ![Team repository permissions view](images/team-repo-permission.png){:width="700px"}
 
 ### View a team's permissions for all repositories
 

docker-hub/quickstart.md

@@ -93,13 +93,13 @@ To create a repository:
 3. Name it **<your-username>/my-private-repo**.
 4. Set the visibility to **Private**.
 
-    ![Create Repository](images/index-create-repo.png)
+    ![Create a repository](images/index-create-repo.png)
 
 5. Click **Create**.
 
     You've created your first repository. You should see:
 
-    ![Repository Created](images/index-repo-created.png)
+    ![Repository created](images/index-repo-created.png)
 
 ### Step 3: Download and install Docker Desktop
 
@@ -175,7 +175,7 @@ Docker image locally.
 
 5. Your repository in Docker Hub should now display a new `latest` tag under **Tags**:
 
-    ![Tag Created](images/index-tag.png)
+    ![Tag created](images/index-tag.png)
 
 Congratulations! You've successfully:
 

docker-hub/repos/access/index.md

@@ -27,7 +27,7 @@ see the [organizations documentation](../../../docker-hub/orgs.md#create-an-orga
 Docker Hub's individual repositories view shows you the available tags and the
 size of the associated image. Go to the **Repositories** view and select repository to see its tags. To view individual tags, select the **Tags** tab.
 
-![View Repo Tags](../../images/repo-overview.png)
+![View repo tags](../../images/repo-overview.png)
 
 Image sizes are the cumulative space taken up by the image and all its parent
 images. This is also the disk space used by the contents of the `.tar` file
@@ -48,7 +48,7 @@ To delete a tag, select the corresponding checkbox and select **Delete** from th
 
 You can select a tag's digest to view more details.
 
-![View Tag](../../images/repo-image-layers.png)
+![View tag](../../images/repo-image-layers.png)
 
 ## Searching for repositories
 

docker-hub/repos/configure/index.md

@@ -11,7 +11,7 @@ When configuring repositories, your private repositories let you keep your conta
 
 You can make an existing repository private by going to its **Settings** tab and select **Make private**.
 
-![Repo make private](../../images/repo-make-private.png){: style="max-width: 60%"}
+![Make a repo private](../../images/repo-make-private.png){: style="max-width: 60%"}
 
 You get one free private repository with your Docker Hub user account (not
 available for organizations you're a member of). If you need more private

docker-hub/repos/index.md

@@ -53,7 +53,7 @@ To create a private repository, navigate to Docker Hub and select **Repositories
 >
 > To update your public repository to private, navigate to your repository, select **Settings** and **Make private**.
 
-![Create Private Repo](/docker-hub/images/repo-create-private.png){: style="max-width: 60%"}
+![Create a private repo](/docker-hub/images/repo-create-private.png){: style="max-width: 60%"}
 
 ## Deleting a repository