Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No visible marker provided that can indicate the field are mandatory for "Target database name" and "Network share path":A11y_[BM]SQL Migration extension for Azure Data Studio_Database backup_Network file share_Labels or Instructions #25919

Closed
Swati1700 opened this issue Sep 16, 2024 · 2 comments

Comments

@Swati1700
Copy link

Swati1700 commented Sep 16, 2024

"Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification."

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

GitHub Tags:

#A11yMAS; #A11yTCS; #Win11; #DesktopApp; #A11ySev2; #BM_SQL Migration extension for Azure Data Studio_Win32_AUG2024; #SQL Migration extension for Azure Data Studio; #WCAG3.3.2; #FTP; #Win32; #Labels or Instructions;

Environment Details:

Application Name: SQL Migration extension for Azure Data Studio
Microsoft Windows 11 version 23H2 (OS Build 22631.4037)
Version: 1.49.1 (user setup)
Commit: 2f696aa
Date: 2024-08-13T18:12:38.831Z
VS Code: 1.82.0
Electron: 25.9.8
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22631
Azure SQL Migration v1.4.8

Repro Steps:

  1. Install Azure data studio and open
  2. Tab till Extension press enter key and install Azure SQL Migration
  3. Tab till Respective server and right click
  4. Tab till manage and press enter key
  5. Tab till Azure SQL Migration and press enter key
  6. Tab till migrate to azure sql and press enter key andSaved session page will open
  7. Select start new session and give next ,Databases for assessment page will open
  8. Select the respective databases and give next ,Assessment results and recommendations page will open
  9. Select Azure SQL managed Instance/Virtual Machines from Azure SQL Target
  10. Tab till Get Azure recommendation and press enter,
  11. Get Azure Recommendation will open and select collect performance data now ,Browse folder and give start
  12. Tab till view/select and press enter ,select database and give next
  13. Azure SQL Target will open and give next, Migration mode page will open and select online.
  14. Tab till "My databse backups are on a network share" radio button and select it.
  15. Tab till "Next" button and press enter.
  16. Tab till "Target database name" and "Network share path" grid columns.
  17. Observe the fields are marked as mandatory visually.

Note: Similar issue is also reproducing in the below scenarios:
Migrate to azure sql - Azure Database Migration Service (Subscription combo box)
Migrate to azure sql- Database backup

Actual results:

No visible marker provided that can indicate the field are mandatory for "Target database name" and "Network share path".

Expected results:

Visible marker should be provided that can indicate the field are mandatory for "Target database name" and "Network share path".

User Impact:

The Users will get confused and will miss out the mandatory fields.

Attachments:

25919_A11y_.BM.SQL.Migration.extension.for.Azure.Data.Studio_Database.backup_Network.file.share_Labels.or.Instructions.webm

25919_A11y_ BM SQL Migration extension for Azure Data Studio_Database backup_Network file share_Labels or Instructions

@akshika898
Copy link
Contributor

akshika898 commented Oct 18, 2024

While reading through the issue i understand that we need the required indicator on

  1. subscription combo box
  2. target database name and network share path (Database backup on network share)
  3. What do we mean here by Similar issue in database backup?
    Does it refer to when Database Backups are on blob storage?
    Image

@Swati1700
Copy link
Author

Swati1700 commented Nov 25, 2024

#Closed;
Verified the issue in the environment Version: 1.50.0 (user setup)
Commit: 49c73a8
Date: 2024-11-17T22:41:05.327Z
VS Code: 1.82.0
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.26100
and issue is fixed. Hence closing the bug.
Image
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants