question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update documentation and guides related to WinForms Accessibility

See original GitHub issue

.NET Core Version:

.NET Core SDK (reflecting any global.json): Version: 5.0.100-alpha.1.20073.10 Commit: 29f4d693a9

Runtime Environment: OS Name: Windows OS Version: 10.0.18363 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\5.0.100-alpha1-05536\

Have you experienced this same bug with .NET Framework?: Yes

Problem description: WinForms documentation and guides do not fully describe the steps and options about setting accessibility properties:

Additionally, the example from AccessibleObject page doesn’t show how to make screen readers announce changes in control’s state. and therefore might need to be revisited.

Expected behavior: Documentation and guides should be descriptive to allow app developers to implement accessible applications using WinForms controls.

Minimal repro: Create WinForms app, add several WinForms controls to the form, try to get information how to set up accessibility properties to make the application fully accessible. There is no default information except the AccessibleName has default value ‘null’.

Issue Analytics

  • State:open
  • Created 4 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
RussKiecommented, Feb 21, 2020

This issue should really moved to the docs repo.

Proposition for ‘AccessibleName’ property doc update: ‘AccessibleName’ property is used as a control name that can be easily accessed by users with disabilities who are assisted by accessibility technologies (UI Automation)/applications to translate the form content as an accessible content (for instance audio announcement for text labels). ‘AccessibleName’ should have descriptive name and in most cases should be same as the control name. For instance the ‘TextBox’ with name “First name” should have ‘AccessibleName’ “First name” so Narrator or another accessibility app can announce “First name TextBox” when navigating to it.

I wouldn’t mention “disabilities” at all.

- 'AccessibleName' property is used as a control name that can be easily accessed by users with disabilities who are assisted by accessibility technologies...
+ 'AccessibleName' property is used as a control name that can be easily accessed by users who are assisted by accessibility technologies...
1reaction
M-Lipincommented, Feb 19, 2020

It would be good to update the documentation with more descriptive text:

Proposition for ‘AccessibleName’ property doc update: ‘AccessibleName’ property is used as a control name that can be easily accessed by users with disabilities who are assisted by accessibility technologies (UI Automation)/applications to translate the form content as an accessible content (for instance audio announcement for text labels). ‘AccessibleName’ should have descriptive name and in most cases should be same as the control name. For instance the ‘TextBox’ with name “First name” should have ‘AccessibleName’ “First name” so Narrator or another accessibility app can announce “First name TextBox” when navigating to it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Windows Forms .NET Framework - Accessibility
Learn about accessibility functionality in Windows Forms-based applications with a selection of topics and tutorials.
Read more >
Accessibility Support | WinForms Controls
WinForms UI controls fully support MSAA and UI Automation to help assistive tools recognize the bounds, names, roles, states, and values of UI...
Read more >
Accessibility: Test Plan WinForms Controls
Visit the new documentation for updated content. Accessibility: Test Plan WinForms Controls ... “Test Status” Guidelines:
Read more >
The Complete Idiot's Guide to Success as a Real Estate ...
One is to use either ZipForm (www.zipform.com) or WINForms ... You can give the title company access to view just the documents they...
Read more >
C#.Net Developer's Guide - Page 786 - Google Books Result
530 moderators, adding, 713 Multiple Document Interface security, 676 Just In Time ... 158 internal keyword, 107 Internet clients access via proxy keyboard ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found