Pipeline run status indicators lack sufficient non‑color cues in Azure DevOps

Azure DevOps identifies pipeline run status through a combination of color-coded icons, geometric shapes, and textual labels. While the interface attempts to provide non-color cues, the consistency of these cues varies between the Classic Pipelines and the modern YAML Pipelines experiences.

Non-Color Cues Available

To determine if the status satisfies WCAG 2.1 SC 1.4.1 (Use of Color), look for the following elements in the UI:

• Geometric Shapes: Icons use distinct shapes to represent state—for example, a checkmark for success, an 'X' for failure, and a spinning circle or square for in-progress. This provides a primary visual distinction for users who cannot perceive color.
• Text Labels: In the primary 'Runs' list view, status is typically accompanied by explicit text (e.g., 'Succeeded', 'Failed', 'Canceled') placed adjacent to the icon.
• Tooltips: Hovering a mouse over a status icon generally triggers a tooltip that displays the status name in text.

ARIA Labels and Screen Reader Consistency

The implementation of ARIA labels is not universally consistent across all views of Azure DevOps.

• New Pipelines (YAML): Generally utilizes aria-label attributes on icons to allow screen readers to announce the state when the element receives focus.
• Classic Pipelines: Often relies on the adjacent text label. If the text is hidden or omitted in condensed views, screen readers may only encounter the icon as a generic image without a status context.
• Tooltip Limitations: A significant concern is that tooltips triggered by hover are often inaccessible to keyboard-only users or screen readers unless the underlying element is focusable and contains proper ARIA attributes.

Verification Steps

To verify if your specific environment meets accessibility requirements, perform these manual checks:

1. Open the pipeline run list and use the browser's Inspect tool (F12) on a status icon. Check for aria-label, title, or alt attributes that describe the status.
2. Navigate the page using the Tab key. If you can focus on the status icon but no text appears or is announced, the cue is inaccessible to keyboard users.
3. Enable a screen reader (like NVDA or VoiceOver) and confirm if the status is announced as a meaningful word rather than just "image" or "button".

Note: If you are experiencing a specific view where text is entirely missing, please specify if you are using the Classic Editor or YAML Pipelines.