AzureStorageExplorer
AzureStorageExplorer copied to clipboard
A11y_Azure Tools Storage Explorer_Tables_Table Grid_Resize: On Applying resize resolution table section data is not completely visible.
Preflight Checklist
- [X] I have installed the latest version of Storage Explorer.
- [X] I have checked existing resources, including the troubleshooting guide and the release notes.
- [X] I have searched for similar issues.
Storage Explorer Version
1.32.1 (96)
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20231114.10
Platform
Windows
OS Version
Windows 11 Enterprise Insider Preview (23H2)
Bug Description
GitHub Tags:
#A11yMAS;#A11yTCS;#Win11;#DesktopApp;#A11ySev3;#BM_AzureToolsStorageExplorer_Win32_Dec2023;#Azure Tools Storage Explorer;#Resize;#WCAG1.4.4;#FTP;
Environment Details:
Application: Microsoft Azure Storage Explore version: 1.32.1 (96)
Pre-requisite:
Go to system setting ->display->scale->text size>200% and apply it. Alternatively: Go to system setting ->display->scale->custom scaling 200->sign out and sign in again.
Steps to Reproduce
- Launch Storage Explorer.
- TAB to "Open Connect dialog" pane and Sign in to Azure.
- TAB to "Manage Accounts" pane and Select the subscriptions you will use. Once selected, click on "Apply" button.
- TAB to "Tables" of the selected subscription and expand it.
- TAB to any data item and press ENTER on it.
- TAB to column headers present in table.
- Observe that On applying resize resolution table section data is completely visible to the user or not
Actual Experience
On Applying resize resolution table section data is not completely visible to the user.
Expected Experience
On Applying resize resolution table section data should be completely visible to the user.
Additional Context
User Impact:
Low vision users who uses resize for better visibility will miss the information present in table and not able to view the data present in table.
Verified the issue at Application: Microsoft Azure Storage Explore version: 1.33.1 (96) but issue is still repro'ing. Please find below attachment for reference.
A fix has been pushed to the UI components, but the package has not been updated yet. We will be making an update to that later, then the fix can be verified.