anthonydresser / testissues

0 stars 0 forks source link

A11y_SQLAzureDataStudio_NewServerGroup_AddServerGroup_Keyboard:Focus is not logical after cancel button #2508

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; !A11yMAS; !A11ySev1; !A11yTCS; !SQL Azure Data Studio; !Benchmark; !DesktopApp; !Win32; !MAS2.4.3; !Keyboard;

Environment Details: Application Name: Azure Data Studio Version: 1.16.0-insider Commit: 506c6a5e5f8423d3249670f55b1466b1980a5f03 Date: 2020-02-17T05:43:18.399Z VS Code: 1.42.0 Electron: 7.1.11 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Windows_NT x64 10.0.18363

Additional Details: MAS References:MAS2.4.3

Repro Steps:

  1. Launch Azure Data Studio.
  2. Select the Connections icon (if not already selected) from left bar.
  3. Hover over the 'Servers' header and select the 'New Server Group' icon.
  4. Navigate to Cancel button.

Actual: On navigating to the cancel button hit enter the next tab key focus is seen on the server icon in the left panel.

Same issue is observed in the following page: 1.Add new controller

Expected: Focus should be on the button "new server group" button that opened the dialog.

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: Keyboard users will not receive logical navigation sequence as well as the button that revelaed the content wil not be visible on first tab.

MAS Reference: MAS 2.4.3:https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={0de7fbe1-ad7e-48e5-bcbb-8d986691e2b9}

Attachment link for Reference : https://microsoft-my.sharepoint.com/:p:/g/personal/v-stfe_microsoft_com1/EYVbhknCcflElKIGotlEy7sBXmUBdB-ECkcV11QCZBe7hg?e=8Ea0Jb

adstestbot[bot] commented 4 years ago

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