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.

Sign up for GitHub

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

Jump to bottom

[General Question] [NumericUpDown] The Name must not include the same test as the control type and LocalizedControlType #618

Closed
v-lga-hub opened this issue Oct 24, 2019 · 6 comments
Closed

[General Question] [NumericUpDown] The Name must not include the same test as the control type and LocalizedControlType #618

v-lga-hub opened this issue Oct 24, 2019 · 6 comments
Assignees
@v-lga-hub
Labels
status: needs author feedback This issue requires additional information from the issue author. status: no recent activity This issue requires additional information from the author, but hasn't been updated recently.

Comments

@v-lga-hub
Copy link

v-lga-hub commented Oct 24, 2019 •
edited
Loading

We encourage tool related questions to be asked on stackoverflow.com and tagged with accessibility-insights.

Your question here
Make sure to provide enough context. If you have spoken to a team member please mention them here.
spinner just a part of NumericUpDown control in System.Windows.Forms. the name of spinner should not be changed by code. So does this kinds of issue shouldn't be a accessibility defect?
Add any items (screenshots etc) that will help.
image

6-453e6d80-f670-11e9-8893-70ea0817e465.png)
TestResults 10-24-19.zip
@msft-github-bot msft-github-bot added the status: new This issue is new and requires triage by DRI. label Oct 24, 2019
@lamaks lamaks removed their assignment Oct 25, 2019
@lamaks lamaks added status: needs investigation This issue requires investigation by the Accessibility Insights team. and removed status: new This issue is new and requires triage by DRI. labels Oct 25, 2019
@msft-github-bot
Copy link
Collaborator

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

@DaveTryon
Copy link
Contributor

@v-lga-hub, what you're seeing here is the same issue that is reported at microsoft/axe-windows#150 and dotnet/winforms#1588 (last updated on October 8th 2019). It represents a shortcoming in the Windows Forms NumericUpDown control, and is not something that would typically be fixed in your code. We know that the WinForms teams knows about this issue, but we don't have any specific visibility to know when a fix will become available.

There are 2 main ways to respond to this reported issue (in increasing risk)

  1. Leave your code as is for now, and wait for an updated version of Windows Forms (that contains a fix), then upgrade to the new version of Windows forms. You'll need to include this reported issue in your VPAT (if your product needs one) until the issue is actually fixed.
  2. Consider using a framework other than Windows Forms (nuclear option).

Please let us know if you have any additional questions. Thanks!

@DaveTryon DaveTryon added the status: needs author feedback This issue requires additional information from the issue author. label Oct 28, 2019
@msft-github-bot
Copy link
Collaborator

The team requires additional author feedback; please review their replies and update this issue accordingly. Thank you for contributing to Accessibility Insights!

@msft-github-bot msft-github-bot removed the status: needs investigation This issue requires investigation by the Accessibility Insights team. label Oct 28, 2019
@RussKie
Copy link
Member

RussKie commented Oct 31, 2019

@M-Lipin didn't we fix the spinner issue?

@msft-github-bot msft-github-bot added the status: no recent activity This issue requires additional information from the author, but hasn't been updated recently. label Nov 4, 2019
@msft-github-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for contributing to Accessibility Insights!

@M-Lipin M-Lipin mentioned this issue Nov 14, 2019
Closed
@M-Lipin
Copy link

M-Lipin commented Nov 14, 2019

@M-Lipin didn't we fix the spinner issue?

I can reproduce it in .NET Core 3.1, filed the bug: dotnet/winforms#2370

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@v-lga-hub v-lga-hub

Labels
status: needs author feedback This issue requires additional information from the issue author. status: no recent activity This issue requires additional information from the author, but hasn't been updated recently.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@RussKie @M-Lipin @lamaks @msft-github-bot @DaveTryon @v-lga-hub