anthonydresser / testissues

0 stars 0 forks source link

A11y_AzureDataStudio(Schema,Dacpac,Backup)_ Deploy Dacpac Settings_Screenreader: NVDA is not announcing the radio buttons of Target Database. #1592

Open adsbot[bot] opened 5 years ago

adsbot[bot] commented 5 years ago

Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.” Environment Details: Application Name: Azure Data Studio Application Version: 1.10.0-insider (user setup) Commit: 1ff9a2ec4c7b88be01666bdd470bbbb4ab95716e Date: 2019-08-09T07:49:00.254Z VS Code 1.37.0 Electron: 4.2.7 Chrome: 69.0.3497.128 Node.js: 10.11.0 V8: 6.9.427.31-electron.0 OS: Windows_NT x64 10.0.18362

Additional Details: Tools Name: Accessibility insight tool MAS References: MAS1.3.1

Repro Steps:

  1. Launch Azure Data Studio application.
  2. Connect to server with windows credentials.
  3. Navigate to Extensions from left menu.
  4. Search & install Dacpac extension.
  5. Navigate to Connections from left menu.
  6. Expand the server connected in step 2.
  7. Right click an on prem database and select Data-tier application wizard from Context menu.
  8. Select first radio button.
  9. Launch NVDA.
  10. Navigate till next button & hit enter.
  11. Navigate up to radio buttons of Target database and observed that NVDA is announcing the Radio buttons properly.

Actual: NVDA is announcing the radio buttons like upgrade existing database new database row 1 column 1 radio button checked 1 of 2.

Expected: NVDA should announce the radio buttons like Upgrade Existing Database radio button checked 1 of 2, New database radio button checked 2 of 2.

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: Screen reader users will face difficulty to understand radio buttons properly.

MAS Reference:

MAS 1.3.1- https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}

adstestbot[bot] commented 5 years ago

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