microsoft / azure-tools-for-java

Azure tools for Java, including Azure Toolkits for Eclipse, IntelliJ and related projects.
Other
239 stars 158 forks source link

[WCAG2.1]A11y_Java Tooling for IntelliJ/Eclipse_Spark Submission_Screen Reader: Narrator/NVDA is reading the "Browse" button as "Open system file dialog to select artifact" button #4271

Closed soumyatippapuram closed 4 years ago

soumyatippapuram commented 4 years ago

Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier

GitHubTags: #A11yTCS; #A11yWCAG2.1; #DesktopApp; #Win10; #A11y_JavaToolingforIntelliJ/Eclipse-Benchmark; #MAS2.5.3; #ScreenReader; #NVDA; #Narrator; #JavatoolingforIntelliJ/Eclipse; #C+E-H; #LabelInName; #Benchmark; #A11ySev1; #A11y_JavaToolingforIntelliJ/Eclipse-WCAG2.1

Environment Details: Eclipse IDE for Enterprise Java Developers. Version: 2020-03 (4.15.0) Build id: 20200313-1211

Solution Installed: The Azure Toolkit for Eclipse 3.220, Scala IDE 4.7.x

OS Details: OS: Windows (Version 1903, Build: 18362.175)

Screen Reader: Narrator, NVDA

MAS Violated: MAS 2.5.3

Repro Steps: 1.Start Screen Reader. Open Java EE - Eclipse application 2.Install "Azure Toolkit for Eclipse" and "Scala Plug-ins" from Eclipse Marketplace 3.Tab till "File > New > Project" in the navigation bar and press enter 4.Tab till "HDInsight Project > Spark on HDInsight (Scala)" and select it. 5.Tab till "Next" button and press enter 6.Enter all the required details, tab till "Next" button and press enter 7.Tab till "Module Dependencies" tab and press enter 8.Tab till "Finish" button and press enter 9.In Project Explorer, expand the created Scala project right-click src, New-->Other and press enter 10.Tab till Scala Wizards, expand and select 'Scala Object' and press next 11.Open the created file and write any code 12.In Project Explorer view, open contextual menu and select "Submit Spark Application to HDInsight" 13.Tab till "Browse" button beside "Artifact from hard disk" radio button 14.Check if the screen reader is reading the "Browse" button properly

Actual Result: Narrator/NVDA is reading the "Browse" button as "Open system file dialog to select artifact" button

Expected Result: Narrator/NVDA should read the word "Browse" along with "Open system file dialog to select artifact" when the focus is on "Browser" button

User impact: Speech-input users will find it difficult to access the "Browse" button

MAS Reference: MAS 2.5.3

Bug_4271_Java Tooling_Spark Submission_Label in Name_NVDA

t-rufang commented 4 years ago

@soumyatippapuram This is a WCAG2.1 bug but it's not an external bug. And we plan to fix this bug before due date 6/30/2021. The question is do we need to add this bug to AAT document?

soumyatippapuram commented 4 years ago

@t-rufang yes, the details of the WCAG 2.1 bug needs to be documented in AAT

t-rufang commented 4 years ago

@soumyatippapuram Thanks for the reply. But I still have another concern, once the conformance document is generated, it can't be modified anymore. So how do we remove the record from the conformance doc when this issue is finally fixed before due date(June 1st 2021)?

soumyatippapuram commented 4 years ago

@t-rufang You can re-publish the Conformance Document once this bug is fixed.

vscjavaci commented 4 years ago

Track internal issue by AB#1749642