Hack week 2025: Fix alt text in the remaining folders (#53967)

felicitymay · mchammer01 · web-flow · commit fd21fbe407ee · 2025-01-21T12:26:23.000Z
Co-authored-by: mc &lt;42146119+mchammer01@users.noreply.github.com&gt;
diff --git a/content/code-security/security-advisories/working-with-repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/content/code-security/security-advisories/working-with-repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
@@ -36,7 +36,7 @@ Collaborators have write permissions to the security advisory. For more informat
 1. In the "Security Advisories" list, click the security advisory you'd like to add a collaborator to.
 1. On the right side of the page, under "Collaborators", type the name of the user or team you'd like to add to the security advisory.
 1. Click **{% octicon "plus" aria-label="Add Collaborator" %}** to add the selected user or team as a collaborator.
-   ![Screenshot of the "Collaborators" area in the right sidebar of a draft security advisory. The "Add collaborator" button, a plus icon, is outlined in dark orange.](/assets/images/help/security/security-advisory-add-collaborator-button.png)
+   ![Screenshot of the "Collaborators" area in the sidebar of a draft security advisory. The "Add collaborator" button, a plus icon, is outlined in orange.](/assets/images/help/security/security-advisory-add-collaborator-button.png)
 
 ## Further reading
 
diff --git a/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md b/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md
@@ -111,7 +111,7 @@ If GPG verification is disabled in your settings for {% data variables.product.p
 1. On the "User" tab, in the search bar, search for "gpg".
 1. Verify that the "Enables commit signing with GPG or X.509" setting is deselected.
 
-   ![Screenshot of the "User" settings tab. A deselected checkbox, labeled "Enables commit signing with GPG or X.509," is highlighted with an orange outline.](/assets/images/help/codespaces/gpg-vscode-setting.png)
+   ![Screenshot of the "User" settings tab. A deselected checkbox, labeled "Enables commit signing with GPG or X.509," is outlined in orange.](/assets/images/help/codespaces/gpg-vscode-setting.png)
 
 If you find this setting is enabled, you should either deselect the checkbox to stop {% data variables.product.prodname_vscode_shortname %} trying to sign your commits, or you should enable GPG verification for the repository you're working in so your commits can be signed successfully.
 
diff --git a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-github-copilot-pro-subscription/canceling-copilot-pro-as-an-individual-user.md b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-github-copilot-pro-subscription/canceling-copilot-pro-as-an-individual-user.md
@@ -31,6 +31,6 @@ You can cancel your {% data variables.product.prodname_copilot_pro_short %} subs
 {% data reusables.user-settings.billing_plans %}
 1. Under "Add-ons", in the "{% data variables.product.prodname_copilot %}" section, select the **Manage subscription** dropdown on the right and then click **Cancel**.
 
-     ![Screenshot of the {% data variables.product.prodname_copilot %} section of the "Plans and usage" page. The edit dropdown is expanded and the "Cancel" option is highlighted in dark orange.](/assets/images/help/copilot/copilot-cancel-cfi-subscription.png)
+     ![Screenshot of the {% data variables.product.prodname_copilot %} section of the "Plans and usage" page. The edit dropdown is expanded and the "Cancel" option is outlined in orange.](/assets/images/help/copilot/copilot-cancel-cfi-subscription.png)
 
 1. In the "Cancel {% data variables.product.prodname_copilot %}" modal, click **I understand, cancel {% data variables.product.prodname_copilot %}**
diff --git a/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-the-copilot-subscription-for-your-enterprise/downgrading-copilot-for-your-enterprise.md b/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-the-copilot-subscription-for-your-enterprise/downgrading-copilot-for-your-enterprise.md
@@ -18,6 +18,6 @@ redirect_from:
 1. Under "Access management", locate the organization for which you want to downgrade {% data variables.product.prodname_copilot_short %}.
 1. To the right of the organization name, select the **Copilot** dropdown menu, and click **Business**.
 
-   ![Screenshot of the Copilot "access management" page. A dropdown menu is selected, and a button labeled "Business" is highlighted with an orange outline.](/assets/images/help/copilot/copilot-downgrade-to-business.png)
+   ![Screenshot of the Copilot "access management" page. A dropdown menu is selected, and a button labeled "Business" is outlined in orange.](/assets/images/help/copilot/copilot-downgrade-to-business.png)
 
 1. In the pop-up window that appears, review the effects of downgrading the organization, then click **Confirm and downgrade**.
diff --git a/content/copilot/troubleshooting-github-copilot/viewing-logs-for-github-copilot-in-your-environment.md b/content/copilot/troubleshooting-github-copilot/viewing-logs-for-github-copilot-in-your-environment.md
@@ -53,7 +53,7 @@ If you find the log file doesn't contain enough information to resolve an issue,
 
 1. In the menu bar, click **Help**, select **Diagnostic Tools**, and click **Debug Log Settings...**.
 
-   ![Screenshot of the menu bar in a JetBrains IDE. The "Help" menu and "Diagnostic Tools" submenu are expanded, and the "Debug Log Settings" option is highlighted in blue.](/assets/images/help/copilot/jetbrains-debug-log.png)
+   ![Screenshot of the menu bar in a JetBrains IDE. The "Help" menu and "Diagnostic Tools" submenu are expanded and "Debug Log Settings" is highlighted.](/assets/images/help/copilot/jetbrains-debug-log.png)
 
 1. In the "Custom Debug Log Configuration" window, add a new line with the following content, then click **OK**.
 
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md b/content/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -141,7 +141,7 @@ If your organization uses issue types, you can filter issues for a particular ty
 {% data reusables.repositories.sidebar-issues %}
 1. Above the list of issues, select the **Types** dropdown menu.
 
-   ![Screenshot of a list of issues. In the header above the list, the "Types" dropdown menu is expanded and outlined in orange.](/assets/images/help/issues/issue-type-dropdown.png)
+   ![Screenshot of a list of issues. In the list header, the "Types" filter is outlined in orange and expanded.](/assets/images/help/issues/issue-type-dropdown.png)
 
 1. In the list of type, click an issue type.
 
@@ -178,7 +178,7 @@ You can use filters to search for issues and pull requests that meet specific cr
 
 The issues and pull requests search bar allows you to define your own custom filters and sort by a wide variety of criteria. You can find the search bar on each repository's **Issues** and **Pull requests** tabs and on your [Issues and Pull requests dashboards](/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests).
 
-![Screenshot of the list of issues for a repository. Above the list, a search field, containing the query "is:issue is:open", is outlined in dark orange.](/assets/images/help/issues/issues-search-bar.png)
+![Screenshot of the list of issues for a repository. Above the list, a search field, containing the query "is:issue is:open", is outlined in orange.](/assets/images/help/issues/issues-search-bar.png)
 
 > [!TIP]
 > {% data reusables.search.search_issues_and_pull_requests_shortcut %}
diff --git a/content/search-github/searching-on-github/finding-files-on-github.md b/content/search-github/searching-on-github/finding-files-on-github.md
@@ -31,7 +31,7 @@ topics:
 1. Above the list of files, click **Go to file**.
    ![Screenshot of a row of buttons on the main page of a repository. The "Go to file" button is outlined in dark orange.](/assets/images/help/search/find-file-button.png)
 1. In the search field, type the name of the file you'd like to find.
-   ![Screenshot of the search bar for finding a file in a repository. The search bar contains the term "readme" and under the search bar is a link to the file that is the result of the search, "README.md". The search bar is outlined in dark orange.](/assets/images/help/search/find-file-search-field.png)
+   ![Screenshot of the repository file search bar. The search bar has the term "readme." Results are shown under the search bar and include "README.md."](/assets/images/help/search/find-file-search-field.png)
 1. In the list of results, click the file you wanted to find.
 {% endif %}
 
diff --git a/content/support/contacting-github-support/providing-data-to-github-support.md b/content/support/contacting-github-support/providing-data-to-github-support.md
@@ -138,7 +138,7 @@ You can use these steps to create and share a support bundle if you have SSH acc
 {% data reusables.enterprise-accounts.license-tab %}
 1. Under "{% data variables.product.prodname_enterprise %} Help", click **Upload a support bundle**.
 
-   ![Screenshot of the "GitHub Enterprise help" section of the enterprise settings page. The "Upload a support bundle link" is highlighted with a dark orange rectangle.](/assets/images/enterprise/support/upload-support-bundle.png)
+   ![Screenshot of the "GitHub Enterprise help" section of the enterprise settings page. The "Upload a support bundle link" is outlined in orange.](/assets/images/enterprise/support/upload-support-bundle.png)
 1. Under "Select an enterprise account", use the drop-down menu to select the support bundle's associated account.
 1. Under "Upload a support bundle for {% data variables.contact.enterprise_support %}", to select your support bundle, click **Choose file**, or drag your support bundle file onto **Choose file**.
 1. Click **Upload**.
diff --git a/data/reusables/pages/settings-verify-domain-confirm.md b/data/reusables/pages/settings-verify-domain-confirm.md
@@ -1,5 +1,5 @@
 1. After confirming that your DNS configuration has updated, you can verify the domain. If the change wasn't immediate, and you have navigated away from the previous page, return to your Pages settings by following the first few steps and, to the right of the domain, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and then click **Continue verifying**.
 
-   ![Screenshot of {% data variables.product.prodname_pages %} settings showing verified domains. Under the horizontal kebab icon to the right, the "Continue verifying" dropdown option is outlined in dark orange.](/assets/images/help/pages/verify-continue.png)
+   ![Screenshot of "Verified domains" settings. Under the horizontal kebab icon to the right, the "Continue verifying" option is outlined in orange.](/assets/images/help/pages/verify-continue.png)
 1. To verify your domain, click **Verify**.
 1. To make sure your custom domain remains verified, keep the TXT record in your domain's DNS configuration.
