search

anthonydresser / testissues

0 stars 0 forks source link

A11y_SQLAzureDataStudio_AddaSQLServerBigDataCluster-Controller_Addnewcontroller_Zoom: After zooming to 400% the content on the screen is not visible. #2489

Open adsbot[bot] opened 4 years ago

adsbot[bot] commented 4 years ago

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”

!A11y_SQLAzureDataStudio; !A11yWCAG2.1; !A11ySev1; !A11yTCS; !SQL Azure Data Studio; !Benchmark; !DesktopApp; !Win10; !Zoom; !MAS1.4.10;

Environment Details: Application Name: Azure Data Studio Version: 1.16.0-insider OS: Windows_NT x64 10.0.18363

Additional Details: MAS References:MAS1.4.10

Pre-requisite: Set display resolution to 1280x1024, then use DPI zoom to 400%. (Windows Settings > Display Settings > Scale and Layout)

Repro Steps:

  1. Launch Azure Data Studio application.
  2. Connect to server with windows credentials.
  3. Navigate to Connections from left menu.
  4. Select Add a SQL Server Big Data Clusters.
  5. Navigate to + button & hit enter.

Actual: The screen when opened is zoomed to 400% hence the data cannot be seen the labels of the edit box as well as the screen names.

Expected: All data needs to clealry visible on screen.

Recommendations: Refer below link which is repository of bug fixes code snippets: https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx

User Impact: Users will not be able to see data that is present on screen and know the purpose of the edit box present.

MAS Reference: MAS1.4.10 https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/Doc.aspx?sourcedoc=%7BE12828DF-B35C-4F4D-9289-1F932E19F8CF%7D&file=MAS%201.4.10%20%E2%80%93%20Reflow.docx&action=default&mobileredirect=true&cid=b7b7ec5a-4693-42e4-a071-94438648e8b3

Attachment link for Reference : https://microsoft-my.sharepoint.com/:p:/g/personal/v-stfe_microsoft_com1/EdxwK6TCeVpFlQaMwQGVs2IBt8vtjr6SMXUFUDp16ZDo-w?e=4B7PBF

adstestbot[bot] commented 4 years ago

Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: