diff --git a/docs/get-started.md b/docs/get-started.md
index 29afe92b..4d5671e5 100644
--- a/docs/get-started.md
+++ b/docs/get-started.md
@@ -27,7 +27,7 @@ import TabItem from '@theme/TabItem';
 Aiven provides managed open source services for streaming, storing and analyzing data on all major clouds.
 All services run reliably and securely in the clouds of your choice, are observable, and can easily be integrated with each other and with external 3rd party tools.
 
-<img src={Overview} className="centered" alt="" width="54%" />
+<img src={Overview} className="centered" alt="Illustration of the platform" width="54%" />
 
 ## Discover the Aiven platform
 
diff --git a/docs/platform/howto/use-aws-privatelinks.md b/docs/platform/howto/use-aws-privatelinks.md
index 1dfe9fbf..add10042 100644
--- a/docs/platform/howto/use-aws-privatelinks.md
+++ b/docs/platform/howto/use-aws-privatelinks.md
@@ -164,7 +164,7 @@ AWS PrivateLink is not supported in:
     As a result, PrivateLink connection details are added to the **Connection information** section on the service
     <ConsoleLabel name="overview"/>.
 
-    <img src={AivenConsolePrivateLinkConfiguration} className="image"/>
+    <img src={AivenConsolePrivateLinkConfiguration} className="image" alt="Screenshot of the configuration"/>
 
     It takes a couple of minutes before connectivity is available after
     you enable a service component. This is because AWS requires an AWS
diff --git a/docs/products/kafka/concepts/upgrade-procedure.md b/docs/products/kafka/concepts/upgrade-procedure.md
index a3075182..9d261873 100644
--- a/docs/products/kafka/concepts/upgrade-procedure.md
+++ b/docs/products/kafka/concepts/upgrade-procedure.md
@@ -25,7 +25,7 @@ This example demonstrates the steps in the automated upgrade procedure for
 a 3-node Apache Kafka service, visualized below:
 <!-- vale on -->
 
-<img src={MyImg} className="centered" alt="" width="65%" />
+<img src={MyImg} className="centered" alt="3-node Kafka service" width="60%" />
 
 During an upgrade procedure:
 
@@ -40,7 +40,7 @@ During an upgrade procedure:
 1. **Transfer data and leadership:** The partition data and leadership are transferred
    to new nodes.
 
-    <img src={MyImg2} className="centered" alt="" width="65%" />
+    <img src={MyImg2} className="centered" alt="Kafka cluster illustration" width="65%" />
 
     :::warning
     This step is CPU intensive due to the additional data movement
@@ -58,7 +58,7 @@ During an upgrade procedure:
 1. **Complete process**: The process is completed once the last old node has been
   removed from the cluster.
 
-    <img src={MyImg3} className="centered" alt="" width="65%" />
+    <img src={MyImg3} className="centered" alt="Kafka cluster new node illustration" width="65%" />
 
 ## No downtime during upgrade