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

[Accessibility]A11y_VSCode_ShowOpenedEditors_ScreenReader:Voiceover does not read the search results found after typing any command in editor. #52326

Closed
AccessibilityTestingTeam-TCS opened this issue Jun 19, 2018 · 4 comments
Assignees
Labels
a11ymas Issue from accessibility team *duplicate Issue identified as a duplicate of another issue(s) macos Issues with VS Code on MAC/OS X search Search widget and operation issues

Comments

@AccessibilityTestingTeam-TCS

Environment Details:
VSCode Version : 1.23.1
OS Version : MAC OS HighSierra10.13.5
Additional Details:
MAS Violated : MAS 1.3.1
ScreenReader Versions : VoiceOver
Repro Steps:
Launch VS Code while Voiceover is ON.
1.Navigate to welcome screen and beside opened editors pane at top(in middle pane)->Select More(…)->Select "Show Opened Editors" from dropdown.
2.Navigate to editor and search for any commands.
Actual:
Voiceover does not read the "No results found....." content which tells user the search result did not produce any valid result.
Expected:
JAWS /NVDA should read the "No results found...." content as soon as search is performed by user and no outputs are found.
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:
Screenreader users will not know about the empty search content and other meaningful information.When "No results...." content is read ,the users will then and there come to know about the search results output.
MAS Reference:
MAS 1.3.1 - https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Does this issue occur when all extensions are disabled?: Yes/No
Attachment for Reference:
EditorSearch.pptx

@AccessibilityTestingTeam-TCS AccessibilityTestingTeam-TCS changed the title [Accessibility]A11y_VSCode_ShowOpenedEditors_ScreenReader:NVDA does not read the search results found after typinng any command in editor. [Accessibility]A11y_VSCode_ShowOpenedEditors_ScreenReader:NVDA does not read the search results found after typing any command in editor. Jun 19, 2018
@vscodebot vscodebot bot added the search Search widget and operation issues label Jun 19, 2018
@alvinkiett84
Copy link

alvinkiett84 commented Jun 19, 2018 via email

@AccessibilityTestingTeam-TCS AccessibilityTestingTeam-TCS changed the title [Accessibility]A11y_VSCode_ShowOpenedEditors_ScreenReader:NVDA does not read the search results found after typing any command in editor. [Accessibility]A11y_VSCode_ShowOpenedEditors_ScreenReader:Voiceover does not read the search results found after typing any command in editor. Jun 20, 2018
@roblourens
Copy link
Member

roblourens commented Jun 20, 2018

Is this the same as #52325?

@isidorn
Copy link
Contributor

isidorn commented Jul 4, 2018

Dup of #51824

@isidorn isidorn closed this as completed Jul 4, 2018
@isidorn isidorn added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 4, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 18, 2018
@chrmarti chrmarti added the a11ymas Issue from accessibility team label Oct 2, 2018
@isidorn isidorn added macos Issues with VS Code on MAC/OS X windows VS Code on Windows issues and removed windows VS Code on Windows issues labels Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
a11ymas Issue from accessibility team *duplicate Issue identified as a duplicate of another issue(s) macos Issues with VS Code on MAC/OS X search Search widget and operation issues
Projects
None yet
Development

No branches or pull requests

5 participants