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 [Inspect]: Cannot find the RichEdit control of the "Text" property in UIA structure of a PropertyGrid control #2704

Closed
M-Lipin opened this issue Jan 13, 2020 · 5 comments · Fixed by #3014 or #3849
Labels
tenet-accessibility MAS violation, UIA issue; problems with accessibility standards

Comments

@M-Lipin
Copy link
Contributor

M-Lipin commented Jan 13, 2020

  • .NET Core Version:

.NET Core 5.0.0-alpha.1.19564.1 (also reproduces in earlier versions of .NET Core WinForms.

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

Problem description:

The issue is that RichEdit control is not shown in the UIA hierarchy of PropertyGrid control children.

image

Expected behavior:
RichEdit control (when shown) should appear in the PropertyGrid control's children hierarchy.

Minimal repro:

  • Create WinForms app with PropertyGrid and Button control.
  • Associate the button with PropertyGrid as a selected object.
  • Run the app, type something in the RichEdit control control (this is a button's text input control) and inpsect the button with the Inspect tool. Observe that the input is not in the UIA hierarchy.
@weltkante
Copy link
Contributor

Does this work for other popup/dropdown editors in the property grid? (Control editors, including custom editors, have the option to opt-in into either a dropdown or a popup.) If the problem isn't just isolated to RichTextBox it might be worth looking for a general solution so user defined editors can also profit from the solution.

If the solution to this accessibility issue requires certain code in the editor itself it might be worth documenting it, so programmers of user-defined editors can also solve this problem for their own editor implementations.

@RussKie RussKie added the tenet-accessibility MAS violation, UIA issue; problems with accessibility standards label Jan 14, 2020
@merriemcgaw merriemcgaw added this to the 5.0 milestone Jan 23, 2020
@merriemcgaw
Copy link
Member

merriemcgaw commented Jan 23, 2020

That's a great point @weltkante. I think this works as expected for the other editors. @M-Lipin can you confirm?
If there's something specific we did to get those to work that we missed with this one; we should add that note to the docs.
I've got an accessibility samples and documentation project simmering on a back burner that may be coming up one of these days :)

@M-Lipin
Copy link
Contributor Author

M-Lipin commented Mar 12, 2020

Thank you for the points @merriemcgaw and @weltkante ! The solution works for all drop-down editors. But popup inner accessibility and accessible hierarchy is the responsibility of editor's developer.

@Marie-Shi
Copy link

Verified the issue with latest .NET 5.0.100-rc2.20459.18 from RC2 branch, it is fixed. Now RichEdit control (when shown) appears in the PropertyGrid control's children hierarchy.
Untitled

@Marie-Shi
Copy link

Verified the issue with latest .NET 6.0.100-preview.1.21080.4 from Release/6.0.1xx-preview1 branch, it is fixed. Now RichEdit control (when shown) appears in the PropertyGrid control's children hierarchy.

@RussKie RussKie removed this from the 6.0 milestone May 17, 2021
@dotnet dotnet locked as resolved and limited conversation to collaborators Feb 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.