Fix image alt texts for accessibility in deep-dive #7 and #9 articles

docs/en/Community-Articles/2026-06-18-deep-dive-7-scopes/post.md

@@ -29,7 +29,7 @@ For me, that changes the feeling of using an AI agent. It is no longer "here is
 
 An AI Scope **restricts which directories the agent can access during a session**.
 
-![](auth-identity-scope.png)
+![Auth and Identity scope configuration in ABP Studio](auth-identity-scope.png)
 
 Depending on the task, a scope can include:
 
@@ -56,7 +56,7 @@ The first message of a session locks the configuration that affects the system p
 
 That matters when multiple sessions are active.
 
-![](selected-scope.png)
+![Selected AI scope shown in the agent session panel](selected-scope.png)
 
 Imagine I have one session working on a Catalog module and another session answering questions about the whole solution. Those sessions should not accidentally share a changing boundary. Each one should keep the scope it started with.
 
@@ -114,7 +114,7 @@ Which parts of the system should stay out of this session?
 - Scopes define **where** the agent can work.
 - Workflows define **what deterministic actions** should happen around that work.
 
-![](scopes-openning.png)
+![ABP AI Coding Agent panel showing scopes and workflows combined](scopes-openning.png)
 
 That combination is powerful. For example, I can scope the agent to the `Catalog` module and use a workflow that builds the affected package, regenerates proxies if contracts changed, and restarts the related application.
 

docs/en/Community-Articles/2026-06-18-deep-dive-9-workflows/post.md

@@ -16,7 +16,7 @@ When I work alone, I can do those steps manually. When I work with an AI coding
 
 That is the point of **ABP Studio AI Agent Workflows**.
 
-![](workflow.jpg)
+![ABP Studio AI Agent Workflows overview](workflow.jpg)
 
 Workflows let me define repeatable actions around an agent run. The model can focus on the ambiguous part, understanding the requirement and changing the code, while ABP Studio handles the deterministic parts that should happen before or after the work.
 
@@ -30,7 +30,7 @@ If the team always builds a package after an application service change, that sh
 
 Workflows give ABP Studio a place to encode those repeatable steps.
 
-![workflows-openning](workflows-openning.png)
+![Opening the workflow settings panel in ABP Studio](workflows-openning.png)
 
 ![ABP AI Agent workflow settings](workflow-settings.png)
 
@@ -45,7 +45,7 @@ and restart the app, and also add a migration if needed.
 
 I can configure the workflow once and let the agent session carry that context.
 
-![](sample-workflow-1.png)
+![Sample ABP AI Agent workflow configuration](sample-workflow-1.png)
 
 That makes the prompt cleaner:
 
@@ -98,7 +98,7 @@ A generic coding tool can run shell commands, and that is useful. But ABP Studio
 
 Workflows can be personal or shared.
 
-![](shared-with-team.png)
+![Sharing an ABP AI Agent workflow with the team via run profile](shared-with-team.png)
 
 - A **personal workflow** is stored locally under the solution workspace. It is useful for my own development habits. Maybe I like restarting a specific app after each agent turn. Maybe I have a local task that only makes sense on my machine.
 - A **shared workflow** is stored with the active run profile. That makes it suitable for source control and team usage.