vscode-azurefunctions
vscode-azurefunctions copied to clipboard
microsoft
A11y_Azure Tools for VS Code_Azure Function_Select a runtime stack_Screenreader: Screenreader is announcing wrong names for the symbols.
GitHubTags:
#A11yMAS; #A11yTCS; #A11ySev3; #DesktopApp; #Azure Tools for VS Code; #BM_Azure Tools for VS Code_Win32_Apr22; #Win32; #FTP; #NVDA; #JAWS; #Screenreader; #WCAG1.3.1
Environment Details: Application Name: Visual Studio Code Services Windows Version: Windows 11
Repro Steps:
- Open Visual studio code
- Tab till extension button and search for "Azure Functions"
- Tab till install and and press enter now tab till the "Azure" button and press enter.
- Right click on any of the functions
- Tab navigate to "Create function app in azure" and hit enter.
- Enter a global unique name for new function app and hit enter.
- Select a runtime screen will appear.
- Tab navigate to "Change Azure function version".
- Turn on the JAWS.
- Check if the JAWS reads the symbol correctly or not.
Actual: Screenreader is announcing wrong names for "setting" symbol as "gear", "Add' symbol as "plus", "skip for now" symbol as "clock"
Note: Similar issue observed in NVDA.
Expected Result: Screenreader should announce correct names for the symbols.
Attachment
:
Could you please clarify what the issue here is? Should the symbols not be read or is it actually be read incorrectly? I can't discern exactly what your gif is trying to demonstrate.
Could you please give me a clear example of what the correct reading would be and what the incorrect reading currently is?
After discussing this further, I think that the issue here is that the icons are being read as plain text. From the listener's perspective, there is no difference between 🕑 and "clock"
Hi @nturinski , If those symbols are just for decorative purpose then screen reader should not announce anything related to it. Or if the symbol is conveying any information , then it should announce proper information . The Announcement of "Gear" for setting symbol and "Clock" for Skip for now, does not describe the symbols properly.
VS Code team has recently added a feature request that extensions should be able to specify accessibilityInformation for QuickPickItems. The implementation of this sort of feature should give us the flexibility we need to resolve issues like this one. Here is a link to the issue where this was first discussed: https://github.com/microsoft/vscode/issues/133169
Hi @MicroFish91 When can we expect this implementation will be done on the extension?
Hi @Ashutoshsahoo164 I am not sure yet. I can verify that they have added this feature request to their current backlog but they have not mentioned when they will prioritize this one. I can say that they are a very diligent team and release regularly so we on the extensions team will be on the lookout to implement once this feature drops. I know that's not a solid date, but I hope that helps some, thank you :)
@MicroFish91 The link for the issue which you gave is not similar to this issue. Sev3 bugs do not have any defined SLA. Product team can act as per their Convenience.
This one kind of fell off my radar. Not sure the best way to address this one to be honest. There are some icons we can migrate to within this list that might be more appropriately descriptive, but there are other icons we are using that don't really have good alternatives.
I dangled an upstream feature request here to see if perhaps we could eventually put in custom screen reader descriptions. If that's not feasible and there are not good icon alternatives, we will need to revisit and see if some of these icons should be removed entirely in our codebase 🤷
...TBD will revisit based on upstream feedback
Based on upstream feedback listed in my comment directly above, we are back to tracking against this upstream issue as it has been re-opened: https://github.com/microsoft/vscode/issues/133169