diff --git a/content/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment.md b/content/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment.md
index c40bd9e80165..6774d27239c0 100644
--- a/content/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment.md
+++ b/content/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment.md
@@ -208,7 +208,7 @@ Variables stored in an environment are only available to workflow jobs that refe
1. Optionally, specify what branches{% ifversion deployment-protections-tag-patterns %} and tags{% endif %} can deploy to this environment. For more information, see "[Deployment branches{% ifversion deployment-protections-tag-patterns %} and tags{% endif %}](/actions/deployment/targeting-different-environments/managing-environments-for-deployment#deployment-branches{% ifversion deployment-protections-tag-patterns %}-and-tags{% endif %})."
1. Select the desired option in the **Deployment branches** dropdown.
1. If you chose **Selected branches{% ifversion deployment-protections-tag-patterns %} and tags{% endif %}**, to add a new rule, click **Add deployment branch{% ifversion deployment-protections-tag-patterns %} or tag{% endif %} rule**
- {% ifversion deployment-protections-tag-patterns %}1. In the "Ref type" dropdown menu, depending on what rule you want to apply, click **{% octicon "git-branch" aria-label="The branch icon" %} Branch** or **{% octicon "tag" aria-label="The tag icon" %} Tag**.{% endif %}
+ {% ifversion deployment-protections-tag-patterns %}1. In the "Ref type" dropdown menu, depending on what rule you want to apply, click **{% octicon "git-branch" aria-hidden="true" %} Branch** or **{% octicon "tag" aria-hidden="true" %} Tag**.{% endif %}
1. Enter the name pattern for the branch{% ifversion deployment-protections-tag-patterns %} or tag{% endif %} that you want to allow.
{% ifversion deployment-protections-tag-patterns %}
diff --git a/content/apps/using-github-apps/reviewing-and-modifying-installed-github-apps.md b/content/apps/using-github-apps/reviewing-and-modifying-installed-github-apps.md
index a3f512be1129..6c9f62ce3c0d 100644
--- a/content/apps/using-github-apps/reviewing-and-modifying-installed-github-apps.md
+++ b/content/apps/using-github-apps/reviewing-and-modifying-installed-github-apps.md
@@ -38,7 +38,7 @@ In addition to reviewing {% data variables.product.prodname_github_apps %} that
> In the following steps, you will be taken to the account settings for the organization or personal account where the {% data variables.product.prodname_github_app %} is installed. The settings will affect all repositories where the app is installed under that account, not just the repository where you navigated from.
1. Navigate to the main page of the organization or repository.
- 1. Click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+ 1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. Under "Integrations," click **GitHub Apps**. A list of the {% data variables.product.prodname_github_apps %} that have been granted access to your repository will be displayed.
1. Next to the {% data variables.product.prodname_github_app %} you want to review or modify, click **Configure**.
diff --git a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.md b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.md
index 4d3ca26dee19..cf30340a821a 100644
--- a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.md
+++ b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.md
@@ -38,7 +38,7 @@ You can run {% data variables.product.prodname_code_scanning %} on {% data varia
With advanced setup for {% data variables.product.prodname_code_scanning %}, you can customize a {% data variables.product.prodname_code_scanning %} workflow for granular control over your configuration. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning)."
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% ifversion fpt or ghec %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.code-scanning.codeql_workflow %} file.
+{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% ifversion fpt or ghec %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-hidden="true" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.code-scanning.codeql_workflow %} file.
## Editing a {% data variables.product.prodname_code_scanning %} workflow
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts.md b/content/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts.md
index 4a65a614103a..5ee3830cfc73 100644
--- a/content/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts.md
+++ b/content/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts.md
@@ -44,7 +44,7 @@ With a {% data variables.product.prodname_copilot_enterprise %} license, you can
{% data reusables.repositories.sidebar-security %}
{% data reusables.repositories.sidebar-code-scanning-alerts %}
1. Click the name of an alert.
-1. If {% data variables.product.prodname_copilot_autofix_short %} can suggest a fix, at the top of the page, click **{% octicon "shield-check" aria-label="Generate fix" %} Generate fix**.
+1. If {% data variables.product.prodname_copilot_autofix_short %} can suggest a fix, at the top of the page, click **{% octicon "shield-check" aria-hidden="true" %} Generate fix**.
1. Once the suggested fix has been generated, at the bottom of the page, you can click **Create PR with fix** to automatically generate a pull request with the suggested fix.
A new branch is created from the default branch, the generated fix is committed and a draft pull request is created. You can test and edit the suggested fix as you would with any other fix.
diff --git a/content/code-security/code-scanning/troubleshooting-code-scanning/default-setup-fails-with-a-language.md b/content/code-security/code-scanning/troubleshooting-code-scanning/default-setup-fails-with-a-language.md
index 228c24dfdeb7..20c8d2154aee 100644
--- a/content/code-security/code-scanning/troubleshooting-code-scanning/default-setup-fails-with-a-language.md
+++ b/content/code-security/code-scanning/troubleshooting-code-scanning/default-setup-fails-with-a-language.md
@@ -14,7 +14,7 @@ To enable default setup when a language previously failed, you must reconfigure
1. If default setup fails, navigate to the main page of your repository, then click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" %} Code security and analysis**.
1. Navigate to the "{% data variables.product.prodname_code_scanning_caps %}" section. Then, in the error message reading "{% data variables.product.prodname_codeql %} default configuration **failed**", click **failed**.
-1. In the "Jobs" section of the workflow run summary for default setup, identify any failing jobs associated with specific languages. These jobs will be labeled **{% octicon "x-circle-fill" aria-label="failed" %} Analyze (LANGUAGE)**.
+1. In the "Jobs" section of the workflow run summary for default setup, identify any failing jobs associated with specific languages. These jobs will be labeled **{% octicon "x-circle-fill" aria-hidden="true" %} Analyze (LANGUAGE)**.
1. Once you have determined which language-specific jobs are failing, configure default setup once more and deselect the failing languages for analysis. For more information, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning)."
Alternatively, if you would like to analyze every language in your repository, you can configure advanced setup for {% data variables.product.prodname_code_scanning %}. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning)."
diff --git a/content/code-security/getting-started/quickstart-for-securing-your-repository.md b/content/code-security/getting-started/quickstart-for-securing-your-repository.md
index 84fb9a45a2aa..9c2ed5357463 100644
--- a/content/code-security/getting-started/quickstart-for-securing-your-repository.md
+++ b/content/code-security/getting-started/quickstart-for-securing-your-repository.md
@@ -31,7 +31,7 @@ Your security needs are unique to your repository, so you may not need to enable
The first step to securing a repository is to establish who can see and modify your code. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features)."
-From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**, then scroll down to the "Danger Zone."
+From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**, then scroll down to the "Danger Zone."
* To change who can view your repository, click **Change visibility**. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)."
* To change who can access your repository and adjust permissions, click **Manage access**. For more information, see"[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
@@ -41,7 +41,7 @@ From the main page of your repository, click **{% octicon "gear" aria-label="The
{% ifversion fpt or ghec %}
{% data reusables.dependency-graph.feature-availability %} The dependency graph interprets manifest and lock files in a repository to identify dependencies.
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. Click **Security & analysis**.
1. Next to Dependency graph, click **Enable** or **Disable**.
{% endif %}
@@ -82,7 +82,7 @@ Dependency review lets you visualize dependency changes in pull requests before
Dependency review is a {% data variables.product.prodname_GH_advanced_security %} feature. {% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/quickstart-for-securing-your-repository#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec or ghes %}To enable dependency review for a {% ifversion ghec %}private or internal {% endif %}repository, ensure that the dependency graph is enabled and enable {% data variables.product.prodname_GH_advanced_security %}.
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. Click **Security & analysis**.
1. {% ifversion ghec %}If dependency graph is not already enabled, click **Enable**.{% elsif ghes %}Check that dependency graph is configured for your enterprise.{% endif %}
1. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.
@@ -93,7 +93,7 @@ Dependency review is a {% data variables.product.prodname_GH_advanced_security %
For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected.
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. Click **Security & analysis**.
1. Next to {% data variables.product.prodname_dependabot_security_updates %}, click **Enable**.
@@ -104,7 +104,7 @@ For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-secu
You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)."
{% ifversion dependabot-settings-update-37 %}
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. Click **Security & analysis**.
1. Next to {% data variables.product.prodname_dependabot_version_updates %}, click **Enable** to create a basic `dependabot.yml` configuration file.
1. Specify the dependencies to update and any associated configuration options, then commit the file to the repository. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)."
@@ -131,7 +131,7 @@ Alternatively, you can use advanced setup, which generates a workflow file you c
{% data reusables.gated-features.secret-scanning %}
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. Click **Code security & analysis**.
{% ifversion ghec or ghes %}
1. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.{% endif %}
@@ -141,7 +141,7 @@ Alternatively, you can use advanced setup, which generates a workflow file you c
If you are a repository maintainer, it's good practice to specify a security policy for your repository by creating a file named `SECURITY.md` in the repository. This file instructs users about how to best contact you and collaborate with you when they want to report security vulnerabilities in your repository. You can view the security policy of a repository from the repository’s **Security** tab.
-1. From the main page of your repository, click **{% octicon "shield" aria-label="The shield symbol" %} Security**.
+1. From the main page of your repository, click **{% octicon "shield" aria-hidden="true" %} Security**.
1. Click **Security policy**.
1. Click **Start setup**.
1. Add information about supported versions of your project and how to report vulnerabilities.
diff --git a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning.md b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning.md
index f4b2074b8e48..e3433484ca50 100644
--- a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning.md
+++ b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning.md
@@ -34,7 +34,7 @@ You can specify custom patterns for {% data variables.product.prodname_secret_sc
### Regular expression syntax for manually defining custom patterns {% endif %}
-The **More options {% octicon "chevron-down" aria-label="down" %}** section in the UI helps you write regular expressions manually.
+The **More options {% octicon "chevron-down" aria-hidden="true" %}** section in the UI helps you write regular expressions manually.
* **Secret format:** an expression that describes the format of the secret itself.
* **Before secret:** an expression that describes the characters that come before the secret. By default, this is set to `\A|[^0-9A-Za-z]` which means that the secret must be at the start of a line or be preceded by a non-alphanumeric character.
diff --git a/content/code-security/security-overview/filtering-alerts-in-security-overview.md b/content/code-security/security-overview/filtering-alerts-in-security-overview.md
index 850df50113bc..bef09d25e828 100644
--- a/content/code-security/security-overview/filtering-alerts-in-security-overview.md
+++ b/content/code-security/security-overview/filtering-alerts-in-security-overview.md
@@ -43,7 +43,7 @@ All security views have features to help you define filters. These provide an ea
* **Interactive search text box.** When you click in the search box and press the keyboard "Space" key, a pop-up text box shows the filter options available in that view. You can use the mouse or keyboard arrow keys to select the options you want in the text box before pressing the keyboard "Return" key to add the filter. Supported for all views.
* **Dropdown selectors and toggles.** Shown at the end of the "Search text box" or in the header of the data table. As you choose the data to view, the filters shown in the search text box are updated accordingly. Supported on the alert views.{% ifversion security-overview-3-13-overview %}
-* **Advanced filters dialog.** When you click the **{% octicon "filter" aria-label="Advanced filter dialog" %} Filter** button, you can use dropdown lists to select the "Qualifier", "Operator", and "Values" for each filter. Supported on the "Overview" and metric views.{% endif %}
+* **Advanced filters dialog.** When you click the **{% octicon "filter" aria-hidden="true" %} Filter** button, you can use dropdown lists to select the "Qualifier", "Operator", and "Values" for each filter. Supported on the "Overview" and metric views.{% endif %}
## Repository name, visibility, and status filters
diff --git a/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/managing-requests-for-copilot-business-in-your-organization.md b/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/managing-requests-for-copilot-business-in-your-organization.md
index a15c1cc3f622..6c1a122f76e8 100644
--- a/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/managing-requests-for-copilot-business-in-your-organization.md
+++ b/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/managing-requests-for-copilot-business-in-your-organization.md
@@ -19,7 +19,7 @@ If your organization is owned by an enterprise, before you can approve a request
{% data reusables.profile.access_org %}
{% data reusables.organizations.org-list %}
-1. In the "Access" section of the sidebar, click **{% octicon "bell" aria-label="The notifications bell" %} Requests from members**.
+1. In the "Access" section of the sidebar, click **{% octicon "bell" aria-hidden="true" %} Requests from members**.
1. To accept the request and grant the member access to {% data variables.product.prodname_copilot_for_business %}, click **Buy {% data variables.product.prodname_copilot_business_short %}**.
All requests for {% data variables.product.prodname_copilot_for_business %} are grouped together under "{% data variables.product.prodname_copilot_business_short %}."
diff --git a/content/copilot/using-github-copilot/asking-github-copilot-questions-in-your-ide.md b/content/copilot/using-github-copilot/asking-github-copilot-questions-in-your-ide.md
index 93fe46f10cca..fc33d9831f12 100644
--- a/content/copilot/using-github-copilot/asking-github-copilot-questions-in-your-ide.md
+++ b/content/copilot/using-github-copilot/asking-github-copilot-questions-in-your-ide.md
@@ -406,7 +406,7 @@ By default, {% data variables.product.prodname_copilot_chat_short %} will refere
* **Built-in requests**. In addition to submitting prompts through the chat window, you can submit built-in requests by right clicking in a file, selecting **{% data variables.product.prodname_copilot %}**, then selecting one of the options.
* **Inline**. You can submit a chat prompt inline, and scope it to a highlighted code block or your current file.
- * To start an inline chat, right click on a code block or anywhere in your current file, hover over **{% data variables.product.prodname_copilot %}**, then select **{% octicon "plus" aria-label="plus" %} {% data variables.product.prodname_copilot_short %}: Inline Chat**, or enter Ctrl+Shift+I.
+ * To start an inline chat, right click on a code block or anywhere in your current file, hover over **{% data variables.product.prodname_copilot %}**, then select **{% octicon "plus" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}: Inline Chat**, or enter Ctrl+Shift+I.
## Sharing feedback
diff --git a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
index 5b1756f5feb3..509b21dd8f6f 100644
--- a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
+++ b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
@@ -39,7 +39,7 @@ You cannot comment on a pull request from {% data variables.product.prodname_des
{% data reusables.repositories.sidebar-pr %}
1. In the list of pull requests, click the pull request that you would like to open in {% data variables.product.prodname_desktop %}.
-1. To the right of the title of the pull request, click **{% octicon "code" aria-label="" %} Code**, then, on the **Local** tab, click **Checkout with GitHub Desktop**.
+1. To the right of the title of the pull request, click **{% octicon "code" aria-hidden="true" %} Code**, then, on the **Local** tab, click **Checkout with GitHub Desktop**.
diff --git a/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md b/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
index 55fab5fb9fb4..fd7ba2e6e664 100644
--- a/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
+++ b/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
@@ -36,7 +36,7 @@ To star a repository: Go to your {% data variables.product.prodname_community_ex
The {% data variables.product.prodname_community_exchange %} community moderates repository submissions. You can report abusive repositories, spammy, or disruptive content at any time.
-To report an abusive repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to report, click the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down right by its name, then click **{% octicon "report" aria-label="The report symbol" %} Report abuse**.
+To report an abusive repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to report, click the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down right by its name, then click **{% octicon "report" aria-hidden="true" %} Report abuse**.
## Further reading
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index b9383aa86269..de52c693eeec 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -47,7 +47,7 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} from the sidebar
-1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**.
+1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-hidden="true" %}**.
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md
index 958d8698adab..47f5b1831c7e 100644
--- a/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md
@@ -85,7 +85,7 @@ You can add up to six templates to your organization's recommended templates.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
1. Under "Recommended templates", click **Customize recommended templates**.
1. In the list of templates owned by your organization, select up to six templates that you want to recommend to your members.
@@ -99,7 +99,7 @@ You can change the display order of your recommended templates in the "Create pr
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
1. Under "Recommended templates", find the template you want to reposition, click on {% octicon "grabber" aria-label="Drag to reorder" %}, and drag the template to the new position.
diff --git a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
index 8cde2773ee54..e4adf0cb2689 100644
--- a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
+++ b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -28,7 +28,7 @@ When {% data variables.projects.projects_v1_boards %} are disabled, you will no
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
1. Decide whether to disable {% data variables.projects.projects_v2_and_v1 %} in your organization. Then, under "Projects":
* To disable {% data variables.projects.projects_v2_and_v1 %}, deselect **Enable Projects for the organization**.
* To enable {% data variables.projects.projects_v2_and_v1 %} in the organization, select **Enable Projects for the organization**.
@@ -44,7 +44,7 @@ You can control whether organization members can create {% data variables.projec
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
1. Decide whether to allow members to create {% data variables.projects.projects_v1_boards %} in repositories in your organization. Then, under "Projects (classic) only":
* To enable {% data variables.projects.projects_v1_boards %} in repositories, select **Allow members to enable {% data variables.product.prodname_projects_v1_caps %} for all repositories**.
* To disable {% data variables.projects.projects_v1_boards %} in repositories, deselect **Allow members to enable {% data variables.product.prodname_projects_v1_caps %} for all repositories**.
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
index da22e21a2182..e2fac499f6db 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
@@ -30,7 +30,7 @@ Organizational rulesets that apply to branches of a repository will no longer al
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.navigate-to-branches %}
-1. Next to the branch you want to rename, select the {% octicon "kebab-horizontal" aria-label="More" %} dropdown menu, then click **{% octicon "pencil" aria-label="Rename branch" %} Rename branch**.
+1. Next to the branch you want to rename, select the {% octicon "kebab-horizontal" aria-label="More" %} dropdown menu, then click **{% octicon "pencil" aria-hidden="true" %} Rename branch**.
1. Type a new name for the branch.
1. Review the information about local environments, then click **Rename branch**.
diff --git a/content/repositories/working-with-files/using-files/downloading-source-code-archives.md b/content/repositories/working-with-files/using-files/downloading-source-code-archives.md
index 2f12ff919870..e3929bdd20bf 100644
--- a/content/repositories/working-with-files/using-files/downloading-source-code-archives.md
+++ b/content/repositories/working-with-files/using-files/downloading-source-code-archives.md
@@ -35,7 +35,7 @@ You can download the source code archives in three ways.
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.releases %}
1. At the top of the Releases page, click **Tags**.
-1. To download the source code, click **{% octicon "file-zip" aria-label="The ZIP icon" %} zip** or **{% octicon "file-zip" aria-label="The ZIP icon" %} tar.gz**.
+1. To download the source code, click **{% octicon "file-zip" aria-hidden="true" %} zip** or **{% octicon "file-zip" aria-hidden="true" %} tar.gz**.
diff --git a/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/content/repositories/working-with-files/using-files/navigating-code-on-github.md
index d7ca7323002a..a437e159a56a 100644
--- a/content/repositories/working-with-files/using-files/navigating-code-on-github.md
+++ b/content/repositories/working-with-files/using-files/navigating-code-on-github.md
@@ -79,8 +79,8 @@ Symbol search is a feature of code search. For more information, see "[AUTOTITLE
* To search for a symbol in the repository as a whole, in the symbols pane, click **Search for this symbol in this repository**. To search for a symbol in all repositories on {% data variables.product.prodname_dotcom %}, click **all repositories**.
1. To navigate between references to a symbol, click {% octicon "chevron-down" aria-label="The downwards-facing chevron icon" %} or {% octicon "chevron-up" aria-label="The upwards-facing chevron icon" %}.
-1. To navigate to a specific reference to a symbol, click a result of the symbol search under **{% octicon "chevron-down" aria-label="The downwards-facing chevron icon" %} In this file**.
-1. To exit the search for a specific symbol, click **{% octicon "arrow-left" aria-label="The left arrow icon" %} All Symbols**.
+1. To navigate to a specific reference to a symbol, click a result of the symbol search under **{% octicon "chevron-down" aria-hidden="true" %} In this file**.
+1. To exit the search for a specific symbol, click **{% octicon "arrow-left" aria-hidden="true" %} All Symbols**.
{% endif %}
## Jumping to the definition of a function or method
diff --git a/content/sponsors/getting-started-with-github-sponsors/navigating-your-sponsors-dashboard.md b/content/sponsors/getting-started-with-github-sponsors/navigating-your-sponsors-dashboard.md
index a24a7b1f6b4d..e5f14387d2b6 100644
--- a/content/sponsors/getting-started-with-github-sponsors/navigating-your-sponsors-dashboard.md
+++ b/content/sponsors/getting-started-with-github-sponsors/navigating-your-sponsors-dashboard.md
@@ -61,13 +61,13 @@ You can also choose to attribute your paid sponsorships to another account by li
{% data reusables.organizations.sponsors-dashboard %}
{% data reusables.organizations.navigate-to-sponsoring %}
-1. From the left sidebar, click **{% octicon "gear" aria-label="The Gear icon" %} Settings**.
+1. From the left sidebar, click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. Under "Sponsorship log", click **log**.
### Link your sponsorships to another account
{% data reusables.organizations.sponsors-dashboard %}
{% data reusables.organizations.navigate-to-sponsoring %}
-1. From the left sidebar, click **{% octicon "gear" aria-label="The Gear icon" %} Settings**.
+1. From the left sidebar, click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. Select the **Linked account** dropdown and click the account to use.
1. Click **Link account** to confirm your selection.
diff --git a/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md b/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
index 8ba40e35ba26..a0e002abfa68 100644
--- a/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
+++ b/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
@@ -73,7 +73,7 @@ You can view your {% data variables.product.company_short %} Invoiced Sponsor Ag
1. Navigate to the organization.
{% data reusables.organizations.navigate-to-sponsoring %}
-1. In the sidebar, click **{% octicon "graph" aria-label="The graph icon" %} Insights**.
+1. In the sidebar, click **{% octicon "graph" aria-hidden="true" %} Insights**.
1. Under your balance, click **{% data variables.product.company_short %} Invoiced Sponsor Agreement** to view the agreement.
## Understanding your {% data variables.product.prodname_sponsors %} invoice
diff --git a/data/reusables/actions/add-hosted-runner.md b/data/reusables/actions/add-hosted-runner.md
index c7d7c234852c..3b65799e8e31 100644
--- a/data/reusables/actions/add-hosted-runner.md
+++ b/data/reusables/actions/add-hosted-runner.md
@@ -1,4 +1,4 @@
-1. Click **New runner**, then click **{% octicon "mark-github" aria-label="New hosted runner" %} New {% data variables.product.prodname_dotcom %}-hosted runner**.
+1. Click **New runner**, then click **{% octicon "mark-github" aria-hidden="true" %} New {% data variables.product.prodname_dotcom %}-hosted runner**.
1. Complete the required details to configure your new runner:
* **Name**: Enter a name for your new runner. For easier identification, this should indicate its hardware and operating configuration, such as `ubuntu-20.04-16core`.
diff --git a/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
index 32a66dc1aa1c..ce5d1a319223 100644
--- a/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
+++ b/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
@@ -1,10 +1,10 @@
{% ifversion fpt %}
1. Navigate to the main page of the organization or repository.
-1. Click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
1. In the left sidebar, click **Actions**, then click **Runners**.
{% elsif ghec %}
1. Navigate to your runner settings:
- * **In an organization or repository**: Navigate to the main page, then click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+ * **In an organization or repository**: Navigate to the main page, then click **{% octicon "gear" aria-hidden="true" %} Settings**.
* **If using an enterprise account**: Navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.github %}, then clicking **Your enterprises**, then clicking the enterprise.
1. Navigate to the {% data variables.product.prodname_actions %} settings:
* **In an organization or repository**: Click **Actions** in the left sidebar, then click **Runners**.
diff --git a/data/reusables/actions/runner-groups-org-navigation.md b/data/reusables/actions/runner-groups-org-navigation.md
index 3fe14315d3c9..92291984f152 100644
--- a/data/reusables/actions/runner-groups-org-navigation.md
+++ b/data/reusables/actions/runner-groups-org-navigation.md
@@ -1,3 +1,3 @@
1. Navigate to the main page of the organization where your runner groups are located.
-1. Click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
diff --git a/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md b/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
index 533f9c6a8bfa..242e3d822cb1 100644
--- a/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
+++ b/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
@@ -1 +1 @@
-1. In your organization or repository, navigate to the main page and click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+1. In your organization or repository, navigate to the main page and click **{% octicon "gear" aria-hidden="true" %} Settings**.
diff --git a/data/reusables/actions/self-hosted-runner-navigate-to-org.md b/data/reusables/actions/self-hosted-runner-navigate-to-org.md
index dfd6534605b3..1ed444c9a905 100644
--- a/data/reusables/actions/self-hosted-runner-navigate-to-org.md
+++ b/data/reusables/actions/self-hosted-runner-navigate-to-org.md
@@ -1,3 +1,3 @@
1. Navigate to the main page of the organization where your self-hosted runner group is registered.
-1. Click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
{% data reusables.organizations.settings-sidebar-actions-runners %}
diff --git a/data/reusables/actions/self-hosted-runner-navigate-to-repo.md b/data/reusables/actions/self-hosted-runner-navigate-to-repo.md
index 709d15f0f0bd..d0076c416f48 100644
--- a/data/reusables/actions/self-hosted-runner-navigate-to-repo.md
+++ b/data/reusables/actions/self-hosted-runner-navigate-to-repo.md
@@ -1,3 +1,3 @@
1. Navigate to the main page of the repository where your self-hosted runner group is registered.
-1. Click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
{% data reusables.organizations.settings-sidebar-actions-runners %}
diff --git a/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
index 2a6883520a83..49e52da457bc 100644
--- a/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
+++ b/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
@@ -1,7 +1,7 @@
1. Enter the details for your new custom pattern. You must at least provide the name for your pattern, and a regular expression for the format of your secret pattern.
1. In the "Pattern name" field, type a name for your pattern.
- 1. In the "Secret format" field, type a regular expression for the format of your secret pattern.{% ifversion secret-scanning-custom-pattern-ai-generated %} Alternatively, you can use the generator to generate a regular expression for you. For more information, see "[AUTOTITLE](/code-security/secret-scanning/copilot-secret-scanning/generating-regular-expressions-for-custom-patterns-with-copilot-secret-scanning)."{% endif %}
- 1. You can click **More options {% octicon "chevron-down" aria-label="down" %}** to provide other surrounding content or additional match requirements for the secret format.
+ 1. In the "Secret format" field, type a regular expression for the format of your secret pattern.{% ifversion secret-scanning-custom-pattern-ai-generated %} Alternatively, you can use the generator to generate a regular expression for you. For more information, see "[AUTOTITLE](/code-security/secret-scanning/copilot-secret-scanning/generating-regular-expressions-for-custom-patterns-with-ai)."{% endif %}
+ 1. You can click **More options {% octicon "chevron-down" aria-hidden="true" %}** to provide other surrounding content or additional match requirements for the secret format.
1. Provide a sample test string to make sure your configuration is matching the patterns you expect.
diff --git a/data/reusables/advanced-security/secret-scanning-generate-regular-expression-custom-pattern.md b/data/reusables/advanced-security/secret-scanning-generate-regular-expression-custom-pattern.md
index f75728e1a6f4..8824fed109e6 100644
--- a/data/reusables/advanced-security/secret-scanning-generate-regular-expression-custom-pattern.md
+++ b/data/reusables/advanced-security/secret-scanning-generate-regular-expression-custom-pattern.md
@@ -13,4 +13,4 @@
-1. You can click **More options {% octicon "chevron-down" aria-label="down" %}** to provide other surrounding content or additional match requirements for the secret format. {% data variables.product.prodname_dotcom %} will add the examples you typed in the sliding panel to the **Test string** field.
+1. You can click **More options {% octicon "chevron-down" aria-hidden="true" %}** to provide other surrounding content or additional match requirements for the secret format. {% data variables.product.prodname_dotcom %} will add the examples you typed in the sliding panel to the **Test string** field.
diff --git a/data/reusables/enterprise-accounts/messages-tab.md b/data/reusables/enterprise-accounts/messages-tab.md
index 6d3cb5b9dc8b..f5bec8fd1209 100644
--- a/data/reusables/enterprise-accounts/messages-tab.md
+++ b/data/reusables/enterprise-accounts/messages-tab.md
@@ -1 +1 @@
-1. Under **{% octicon "gear" aria-label="The Settings gear" %} Settings**, click **{% ifversion ghes %}Messages{% elsif ghec %}Announcement{% endif %}**.
+1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **{% ifversion ghes %}Messages{% elsif ghec %}Announcement{% endif %}**.
diff --git a/data/reusables/files/add-file.md b/data/reusables/files/add-file.md
index 58cd9fc76c2e..15e320cb1353 100644
--- a/data/reusables/files/add-file.md
+++ b/data/reusables/files/add-file.md
@@ -1,5 +1,5 @@
{% ifversion code-view-ui %}
-1. Above the list of files, select the **Add file** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %} dropdown menu, then click **{% octicon "plus" aria-label="The plus sign icon" %} Create new file**.
+1. Above the list of files, select the **Add file** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %} dropdown menu, then click **{% octicon "plus" aria-hidden="true" %} Create new file**.
Alternatively, you can click {% octicon "plus" aria-label="The plus sign icon" %} in the file tree view on the left.
diff --git a/data/reusables/repositories/rulesets-require-code-scanning-results.md b/data/reusables/repositories/rulesets-require-code-scanning-results.md
index 230e6d1fbc0b..83df1a2353e4 100644
--- a/data/reusables/repositories/rulesets-require-code-scanning-results.md
+++ b/data/reusables/repositories/rulesets-require-code-scanning-results.md
@@ -1,5 +1,5 @@
1. Under "Branch protections", select **Require {% data variables.product.prodname_code_scanning %} results**.
-1. Under "Required tools and alert thresholds", click **{% octicon "plus" aria-label="Add tool" %} Add tool** and select a {% data variables.product.prodname_code_scanning %} tool with the dropdown. For example, "{% data variables.product.prodname_codeql %}".
+1. Under "Required tools and alert thresholds", click **{% octicon "plus" aria-hidden="true" %} Add tool** and select a {% data variables.product.prodname_code_scanning %} tool with the dropdown. For example, "{% data variables.product.prodname_codeql %}".
1. Next to the name of a {% data variables.product.prodname_code_scanning %} tool:
* Click **Alerts** and select one of: **None**, **Errors**, **Errors and Warnings** or **All**.
* Click **Security alerts** and select one of: **None**, **Critical**, **High or higher**, **Medium or higher**, or **All**.
diff --git a/data/reusables/sponsors/sponsorship-dashboard.md b/data/reusables/sponsors/sponsorship-dashboard.md
index 797190f59945..fc902cec4c9a 100644
--- a/data/reusables/sponsors/sponsorship-dashboard.md
+++ b/data/reusables/sponsors/sponsorship-dashboard.md
@@ -2,5 +2,5 @@
* If you're sponsoring a personal account, under the user's name, click **Sponsoring**.
- * If you're sponsoring an organization, to the right of the organization's name, click **{% octicon "heart-fill" aria-label="" %} Sponsoring**.
+ * If you're sponsoring an organization, to the right of the organization's name, click **{% octicon "heart-fill" aria-hidden="true" %} Sponsoring**.
1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** dropdown menu, then click the organization.