Alt text examples

These examples of good alt text for various image types enables screen reader users to understand images as effectively as those who can see them.

Good alt text describes an image so that a user who uses a screen reader can reach the same understanding as a user who can perceive the image visually.

The following examples show what good surrounding text and alt text can look like for different types of images.

Good alt text enables screen reader users to understand images as effectively as those who can see them, with examples provided for various image types. For general guidelines about using images accessibly, see Using images with accessibility.

Screenshot of full-width UI

This example shows a screenshot of the full width of the UI and its surrounding text:

An uploaded package can have the following possible statuses: approved, installed, rejected, vetting, and app validation failed to complete. When the package is uploaded successfully, the package and its status appear on the Uploaded Apps page in Splunk Web. The app version appears only when the package passes all AppInspect checks and is approved. The following screenshot shows an example of the Uploaded Apps page:

Several uploaded app packages in a table with their names and statuses. Approved and installed packages include app versions, but packages with rejected, vetting, and failed statuses do not.

Simple flow diagram

This example shows a flow diagram with its surrounding text:

To plan a Splunk app for Splunk Cloud Platform or Splunk Enterprise, start by gathering the requirements of your app and understanding your data.
Diagram of the Splunk app lifecycle, starting with the planning phase, then the develop phase, and finally the release and maintain phase.

Simple search process diagram

This example shows a search process diagram and its surrounding text:

In a typical distributed search process, there are 2 search processing phases: a map phase and a reduce phase. The map phase takes place across the indexers in your deployment. In the map phase, the indexers locate event data that matches the search and sorts it into field-value pairs. When the map phase is complete, indexers send the results to the search head for the reduce phase. During the reduce phase, the search heads process the results through the commands in your search and aggregate them to produce a final result set.

The following diagram illustrates the standard 2-phase distributed search process.

A standard two-phase search process, described before the image, in the section "Overview of parallel reduce search processing".

Complex cluster diagram

This example shows a diagram and its surrounding text:

You can use Splunk Phantom on-premises or in Amazon Web Services to monitor and automate responses to security issues. Splunk Phantom uses a PostgreSQL database to store information about incidents or cases, a file share to save relevant items in a vault, and a Splunk Cloud Platform or Splunk Enterprise deployment. You can choose either a limited, internal deployment that runs without a user interface or a fully featured deployment that's external from Splunk Phantom.

In order to horizontally scale Splunk Phantom to handle larger workloads, you can deploy Splunk Phantom as a cluster, which consists of three or more instances of Splunk Phantom that share all of the resources previously mentioned.

This diagram shows an example of a Splunk Phantom cluster with the connections marked:

The Splunk Phantom web interface connects to a load balancer, which connects to three Splunk Phantom cluster nodes. The nodes connect to a PostgreSQL database, a file share, and a Splunk platform deployment.

GIF

This example shows a GIF with its surrounding text. The alt text contains a detailed description of what happens during the animation:

The following animation shows how to add a Flow Model and launch the Explorer:
From the home page, the user adds a new Flow Model. A pop-up message appears, and the user enters a name and base search for the Flow Model and selects Save. In the Flow Model editor, the user selects "customer ID" and "order_id" under Correlation IDs, "action" under Step, and "country" under Attributes, then selects Preview. The Preview page shows a flowchart of steps, starting with "New Account Created" and ending in "Purchased Game".

Inline image

This example shows an icon that users must select as part of a step in a task. The alt text contains the name or function of the icon.

Select the settings icon (Settings) to show a list of settings.