Docs accessibility sprint 2025 march oleks 3

oleks-k · Evergreen · commit 7e89b155dcbd · 2025-03-24T23:22:45.000Z
diff --git a/Packages/com.unity.render-pipelines.core/Documentation~/Look-Dev-Environment-Library.md b/Packages/com.unity.render-pipelines.core/Documentation~/Look-Dev-Environment-Library.md
@@ -4,7 +4,7 @@ An Environment Library is an Asset that contains a list of environments that you
 
 <a name="Creation"></a>
 
-![](Images/LookDevEnvironmentLibrary1.png)
+![Environment Library asset.](Images/LookDevEnvironmentLibrary1.png)
 
 ## Creating an Environment Library
 
@@ -26,13 +26,13 @@ To add, remove, or duplicate environments, use the toolbar at the bottom of the
 
 | **Button**                                                   | **Function**  | **Description**                                              |
 | ------------------------------------------------------------ | ------------- | ------------------------------------------------------------ |
-| ![](Images/LookDevEnvironmentLibrary2.png) | **Add**       | Click this button to add a new environment to the bottom of the list. |
-| ![](Images/LookDevEnvironmentLibrary3.png) | **Remove**    | Click this button to remove the environment currently selected. Note that the environment that you have selected is the one with the blue frame. |
-| ![](Images/LookDevEnvironmentLibrary4.png)                   | **Duplicate** | Click this button to duplicate the currently selected environment and add it as a new environment to the bottom of the list. |
+| ![This button adds a new environment to the bottom of the list.](Images/LookDevEnvironmentLibrary2.png) | **Add**       | Click this button to add a new environment to the bottom of the list. |
+| ![This button removes the currently selected environment.](Images/LookDevEnvironmentLibrary3.png) | **Remove**    | Click this button to remove the environment currently selected. Note that the environment that you have selected is the one with the blue frame. |
+| ![This button duplicates the currently selected environment.](Images/LookDevEnvironmentLibrary4.png)                   | **Duplicate** | Click this button to duplicate the currently selected environment and add it as a new environment to the bottom of the list. |
 
 ## Properties
 
-![](Images/LookDevEnvironmentLibrary5.png)
+![Environment Library properties](Images/LookDevEnvironmentLibrary5.png)
 
 | **Property**        | **Description**                                              |
 | ------------------- | ------------------------------------------------------------ |
diff --git a/Packages/com.unity.render-pipelines.core/Documentation~/Look-Dev.md b/Packages/com.unity.render-pipelines.core/Documentation~/Look-Dev.md
@@ -46,15 +46,15 @@ Use the toolbar in the top-left of the window to change which viewing mode Look
 
 ### Single viewport
 
-![](Images/LookDev1.png)
+![Buttons for switching between viewports 1 and 2.](Images/LookDev1.png)
 
 By default, Look Dev displays a single viewport which contains the Prefab or GameObject you are working with. If you are in another viewing mode, you can click either the number **1** or number **2** button to go back to single view. Each button corresponds to a viewport in Look Dev. Select button **1** to use viewport 1, and button 2 to use viewport **2**.
 
 <a name="MultiView"></a>
 
 ### Multi-viewport
 
-![](Images/LookDev2.png)
+![Buttons for changing the multi-viewport mode.](Images/LookDev2.png)
 
 Use multiple viewports to compare different environments and settings for the same Asset. You can arrange viewports:
 
@@ -73,23 +73,21 @@ When using multiple viewports, it only makes sense to compare different Prefabs
 
 Vertical and horizontal side-by-side viewports show an identical view of your Asset.
 
-![](Images/LookDev3.png)
+![Vertical side-by-side viewport view.](Images/LookDev3.png)
 
 ##### Split-screen
 
 In a split-screen view, there is a red/blue manipulation Gizmo that separates the two viewports. For information on how to use this Gizmo, see [Using the manipulation Gizmo](#ManipulationGizmo).
 
-![](Images/LookDev4.png)
+![Split-screen viewport view.](Images/LookDev4.png)
 
 #### Multi-viewport Camera
 
 By default, Look Dev synchronizes the camera movement for both views. To decouple the Cameras from one another, and manipulate them independently, click the **Synchronized Cameras** button in-between the two numbered Camera buttons.
 
-![](Images/LookDev5.png)
-
 To align the cameras with each other, or reset them, click on the drop-down arrow next to the viewport **2** icon:
 
-![](Images/LookDev6.png)
+![Drop-down options of multi-viewport cameras.](Images/LookDev6.png)
 
 <a name="ManipulationGizmo"></a>
 
@@ -101,13 +99,11 @@ The manipulation Gizmo represents the separation plane between the two viewports
 
 To move the separator, click and drag the straight line of the Gizmo to the location you want.
 
-![](Images/LookDev7.png)
-
 #### Changing the orientation and length
 
 To change the orientation and length of the manipulator Gizmo, click and drag the circle at either end of the manipulator. Changing the length of the Gizmo lets you  set the orientation and [blending](#Blending) values more precisely.
 
-![](Images/LookDev8.png))
+![Click and drag the circle at either end of the gizmo to change its orientation and length.](Images/LookDev8.png)
 
 #### Changing the split in increments
 
@@ -121,7 +117,7 @@ The central white circle on the separator allows you to blend between the two vi
 
 The white circle automatically snaps back into the center when you drag it back. This helps you get back to the default blending value quickly.
 
-![](Images/LookDev9.png)
+![The white circle on the separator lets you change the blending behavior.](Images/LookDev9.png)
 
 ### HDRI environments in Look Dev
 
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/Anti-Aliasing.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/Anti-Aliasing.md
@@ -4,7 +4,7 @@
 
 This is most obvious if you compare the original and digital signals for an audio source at its highest frequencies, or a visual source in its smallest details. Regular signal processing uses the [Nyquist rate](Glossary.md#NyquistRate) to avoid aliasing, however it's not practical for image rendering because it's resource intensive.
 
-![](Images/MSAA1.png)
+![Example of aliasing happening during the rasterization process.](Images/MSAA1.png)
 
 An example of the rasterization process creating some aliasing.
 
@@ -96,18 +96,18 @@ When you enable MSAA in your Unity Project, you must also enable it for your Cam
 
 Increasing the MSAA Sample Count produces smoother antialiasing, at the cost of performance. Here are some visual examples showing the effect of the different MSAA Sample Counts:
 
-![](Images/MSAA3.png)
+![Rendered image sample with MSAA Sample Count set to None.](Images/MSAA3.png)
 
 MSAA Sample Count set to None.
 
-![](Images/MSAA4.png)
+![Rendered image sample with MSAA Sample Count set to MSAA 2X.](Images/MSAA4.png)
 
 MSAA Sample Count set to MSAA 2X.
 
-![](Images/MSAA5.png)
+![Rendered image sample with MSAA Sample Count set to MSAA 4X.](Images/MSAA5.png)
 
 MSAA Sample Count set to MSAA 4X.
 
-![](Images/MSAA6.png)
+![Rendered image sample with MSAA Sample Count set to MSAA 8X.](Images/MSAA6.png)
 
 MSAA Sample Count set to MSAA 8X.
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/LUT-Authoring-Photoshop.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/LUT-Authoring-Photoshop.md
@@ -19,7 +19,7 @@ Export the current [Camera](hdrp-camera-component-reference.md)'s view to a log-
 2. Select **Edit** > **Rendering** > **Render Selected HDRP Camera to Log EXR** **(**or press **Ctrl+Shift+Alt+E)**.
 3. Save the EXR file.
 
-![](Images/LUTAuthoringPhototshop1.png)
+![Camera view before applying LUT effect.](Images/LUTAuthoringPhototshop1.png)
 
 After you export the EXR file, transform the data from the format that Unity uses (Alexa LogC El.1000) to Linear RGB space, so that external software can use it. To do this, HDRP provides a set of ready-to-use transform LUTs. To get them:
 
@@ -32,21 +32,21 @@ After you export the EXR file, transform the data from the format that Unity use
 
 Import the EXR file into Photoshop. Because it's a raw log-encoded file, it appears washed-out.
 
-![](Images/LUTAuthoringPhototshop2.png)
+![EXR file imported in Photoshop.](Images/LUTAuthoringPhototshop2.png)
 
 Add a non-destructive **Color Lookup** adjustment layer to your image (menu: **Layer** > **New Adjustment Layer** > **Color Lookup…**). Then, in the new layer's **Properties**:
 
 - Set **Data Order** to **RGB**.
 - Set **Table Order** to **BGR**.
 - In the **3DLUT File** drop-down, select **Load 3D LUT…** and select the Unity Log To Linear file to transform the LUT to a usable color space. This is in your Unity Project folder at Assets/HDRP Sample Content/Post-processing/Cube LUTs/.
 
-![](Images/LUTAuthoringPhototshop3.png)
+![Example image with the LUT file from Unity applied to it.](Images/LUTAuthoringPhototshop3.png)
 
 ## Step 4: Apply color grading
 
 You can now start grading your image. Make sure you only do global color operations through the use of non-destructive adjustment layers. LUTs can't store local operators or any filters that affect neighboring pixels (such as blur), so these create visual artifacts. Place all the adjustment layers on top of the **Color Lookup** layer, unless you intend to grade directly on the Log input.
 
-![](Images/LUTAuthoringPhototshop4.png)
+![Example image with color grading applied in Photoshop.](Images/LUTAuthoringPhototshop4.png)
 
 ## Step 5: Export your work as a CUBE file
 
@@ -66,6 +66,6 @@ Unity automatically interprets the CUBE file as a usable Texture3D Asset. You ca
 4. Assign your CUBE Texture to the **Lookup Texture** property.
 5. Change the **Contribution** to set how much the **Lookup Texture** contributes to the Scene.
 
-![](Images/LUTAuthoringPhototshop5.png)
+![Unity scene with the Tonemapping effect that uses a lookup texture created in Photoshop.](Images/LUTAuthoringPhototshop5.png)
 
 You can continue to color grade in Photoshop and override the previously saved CUBE file. Unity automatically updates the grading in the Scene with your changes.
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/LUT-Authoring-Resolve.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/LUT-Authoring-Resolve.md
@@ -19,7 +19,7 @@ Export the current [Camera](hdrp-camera-component-reference.md)'s view to a log-
 2. Select **Edit** > **Rendering** > **Render Selected HDRP Camera to Log EXR** **(**or press **Ctrl+Shift+Alt+E)**.
 3. Save the EXR file.
 
-![](Images/LUTAuthoringResolve1.png)
+![Camera view before applying LUT effect.](Images/LUTAuthoringResolve1.png)
 
 After you export the EXR file, transform the data from the format that Unity uses (Alexa LogC El.1000) to Linear RGB space, so that external software can use it. To do this, HDRP provides a set of ready-to-use transform LUTs. To get them:
 
@@ -47,13 +47,13 @@ Now import the EXR into Resolve and apply the **Unity Log To Linear r1** LUT to
 2. In the context menu, select **3D Lut**.
 3. Select the **Unity Log To Linear r1** LUT.
 
-![](Images/LUTAuthoringResolve2.png)
+![Color settings in the DaVinci Resolve editor.](Images/LUTAuthoringResolve2.png)
 
 ## Step 4: Apply color grading
 
 You can now start grading your image. Make sure you only do global color operations because LUTs can't store local operators or any filters that affect neighboring pixels (such as blur or sharpen).
 
-![](Images/LUTAuthoringResolve3.png)
+![Fame in the video editor with LUT color grading.](Images/LUTAuthoringResolve3.png)
 
 ## Step 5: Export your work as a CUBE file
 
@@ -73,6 +73,6 @@ Unity automatically interprets the CUBE file as a usable Texture3D Asset. You ca
 4. Assign your CUBE Texture to the **Lookup Texture** property.
 5. Change the **Contribution** to set how much the **Lookup Texture** contributes to the Scene.
 
-![](Images/LUTAuthoringResolve4.png)
+![Using the CUBE file as a color lookup texture in Unity.](Images/LUTAuthoringResolve4.png)
 
 You can continue to color grade in Resolve and override the previously saved CUBE file. Unity automatically updates the grading in the Scene with your changes.
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/Override-Screen-Space-GI.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/Override-Screen-Space-GI.md
@@ -6,7 +6,7 @@ HDRP implements [ray-traced global illumination](Ray-Traced-Global-Illumination.
 
 SSGI and RTGI replace all [lightmap](https://docs.unity3d.com/Manual/Lightmapping.html) and [Light Probe](https://docs.unity3d.com/Manual/LightProbes.html) data. If you enable this override on a Volume that affects the Camera, Light Probes and the ambient probe stop contributing to lighting for GameObjects.
 
-![](Images/HDRPFeatures-SSGI.png)
+![A sample scene rendered with SSGI.](Images/HDRPFeatures-SSGI.png)
 
 ## Enable Screen Space Global Illumination
 [!include[](Snippets/Volume-Override-Enable-Override.md)]
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/Post-Processing-Channel-Mixer.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/Post-Processing-Channel-Mixer.md
@@ -13,7 +13,7 @@ The Channel Mixer effect modifies the influence of each input color channel on t
 
 ## Properties
 
-![](Images/Post-processingChannelMixer1.png)
+The Channel Mixer component has the following properties.
 
 ### Output channels
 
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/Post-Processing-Tonemapping.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/Post-Processing-Tonemapping.md
@@ -15,7 +15,7 @@ To use Tonemapping, refer to [High Dynamic Range (HDR) and tonemapping](HDR-Outp
 
 ## Properties
 
-![](Images/Post-processingTonemapping1.png)
+![The tonemapping component properties.](Images/Post-processingTonemapping1.png)
 
 | **Property**          | **Description**                                              |
 | --------------------- | ------------------------------------------------------------ |
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/Ray-Traced-Ambient-Occlusion.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/Ray-Traced-Ambient-Occlusion.md
@@ -2,11 +2,11 @@
 
 Ray-Traced Ambient Occlusion is a ray tracing feature in the High Definition Render Pipeline (HDRP). It is an alternative to HDRP's s [screen space ambient occlusion](Override-Ambient-Occlusion.md), with a more accurate ray-traced solution that can use off-screen data.
 
-![](Images/RayTracedAmbientOcclusion1.png)
+![An example of a screen space ambient occlusion texture.](Images/RayTracedAmbientOcclusion1.png)
 
 **Screen space ambient occlusion**
 
-![](Images/RayTracedAmbientOcclusion2.png)
+![An example of a ray-traced ambient occlusion texture.](Images/RayTracedAmbientOcclusion2.png)
 
 **Ray-traced ambient occlusion**
 
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/index.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/index.md
@@ -1,6 +1,6 @@
 # High Definition Render Pipeline overview
 
-![](Images/Index1Main.png)
+![A sample scene rendered with the High Definition Render Pipeline.](Images/Index1Main.png)
 
 The High Definition Render Pipeline (HDRP) is a high-fidelity Scriptable Render Pipeline built by Unity to target modern (Compute Shader compatible) platforms.
 
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/probevolumes-concept.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/probevolumes-concept.md
@@ -26,7 +26,7 @@ Adaptive Probe Volumes have the following advantages:
 ![Two comparison scenes of a red car model. The left scene uses Light Probe Groups, so each part of the car is a different shade of red. The right scene uses Adaptive Probe Volumes, so each part of the car is the same shade of red. ](Images/probevolumes-per-pixel.png)<br/>
 The car model is made up of separate GameObjects. The left scene uses Light Probe Groups, which use per-object lighting, so each part of the car samples a single blended probe value. The right scene uses Adaptive Probe Volumes, which use per-pixel lighting, so each part of the car samples its nearest probes. This image uses the ArchVizPRO Photostudio HDRP asset from the Unity Asset Store.
 
-![](Images/probevolumes-reflection-probe-normalization.png)<br/>
+![Left: Reflection Probe Normalization is disabled. Right: Reflection Probe Normalization is enabled.](Images/probevolumes-reflection-probe-normalization.png)<br/>
 In the left scene, Reflection Probe Normalization is disabled. In the right scene, Reflection Probe Normalization is enabled, and there's less specular light leaking on the kitchen cabinet. This image uses the ArchVizPRO Interior Vol.5 HDRP asset from the Unity Asset Store.
 
 Adaptive Probe Volumes have the following limitations:
@@ -42,7 +42,7 @@ HDRP uses bricks with different sizes to match the amount of geometry in differe
 
 The default Light Probe spacing is 1, 3, 9, or 27 m.
 
-![](Images/probevolumes-debug-displayprobebricks1.PNG)<br/>
+![Purple volumes contain Light Probes spaced 1 meter apart. Large blue bricks contain Light Probes spaced 3 meters apart.](Images/probevolumes-debug-displayprobebricks1.PNG)<br/>
 In this screenshot from the Rendering Debugger, the small purple bricks contain Light Probes spaced 1 meter apart, to capture data from high-geometry areas. The large blue bricks contain Light Probes spaced 3 meters apart, to capture data from areas with less geometry.
 
 Each pixel of a GameObject samples lighting data from the eight closest Light Probes around it.
diff --git a/Packages/com.unity.render-pipelines.high-definition/Documentation~/snippets/tracing-modes.md b/Packages/com.unity.render-pipelines.high-definition/Documentation~/snippets/tracing-modes.md
@@ -14,15 +14,15 @@ In Mixed tracing mode, HDRP processes screen-space ray marching in the GBuffer.
 
 In Mixed tracing mode, HDRP still uses ray tracing for any geometry inside the ray tracing acceleration structure, regardless of whether vertex animation or decals modify the geometry's surface. This means if HDRP fails to intersect the on-screen deformed geometry, it intersects the original mesh inside in the ray tracing acceleration structure. This may cause visual discrepancies between what you see and what you expect. For example, the following Scene contains a cliff that uses mesh deformation.
 
-![](../Images/mixed-tracing-mixed.png)
+![Example scene contains a cliff mesh that uses mesh deformation.](../Images/mixed-tracing-mixed.png)
 
 In this Scene, Mixed mode can include reflections for the opaque leaf particles, the white decal, and GameObjects that aren't visible in the cliff face's non-deformed geometry.
 
-![](../Images/mixed-tracing-ray-traced.png)
+![Reflections in the water show elements that are not visible on the cliff surface.](../Images/mixed-tracing-ray-traced.png)
 
 Reflection rays intersect with the original, non-deformed cliff face geometry. This means the rays can still be affected by the bush behind the rock. To view the Scene from the perspective of the ray tracing mode, refer to the following image.
 
-![](../Images/mixed-tracing-ray-traced-no-deform.png)
+![The scene rendered using ray tracing. The reflections match the cliff surface.](../Images/mixed-tracing-ray-traced-no-deform.png)
 
 This image shows the elements of the Scene that ray tracing takes into account. The non-deformed cliff face geometry reveals the bushes behind the rocks.
 
