Programmatic name is not given for "Delete" button: A11y_Azure Tools Storage Explorer_Manage Stored Access Policies_Devtools

[kapilvaishna]

Preflight Checklist

• I have installed the latest version of Storage Explorer.
• I have checked existing resources, including the troubleshooting guide and the release notes.
• I have searched for similar issues.

Storage Explorer Version

1.36.2

Architecture

x64

Platform

Windows

OS Version

Windows 11

GitHub Tags:

#A11yMAS; #A11yTCS; #Win32; #DesktopApp; #A11ySev2; #BM_AzureToolsStorageExplorer_Win32_Dec2024; #Azure Tools Storage Explorer; #Devtools; #WCAG4.1.2; #FTP;

Environment Details:

Application: Microsoft azure storage explorer
Version: 1.36.2
OS: Windows 11 Enterprise 24H2
Build: 26100.2605

Repro Steps

1. Launch Azure Storage Explorer application.
2. TAB till "Account Management" in left Navigation and press ENTER key.
3. TAB till any "Subsection" for example 'azure tools Manual testing 1' and select it.
4. TAB till "Open explorer" button and press ENTER key
5. "Explorer" section will open. TAB till selected subscription and expand it
6. TAB till storage account and expand it.
7. TAB till any storage account and expand it.
8. TAB till "Blob Containers" and press ENTER key to expand it.
9. TAB till any "Blob container" and press ENTER key to select it now right click and press down arrow key to "Mange stored access polices" and press ENTER key.
10. TAB till "Add" button and press ENTER key.
11. TAB till "Delete" button and inspect it
12. Observe that Programmatic name is not given for "Delete" button.

Actual Experience

Programmatic name is not given for "Delete" button

Expected Experience

Programmatic name should be given for "Delete" button.

User impact

Speech input and screen reader user will face difficulty because screen reader will announce as button only.

Attachment

[InduPriya1805]

rev:inse

[craxal]

@kapilvaishna Fix is ready for validation.

[kapilvaishna]

@craxal issue is repro in build 1.37.0.(104). PFA for reference

[craxal]

@kapilvaishna Sorry, I forgot to send you a link to the new build. The build number you should have should be at least 20250128.2 or later. In the future, can you please report the build number that you test on?