anthonydresser / testissues

0 stars 0 forks source link

A11y_SQLAzureDataStudio_Extension_Install-UninstallExtension_ScreenReader: Heading content not reading as heading by screen reader. #2642

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.”

!A11yWCAG2.1; !A11yTCS; !SQL Azure Data Studio; !DesktopApp; !MacOs; !Benchmark; !A11y_SQLAzureDataStudio; !A11ySev2; !MAS2.4.6; !MAS1.3.1; !VoiceOver;

Environment Details: Version: 1.16.0-insider Commit: 506c6a5 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: Screen reader: Voice Over MAS reference: MAS2.4.6, MAS1.3.1

Repro Steps: Launch Azure Data Studio. From the left menu, click the 'Extensions' icon to open the Extension Manager. Choose any extension from the library. Click the green 'Install' button to install. Launch Voice Over screen reader and navigate to the heading 'Admin pack for SQL Server'. Check if all headings are announced by screen reader.

Actual: Heading content is not announced by Voice Over as heading to screen reader users present at the top of the screen. "Admin pack for SQL Server".

Expected: Heading content should be announced as heading by Voice Over.

User Impact: Screen reader users might miss the heading content present on the screen.

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

MAS Reference: MAS 1.3.1 https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4} MAS 2.4.6 https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={0cf80872-800d-4643-90cf-0c1c3d3e6260}

Attachment link reference:

adstestbot[bot] commented 4 years ago

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