updates to alt text

docs/boards/best-practices-agile-project-management.md

@@ -42,7 +42,7 @@ In this article, we make the following suggestions and guidance:
 
 ## Configure your teams   
 
-Azure Boards provides each team a set of Agile tools to plan and track work. Each project defines a default team, which you can start using immediately. However, if you have a number of development or feature teams, we recommend that you define a team in Azure DevOps for each feature team. This way, each team can work autonomously while collaborating with each other. 
+Azure Boards provides each team a set of Agile tools to plan and track work. Each project defines a default team, which you can start using immediately. However, if you have several development or feature teams, we recommend that you define a team in Azure DevOps for each feature team. This way, each team can work autonomously while collaborating with each other. 
 
 #### Best practice tips: 
 
@@ -244,7 +244,7 @@ In Microsoft Project, you manage tasks that depend on the completion of other ta
 
 ### Add link dialog
 
-Azure Boards supports a number of link types to track related work. Choose the Predecessor/Successor link types to track work with dependencies. The quickest way to add a number of these links is to add a tag to work items that participate in producing or consuming dependencies, create a query based on this tag, and then add the required links from the triage mode of the query results. 
+Azure Boards supports many link types to track related work. Choose the **Predecessor/Successor** link types to track work with dependencies. A quick way to link work items is to add a tag to work items that participate in producing or consuming dependencies, create a query based on this tag, and then add the required links from the [triage mode of the query results](queries/triage-work-items.md). 
 
 The following Add link dialog illustrates how two work items are linked using the Successor link type. 
 

docs/boards/configure-customize.md

@@ -319,7 +319,7 @@ A default team and default area path are defined for each project. For small tea
 Here is an example of area paths and their assignment to teams, which support portfolio management views for the Account Management and Service Delivery teams. 
 
 > [!div class="mx-imgBorder"] 
-> ![Area paths and team assignments](media/config-custom/area-path-team-assignments.png)  
+> ![Screenshot of Area paths and team assignments.](media/config-custom/area-path-team-assignments.png)  
 
 - You create hierarchical area paths to support sub categories of features and product areas 
 - To provide portfolio views, you assign two or more area paths and include sub-areas to a portfolio management team 
@@ -384,14 +384,14 @@ Rollup columns allow you to view progress bars or totals of numeric fields or de
 Here we show **Progress by all Work Items** which displays progress bars for ascendant work items based on the percentage of descendant items that have been closed. 
 
 > [!div class="mx-imgBorder"]  
-> ![Progress bars showing rollup by work items](media/config-custom/progress-by-work-items.png)  
+> ![Screenshot of backlog, Progress bars showing rollup by work items.](media/config-custom/progress-by-work-items.png)  
 
 ::: moniker range="azure-devops"
 
 In addition, the new [Delivery Plans](plans/review-team-plans.md) supports rollup views of epics, features, and other custom portfolio backlogs. 
 
 > [!div class="mx-imgBorder"]  
-> ![Screenshot showing Delivery Plans Progress rollup view of four scenarios. ](plans/media/plans/rollup-view.png)  
+> ![Screenshot showing Delivery Plans Progress rollup view of four scenarios.](plans/media/plans/rollup-view.png)  
 
 ::: moniker-end
 
@@ -409,7 +409,7 @@ Iteration paths support Scrum and Scrumban processes where work is assigned to a
 Iteration paths can be a simple flat list, or grouped under release milestones as shown in the following image. 
 
 > [!div class="mx-imgBorder"]  
-> ![Iteration paths, grouped](media/config-custom/iteration-paths-flat-or-grouped.png)  
+> ![Screenshot of Iteration paths, grouped.](media/config-custom/iteration-paths-flat-or-grouped.png)  
 
 > [!NOTE]   
 > While Iteration Paths don't impact Kanban board tools, you can use Iteration Paths as a filter on boards. To learn more, see [Filter your Kanban board](./backlogs/filter-backlogs-boards-plans.md).
@@ -476,7 +476,7 @@ Sometimes, teams want to track the status of their work that go beyond these def
 Both workflow states and Kanban columns appear in the Cumulative Flow diagram for a team. Individuals can choose which columns appear in the chart. 
 
 > [!div class="mx-imgBorder"]  
-> ![Cumulative flow diagram](media/config-custom/cumulative-flow-diagram.png)  
+> ![Screenshot of Cumulative flow diagram.](media/config-custom/cumulative-flow-diagram.png)  
 
 To learn more, see [Cumulative flow diagram](../report/dashboards/cumulative-flow.md). 
 

docs/boards/extensions/dependency-tracker.md

@@ -96,12 +96,12 @@ Also, the following configuration or customization tasks should be performed:
 2. Choose **Dependency Tracker** from under the Boards group. 
 
     > [!div class="mx-imgBorder"]  
-    > ![Select Dependency Tracker from Azure Boards](media/tracker/select-dependency-tracker.png)
+    > ![Screenshot showing Dependency Tracker hub in Azure Boards.](media/tracker/select-dependency-tracker.png)
 
 1. To focus on your area of ownership, choose the **Area** that corresponds to the team you want to view dependencies for.   
 
     > [!div class="mx-imgBorder"]  
-    > ![Select Area](media/tracker/choose-area-path.png)
+    > ![Screenshot showing selecting Area.](media/tracker/choose-area-path.png)
 
     You can only filter on those Area paths defined for the project. 
 
@@ -114,7 +114,7 @@ You can filter each supported view by typing a keyword or using one or more of t
 To show the filter toolbar, choose the :::image type="icon" source="../../media/icons/filter-icon.png" border="false"::: filter icon. 
 
 > [!div class="mx-imgBorder"]  
-> ![Filter by keyword or field](media/tracker/filter.png)  
+> ![Screenshot showing Dependency Tracker Filter options.](media/tracker/filter.png)  
 
 You can toggle filters  on and off by choosing the filter icon. To see more filters use the arrows at the end of the list of filters. 
 
@@ -139,7 +139,7 @@ Ability to drop dependencies within the selected area (used for excluding depend
 Several views provide interactive visualizations through drill-downs. These features are addressed in the tabbed views descriptions later in this article. 
 
 > [!div class="mx-imgBorder"]  
-> ![Consuming dependencies, drill-down into completed work in an area](media/tracker/drill-down-completed-consuming.png) 
+> ![Screenshot showing Consuming dependencies, drill-down into completed work in an area.](media/tracker/drill-down-completed-consuming.png) 
 
 
 <a id="create" /> 
@@ -151,17 +151,17 @@ A dependency represents work where one team is dependent on another team. Both t
 1. Choose **New Dependency**.  
 
     > [!div class="mx-imgBorder"]  
-    > ![Choose New Dependency](media/tracker/choose-new-dependency.png)
+    > ![Screenshot showing choose New Dependency.](media/tracker/choose-new-dependency.png)
 
     If the partner team is in a different organization, then first choose the **Partner Account**. The Partner Account option can be enabled or disabled by [configuring the Dependency Tracker](#configuration).   
 
     > [!div class="mx-imgBorder"]  
-    > ![Choose partner account](media/tracker/choose-partner-organization.png)
+    > ![Screenshot of Create dependency dialog, Choose partner account.](media/tracker/choose-partner-organization.png)
 
 1.  You can search for work items by ID or by entering a keyword contained within the work item title. Here, we link a user story and a bug. 
 
     > [!div class="mx-imgBorder"]  
-    > ![Create a dependency, choose two existing work items to link](media/tracker/create-dependency.png)
+    > ![Screenshot of Create dependency dialog, choose two existing work items to link.](media/tracker/create-dependency.png)
 
     - The Producer is the team that commits to delivering the work.
     - The Consumer is the team that needs or is dependent on the work.
@@ -170,7 +170,7 @@ A dependency represents work where one team is dependent on another team. Both t
     Optionally, you can choose **Create New** to add work items that you then link as dependent upon each other. Here we create two new features and link them. 
 
     > [!div class="mx-imgBorder"]  
-    > ![Create a dependency, create new work items to link](media/tracker/create-new-work-items-link-dependency.png)
+    > ![Screenshot of Create dependency dialog, create new work items to link.](media/tracker/create-new-work-items-link-dependency.png)
 
     If no work items exist for one half of the dependency, you can create a new work item as needed.
 
@@ -179,21 +179,21 @@ A dependency represents work where one team is dependent on another team. Both t
 1. From the success confirmation dialog, choose **View dependency**. 
 
     > [!div class="mx-imgBorder"]  
-    > ![Success confirmation](media/tracker/success-confirmation.png)
+    > ![Screenshot of Success confirmation dialog.](media/tracker/success-confirmation.png)
 
 1.  The work items that you linked are highlighted.    
 
     As shown in this example, the Fabrikam Fiber/Service Delivery/Voice team is dependent on the MyFirstProject team to deliver their `User Story 706: Cancel order form` to complete `Bug 390: Cancel order form`. 
 
     > [!div class="mx-imgBorder"]  
-    > ![Linked dependent work items](media/tracker/linked-dependent-work-items.png)
+    > ![Screenshot of Create dependency dialog, Linked dependent work items.](media/tracker/linked-dependent-work-items.png)
 
 ## Create links manually 
 
 You can also link work items using the **Links** tab to create Successor/Predecessor links. A Predecessor is the producer of the work item, or the item that must come first. A Successor is the consumer of the work item, or the item that is dependent on the first item.
 
 > [!div class="mx-imgBorder"]  
-> ![Create links manually](media/tracker/create-links-manually.png)
+> ![Screenshot of Add Link dialog, Create links manually.](media/tracker/create-links-manually.png)
 
 > [!NOTE]   
 > The Successor/Predecessor (consumes/produces) link types are the default link types used by the Dependency Tracker. If you're projects are customized using a Hosted XML process model, it's possible to specify different link types in the Dependency Tracker configuration. See [Configure the Dependency Tracker](#configuration) later in this article.
@@ -205,7 +205,7 @@ To learn more, see [Link user stories, issues, bugs, and other work items](../ba
 You can remove a dependency by choosing the  :::image type="icon" source="../../media/icons/actions-icon.png" border="false"::: actions icon from the linked work item and choose **Remove Dependency Link** option from the menu. 
 
 > [!div class="mx-imgBorder"]  
-> ![Remove dependency links.](media/tracker/remove-dependency-link.png)
+> ![Screenshot of work item list, choose actions menu to remove dependency links.](media/tracker/remove-dependency-link.png)
 
 Optionally, you can remove the link from the work item's **Links** tab. 
 
@@ -214,7 +214,7 @@ Optionally, you can remove the link from the work item's **Links** tab.
 To open a set of dependent work items, select them in the same way you would via a [bulk edit](../backlogs/bulk-modify-work-items.md), choose the  :::image type="icon" source="../../media/icons/actions-icon.png" border="false"::: actions icon from one of the selected linked work items and choose **Open in Query** option from the menu. 
 
 > [!div class="mx-imgBorder"]  
-> ![Create a query of dependencies.](media/tracker/open-as-query.png)
+> ![Screenshot of work item list, Create a query of dependencies.](media/tracker/open-as-query.png)
 
 A new tab opens to the Query Results page. 
 
@@ -233,7 +233,7 @@ The **Consuming Dependencies** view shows work that a team is dependent upon oth
 - *What are the workflow states of my consumer dependencies?*
 
 > [!div class="mx-imgBorder"]  
-> ![Consuming-View](media/tracker/consuming-dependencies-view.png)
+> ![Screenshot of Dependency Tracker, Consuming dependencies view.](media/tracker/consuming-dependencies-view.png)
 
 Each column on the bar chart represents another area path that is producing dependencies by workflow state for the selected **Area View**. The table shows the number of unique dependencies. It also lists all work items participating in the filtered view of tracked dependencies. 
 
@@ -256,7 +256,7 @@ The **Producing Dependencies** view shows work that other teams/area paths are d
 - *What are the workflow states of my producer dependencies?*
 
 > [!div class="mx-imgBorder"]  
-> ![Dependency Tracker](media/tracker/producing-dependencies-view.png)
+> ![Screenshot of Dependency Tracker, Producing dependencies view.](media/tracker/producing-dependencies-view.png)
 
 Each column on the bar chart represents another area path that is consuming dependencies by workflow state for the selected **Area View**. The table shows the number of unique dependencies and lists all work items included in the filtered view of tracked dependencies. 
 
@@ -282,14 +282,14 @@ There are two versions of the Timeline view: **Correct Flow** and **Incorrect Fl
 The Correct Flow view shows those dependencies that are in the correct sequence. Successor work items are scheduled to be completed after their predecessor work item.
 
 > [!div class="mx-imgBorder"]  
-> ![Timeline view, correct flow](media/tracker/timeline-oc-word-2019-correct-flow.png)
+> ![Screenshot of Timeline view, correct flow.](media/tracker/timeline-oc-word-2019-correct-flow.png)
 
 #### Incorrect Flow view
 
 The Incorrect Flow  view shows those dependencies that are out of order. At least one predecessor work item is scheduled to be completed after its successor work item.
 
 > [!div class="mx-imgBorder"]  
-> ![Timeline view, incorrect flow](media/tracker/timeline-oc-word-2019-incorrect-flow.png)
+> ![Screenshot of Timeline view, incorrect flow.](media/tracker/timeline-oc-word-2019-incorrect-flow.png)
 
 
 <a id="risk-graph" />
@@ -299,27 +299,27 @@ The Incorrect Flow  view shows those dependencies that are out of order. At leas
 The Risk Graph provides a visualization of how dependencies flow from Consumer team to Producer team, or from Producer to Consumers. The graph allows a team to, at a glance, understand the number of dependencies and level of risks associated. Also, the risk graph view demonstrates the value of linking dependencies and laddering them up to Stories. 
 
 > [!div class="mx-imgBorder"]  
-> ![Dependency Tracker Risk Graph](media/tracker/risk-graph-1.png)
+> ![Screenshot of Dependency Tracker Risk Graph.](media/tracker/risk-graph-1.png)
 
 There are two views: **Consuming From** and **Producing For**. The workflow state color coding is configurable. The width of the lines indicates how many dependencies exist in that area, the thicker the link the more dependencies as indicated in the legend.
 
 #### Consuming From
 
 > [!div class="mx-imgBorder"]  
-> ![Dependency Tracker Risk Graph, Consuming From](media/tracker/risk-graph-ff-consuming-from.png)
+> ![Screenshot of Dependency Tracker Risk Graph, Consuming From view.](media/tracker/risk-graph-ff-consuming-from.png)
 
 #### Producing For
 
 > [!div class="mx-imgBorder"]  
-> ![Dependency Tracker Risk Graph, Producing For](media/tracker/risk-graph-ff-producing-for.png)
+> ![Screenshot of Dependency Tracker Risk Graph, Producing For view.](media/tracker/risk-graph-ff-producing-for.png)
 
 
 #### Filtered on a specific dependency
 
 You can drill down into specifics by choosing one of the dependencies. 
 
 > [!div class="mx-imgBorder"]  
-> ![Dependency Tracker Risk Graph, Producing For, Filtered on a dependency](media/tracker/risk-graph-ff-producing-for-filtered.png)
+> ![Screenshot of Dependency Tracker Risk Graph, Producing For, Filtered on a dependency.](media/tracker/risk-graph-ff-producing-for-filtered.png)
 
 
 <a id="configuration" /> 

docs/boards/extensions/epic-roadmap.md

@@ -10,7 +10,7 @@ ms.manager: mijacobs
 ms.author: kaelli
 author: KathrynEE
 monikerRange: '<= azure-devops'
-ms.date: 04/01/2022
+ms.date: 06/02/2022
 ---
 
 # View progress using the Epic Roadmap 
@@ -20,7 +20,7 @@ ms.date: 04/01/2022
 Similar to the Feature Timeline, the Epic Roadmap supports portfolio management. It provides a calendar view of a single epic and its child features. Within each epic roadmap view, you can drill down to see details at the feature and requirements level.  
 
 > [!div class="mx-imgBorder"]  
-> ![Epic Roadmap initial view](media/epic-roadmap/intro.png)
+> ![Screenshot of Epic Roadmap.](media/epic-roadmap/intro.png)
 > 
 > [!NOTE]   
 > The Feature Timeline and Epic Roadmap extension is not a supported feature of Azure Boards and therefore not supported by the product team. For questions, suggestions, or issues you have when using the extension, visit the extension page.  
@@ -102,14 +102,14 @@ You can access the Epic Roadmap from either your team's Kanban board or backlog.
 1. Choose **Epic Roadmap** and then choose the Epic you want to view. 
 
 	> [!div class="mx-imgBorder"]  
-	> ![Choose Epic Roadmap from Azure Boards](media/epic-roadmap/open-epic-roadmap.png)
+	> ![Screenshot of Choose Epic Roadmap from Azure Boards.](media/epic-roadmap/open-epic-roadmap.png)
 
 	If you don't see the **Epic Road** link, then the [Feature Timeline and Epic Roadmap](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.workitem-feature-timeline-extension) extension isn't installed or enabled. Check with your Project Collection Administrator to request to have it installed. To learn more, [Request and approve extensions](../../marketplace/request-extensions.md). 
 
 2. Choose the Epic you want to view from the drop-down menu. 
 
 	> [!div class="mx-imgBorder"]  
-	> ![Choose Epic from drop-down menu](media/epic-roadmap/choose-epic-drop-down-menu.png)
+	> ![Screenshot of Choose Epic from drop-down menu.](media/epic-roadmap/choose-epic-drop-down-menu.png)
 
 4. Customize your view. 
 
@@ -125,19 +125,19 @@ You can access the Epic Roadmap from either your team's Kanban board or backlog.
 1. To view the requirements linked to a feature, choose the  info :::image type="icon" source="../media/icons/info.png" border="false":::  icon for that feature. 
 
 	> [!div class="mx-imgBorder"]  
-	> ![Feature, Info icon](media/feature-timeline/drill-down-1.png)
+	> ![Screenshot of Feature, Info icon.](media/feature-timeline/drill-down-1.png)
 
 	A dialog opens showing the child items of the feature. 
 
 	> [!div class="mx-imgBorder"]  
-	> ![Feature Timeline controls](media/feature-timeline/drill-down-2.png)
+	> ![Screenshot of child items of the feature.](media/feature-timeline/drill-down-2.png)
 
 	The Start and End iterations are derived from the iteration paths assigned to the child work items. You can change those values by selecting new Start and End iterations from the drop-down path. 
 
 1. To view the dependency linked to a feature, choose the :::image type="icon" source="../media/icons/icon-links-tab-wi.png" border="false"::: link icon for that feature. 
 
 	> [!div class="mx-imgBorder"]  
-	> ![Epic Roadmap, Feature, linked icon](media/epic-roadmap/view-dependency.png)
+	> ![Screenshot of Epic Roadmap, Feature, linked icon.](media/epic-roadmap/view-dependency.png)
 
 ::: moniker range="azure-devops"