AAP-4208A updated accessibility formatting (ansible#792) (ansible#831)

* AAP-4208A updated accessibility formatting

* AAP-4208A updated accessibility formatting

* AAP-4208A updated accessibility formatting

* AAP-4208A updated image formatting

downstream/assemblies/platform/assembly-installing-controller-operator.adoc

@@ -31,8 +31,8 @@ When an instance of {ControllerName} is removed, the associated PVCs are not aut
 
 == Installing the {ControllerName} operator
 
-. Navigate to *Operators* > *Installed Operators*, then click on the *Ansible Automation Platform* operator.
-. Locate the *Automation controller* tab, then click *Create instance*.
+. Navigate to menu:Operators[Installed Operators], then click on the *Ansible Automation Platform* operator.
+. Locate the *Automation controller* tab, then click btn:[Create instance].
 
 You can proceed with configuring the instance using either the Form View or YAML view.
 
@@ -43,9 +43,9 @@ include::platform/proc-configuring-controller-ldap-security.adoc[leveloffset=+2]
 include::platform/proc-configuring-controller-route-options.adoc[leveloffset=+2]
 include::platform/proc-hub-ingress-options.adoc[leveloffset=+2]
 
-Once you have configured your {ControllerName} operator, click *Create* at the bottom of the form view. {OCP} will now create the pods. This may take a few minutes.
+Once you have configured your {ControllerName} operator, click btn:[Create] at the bottom of the form view. {OCP} will now create the pods. This may take a few minutes.
 
-* View progress by navigating to *Workloads* -> *Pods* and locating the newly created instance.
+* View progress by navigating to menu:Workloads[Pods] and locating the newly created instance.
 
 include::platform/proc-operator-external-db-controller.adoc[leveloffset=+1]
 

downstream/assemblies/platform/assembly-installing-hub-operator.adoc

@@ -30,14 +30,14 @@ When an instance of {HubName} is removed, the PVCs are not automatically deleted
 == Installing the {HubName} operator
 
 . Navigate to menu:Operators[Installed Operators].
-. Locate the *Automation hub* entry, then click *Create instance*.
+. Locate the *Automation hub* entry, then click btn:[Create instance].
 
 include::platform/con-storage-options-for-operator-installation-on-ocp.adoc[leveloffset=+2]
 include::platform/proc-provision-ocp-storage-with-readwritemany.adoc[leveloffset=+3]
 include::platform/proc-hub-route-options.adoc[leveloffset=+2]
 include::platform/proc-hub-ingress-options.adoc[leveloffset=+2]
 
-Once you have configured your {HubName} operator, click *Create* at the bottom of the form view. {OCP} will now create the pods. This may take a few minutes.
+Once you have configured your {HubName} operator, click btn:[Create] at the bottom of the form view. {OCP} will now create the pods. This may take a few minutes.
 
 * View progress by navigating to menu:Workloads[Pods] and locating the newly created instance.
 

downstream/modules/aap-on-azure/proc-azure-update-route-tables.adoc

@@ -7,15 +7,15 @@ Before you update the route tables, confirm that you satisfy the xref:proc-azure
 [#routing-to-aap]
 .Routing to {AAPonAzureNameShort}
 
-. Navigate to *Route Tables* in the Azure portal.
+. Navigate to menu:Route Tables[] in the Azure portal.
 . As part of your hub-and-spoke configuration, you created one or more route tables to define the routes between the networks. Click on one of these route tables.
-. From the route table menu bar, click *Routes* > *Add*.
+. From the route table menu bar, navigate to menu:Routes[Add].
 . Configure routes from your existing networks to send traffic to {PlatformNameShort}. You must configure routes for any network requesting {PlatformNameShort} user interfaces and for any network that will have automation performed against its resources.
 For each route that you add, enter the following information:
 ** *Route name*: Enter a route name for the {PlatformNameShort} managed application network
 ** *Address Prefix*: The CIDR block of the managed application kubernetes cluster
 ** *Next Hop Type*: _Virtual network gateway_
-. Click *OK* to save the new route to the route list.
+. Click btn:[OK] to save the new route to the route list.
 
 Repeat this procedure for all other route tables where you want to route traffic to {PlatformNameShort}.
 
@@ -24,21 +24,21 @@ Repeat this procedure for all other route tables where you want to route traffic
 
 Add a route for each spoke network that you would like {PlatformNameShort} to communicate with, for automation or for accessing the user interfaces.
 
-. Navigate to *Route Tables* in the Azure portal.
+. Navigate to menu:Route Tables[] in the Azure portal.
 . In the list of route tables, select the route table for the {AAPonAzureNameShort} managed application.
 +
 The name of the {PlatformNameShort} route table uses the following convention:
 +
 ----
 aks-agentpool-<numbers>-routetable
 ----
-. From the route table menu bar, click *Routes* > *Add*.
+. From the route table menu bar, navigate to menu:Routes[Add].
 . Configure routing to your VNets for each spoke network that you would like {PlatformNameShort} to communicate with, for both automation or accessing the user interfaces.
 . For each route that you add, enter the following information:
 ** *Route name*: Enter a route name for the spoke network that you want {PlatformNameShort} to route to
 ** *Address Prefix*: The CIDR block of the spoke network
 ** *Next Hop Type*: _Virtual network gateway_
-. Click *OK* to save the new route to the route list.
+. Click btn:[OK] to save the new route to the route list.
 
 
 After you have configured the routing rules, traffic is routed to and from {PlatformNameShort} on Azure through your hub network.

downstream/modules/analytics/con-jobs-explorer.adoc

@@ -21,7 +21,7 @@ You can sort results by a set of parameters by using the *Sort by* options from
 
 .Procedure
 
-. Navigate to *Insights* > *Job Explorer*.
+. Navigate to menu:Insights[Job Explorer].
 . In the filter toolbar, click the *Filter by* drop-down menu and select *Job*.
 . In that same toolbar, select a time range. Job Explorer will now display jobs within that time range.
 . To further refine results, return to the filter toolbar and select a different attribute to filter results by, including job status, cluster, or organization.

downstream/modules/analytics/proc-add-roles-to-group.adoc

@@ -11,10 +11,10 @@ Adding roles to an existing group will grant new permissions to existing users i
 .Procedure
 
 . Log in to cloud.redhat.com
-. Click image:cog.png[] > *Settings*.
-. From the sidebar, navigate to *User Access* > *Groups*.
+. Click image:cog.png[] and select *Settings*.
+. From the sidebar, navigate to menu:User Access[Groups].
 . Click the group you want to add users to.
-. Click *Add role*.
-. Select one or more roles to add to this group, then click *Add to group*.
+. Click btn:[Add role].
+. Select one or more roles to add to this group, then click btn:[Add to group].
 
 The selected roles will now be granted to the users of the group. You can review the roles in a group by checking the Roles tab.

downstream/modules/analytics/proc-add-user-to-group.adoc

@@ -11,10 +11,10 @@ You can add users to groups when creating a group or by manually adding users to
 .Procedure
 
 . Log in to cloud.redhat.com
-. Click image:cog.png[] > *Settings*.
-. From the sidebar, navigate to *User Access* > *Groups*.
+. Click image:cog.png[] and select *Settings*.
+. From the sidebar, navigate to menu:User Access[Groups].
 . Click the group you want to add users to.
-. Navigate to the Members tab, then click *Add member*.
-. Select one or more users to add to this group, then click *Add to group*.
+. Navigate to the Members tab, then click btn:[Add member].
+. Select one or more users to add to this group, then click btn:[Add to group].
 
 The selected users will now be added to the group. You can review the users in a group by checking the Members tab.

downstream/modules/analytics/proc-create-groups.adoc

@@ -11,19 +11,19 @@ You can create and assign roles to a group that enables users to access specific
 .Procedure
 
 . Log in to cloud.redhat.com
-. Click image:cog.png[] > *Settings*.
-. From the sidebar, navigate to *User Access* > *Groups*.
-. Click *Create group*.
-. A setup wizard will now appear. Enter a group name and description, then click *Next*.
-. Select one or more roles to add to this group, then click *Next*.
+. Click image:cog.png[] and select *Settings*.
+. From the sidebar, navigate to menu:User Access[Groups].
+. Click btn:[Create group].
+. A setup wizard will now appear. Enter a group name and description, then click btn:[Next].
+. Select one or more roles to add to this group, then click btn:[Next].
 
 [NOTE]
 ====
 Any user in this group will have all the permissions prescribed to each role. See the role reference table for a full list of roles
 ====
 
 [start=7]
-. Select one or more users to add to this group, then click *Next*.
-. Review the details, then click *Submit* to create the group.
+. Select one or more users to add to this group, then click btn:[Next].
+. Review the details, then click btn:[Submit] to create the group.
 
 Users in the group can now access features in {InsightsShort} associated with their assigned permissions.

downstream/modules/analytics/proc-create-savings-plan.adoc

@@ -12,23 +12,23 @@ Create an automation savings plan by defining the tasks needed to complete an au
 
 .Procedure
 
-. Navigate to *Red Hat Insights* > *Savings Planner*.
-. Click *Add Plan*.
+. Navigate to menu:Red Hat Insights[Savings Planner].
+. Click btn:[Add Plan].
 . Provide some information about your automation job:
 .. Enter descriptive information, such as a name, description, and type of automation.
 .. Enter technical information, such as the number of hosts, the duration to manually complete this job, and how often you complete this job.
-.. Click *Next*.
+.. Click btn:[Next].
 . In the tasks section, list the tasks needed to complete this plan:
-.. Enter each task in the field, then *Add*.
+.. Enter each task in the field, then click btn:[Add].
 .. Rearrange tasks by dragging the item up/down the tasks list.
-.. Click *Next*.
+.. Click btn:[Next].
 
 [NOTE]
 ====
 The task list is for your planning purposes only, and does not currently factor into your automation savings calculation.
 ====
 
 [start=5]
-. Select a template to link to this plan, then click *Save*.
+. Select a template to link to this plan, then click btn:[Save].
 
 Your new savings plan is now created and displayed on the {planner} list view.

downstream/modules/analytics/proc-edit-savings-plan.adoc

@@ -9,6 +9,6 @@
 Edit any information about an existing savings plan by clicking on it from the savings planner list view.
 
 .Procedure
-. Navigate to *Red Hat Insights* > *Savings Planner*.
-. On the automation savings plan, click image:ellipsis.png[More,10,25] > *Edit*.
-. Make any changes to the automation plan, then click *Save*.
+. Navigate to menu:Red Hat Insights[Savings Planner].
+. On the automation savings plan, click image:ellipsis.png[More,10,25] and select *Edit*.
+. Make any changes to the automation plan, then click btn:[Save].

downstream/modules/analytics/proc-filter-plans.adoc

@@ -9,5 +9,5 @@
 Find specific types of automation savings plans by filtering or sorting your savings planner list view.
 
 .Procedure
-. Navigate to *Red Hat Insights* > *Savings Planner*.
+. Navigate to menu:Red Hat Insights[Savings Planner].
 . To filter your saving plans based on type, or sort your savings plans by a certain order, select a filter option on the horizontal toolbar.

downstream/modules/analytics/proc-link-plan-job-template.adoc

@@ -9,6 +9,6 @@
 You can associate a job template to a savings plan to allow {InsightsShort} to provide a more accurate time and cost savings estimate for completing this savings plan.
 
 .Procedure
-. Navigate to *Red Hat Insights* > *Savings Planner*.
-. Click image:ellipsis.png[More,10,25] > *Link Template*.
-. Click *Save*.
+. Navigate to menu:Red Hat Insights[Savings Planner].
+. Click image:ellipses.png[More,10,25] and select *Link Template*.
+. Click btn:[Save].

downstream/modules/analytics/proc-view-failed-jobs-detail.adoc

@@ -11,7 +11,7 @@ You can view more detail about failed jobs across your organization by drilling
 
 .Procedure
 
-. Navigate to *Insights* > *Clusters*.
+. Navigate to menu:Insights[Clusters].
 . In the filter toolbar, apply filters for clusters and time range of your choosing.
 . Click on a segment on the graph.
 

downstream/modules/automation-hub/proc-add-user-to-group.adoc

@@ -14,10 +14,10 @@ You can add users to groups when creating a group or manually add users to exist
 .Procedure
 
 . Log in to Automation Hub
-. Navigate to *User Access* > *Groups*.
+. Navigate to menu:User Access[Groups].
 . Click on a Group name.
-. Navigate to the *Users* tab, then click *Add*.
-. Select users to add from the list and click *Add*.
+. Navigate to the menu:Users[] tab, then click btn:[Add].
+. Select users to add from the list and click btn:[Add].
 
 
 You have now added the users you selected to the group. These users now have permissions to use Automation Hub assigned to the group.

downstream/modules/automation-hub/proc-assigning-permissions.adoc

@@ -12,10 +12,10 @@ You can assign permissions to groups in Automation Hub that enable users to acce
 
 .Procedure
 . Log in to your local Automation Hub.
-. Navigate to *User Access* > *Groups*.
+. Navigate to menu:User Access[Groups].
 . Click on a group name.
-. Select the *Permissions* tab, then click *Edit*.
+. Select the *Permissions* tab, then click btn:[Edit].
 . Click in the field for each permission type and select permissions that appear in the list.
-. Click *Save* when finished assigning permissions.
+. Click btn:[Save] when finished assigning permissions.
 
 The group can now access features in Automation Hub associated the their assigned permissions.

downstream/modules/automation-hub/proc-create-groups.adoc

@@ -12,8 +12,8 @@ You can create and assign permissions to a group in Automation Hub that enables
 
 .Procedure
 . Log in to your local Automation Hub.
-. Navigate to *User Access* > *Groups*.
-. Click *Create*.
-. Provide a *Name* and click *Create*.
+. Navigate to menu:User Access[Groups].
+. Click btn:[Create].
+. Provide a *Name* and click btn:[Create].
 
 You can now assign permissions and add users on the new group edit page.

downstream/modules/automation-hub/ref-permissions.adoc

@@ -60,7 +60,7 @@ Change collection remote
 
 View collection remote |
 
-Groups with these permissions can configure remote repository under *Collections* > *Repo Management*.
+Groups with these permissions can configure remote repository by navigating to menu:Collections[Repo Management].
 
 h| containers |
 

downstream/modules/platform/proc-configuring-reverse-proxy.adoc

@@ -12,7 +12,7 @@ You can support a reverse proxy server configuration by adding `HTTP_X_FORWARDED
 
 .Procedure
 
-. On your {ControllerName}, navigate to *Settings* > *Miscellaneous System*.
+. On your {ControllerName}, navigate to menu:Settings[Miscellaneous System].
 . In the *REMOTE_HOST_HEADERS* field, enter the following values:
 +
 ----

downstream/modules/platform/proc-enable-proxy-support.adoc

@@ -9,7 +9,7 @@ To enable proxy server support, edit the *REMOTE_HOST_HEADERS* field in the sett
 
 .Procedure
 
-. On your {ControllerName}, navigate to *Settings* > *Miscellaneous System*.
+. On your {ControllerName}, navigate to menu:Settings[Miscellaneous System].
 . In the *REMOTE_HOST_HEADERS* field, enter the following values:
 +
 ----

downstream/modules/platform/proc-restore-aap-backup.adoc

@@ -15,7 +15,7 @@ $ ./setup.sh -r -e ‘restore_backup_file=/ansible/mybackup/tower-backup-latest.
 <3> `-r` sets the restore database option to `True`
 
 . Log in to your new RHEL 8 Tower 3.8 instance to verify whether the content from your original instance has been restored:
-.. Navigate to *Administration* > *Instance groups*. The recreated instance groups should now contain the *Total Jobs* from your original instance.
+.. Navigate to menu:Administration[Instance groups]. The recreated instance groups should now contain the *Total Jobs* from your original instance.
 .. Using the side navigation panel, check that your content has been imported from your original instance, including Jobs, Templates, Inventories, Credentials, and Users.
 
 You now have a new instance of Ansible Tower with all the Ansible content from your original instance.