No Accessibility ID locators for UI elements - needed for UI tests #4179

Open
opened 2026-01-30 23:40:15 +00:00 by claunia · 0 comments
Owner

Originally created by @hassanuz on GitHub (Sep 30, 2019).

Originally assigned to: @carlos-zamora on GitHub.

Environment

Windows build number: 1903 (Build 18890)
Windows Terminal version (if applicable): N/A 

Any other software? Inspect.exe and UI Recorder to identify UI elements.

Steps to reproduce

  1. Launch Terminal
  2. Launch Inspect or UI Recorder
  3. Attempt to locate Accessibility/Automation ID for the Terminal Tab Elements (big + sign and Down Arrow ˅ sign, and the close tab little x sign)

Expected behavior

Inspect.exe is able to recognize Accessibility Attributes in the top bar, and WinAppDriver is able to automate against them.

Actual behavior

No automation ID attributes being picked up via Inspect.

Originally created by @hassanuz on GitHub (Sep 30, 2019). Originally assigned to: @carlos-zamora on GitHub. # Environment ```none Windows build number: 1903 (Build 18890) Windows Terminal version (if applicable): N/A Any other software? Inspect.exe and UI Recorder to identify UI elements. ``` # Steps to reproduce 1. Launch Terminal 2. Launch Inspect or [UI Recorder](https://github.com/microsoft/WinAppDriver/releases/tag/UIR-v1.1) 3. Attempt to locate Accessibility/Automation ID for the Terminal Tab Elements (big **+** sign and Down Arrow **˅** sign, and the close tab little **x** sign) # Expected behavior Inspect.exe is able to recognize Accessibility Attributes in the top bar, and WinAppDriver is able to automate against them. # Actual behavior No automation ID attributes being picked up via Inspect.
claunia added the Resolution-ExternalResolution-Duplicate labels 2026-01-30 23:40:15 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4179