UI is not accessible for blind and low vision users that are using screen readers

[hamidrezaabroshan]

Blind and visually impaired users are using screen readers such as nvda screen reader to work with the computers.
When I navigate on the screen with tab key or arrow keys, in most cases, Nvda reads nothing.
To Reproduce
download free and open source Nvda and try to navigate by tabbing or arrow keys.
Expected behaviour
The component type and value should be reported and the blind user should have access to this app too.
The keyword for finding dev resources is ui lib + accessibility such as Telerik accessibility, but I'll put some resources that I found.
https://docs.telerik.com/kendo-ui/accessibility/accessibility-overview

https://www.telerik.com/aspnet-ajax/tech-sheets/accessibility-support
https://docs.telerik.com/aspnet-core/accessibility/overview
Thanks very much.

[aspriddell]

This is mostly to do with the TextBlock/Label components not being focusable that causes this issue. From a quick test, all telerik components actually work without any changes needed.

I don't have a timeframe on this one as it looks like WPF apps in general suffer from a lack of accessibility support but will do some research and see what works.

[hamidrezaabroshan]

Thanks, I'm not a dotnet or wpf expert, but these links may help. I researched about focusing on text blocks. If it helps, I can run some code snippets and report the results using a screen reader. https://learn.microsoft.com/en-us/accessibility-tools-docs/items/wpf/edit_name https://wpf.2000things.com/tag/accessibility/ Thanks a lot.

…

On Wed, Sep 28, 2022 at 6:49 PM Albie ***@***.***> wrote: This is mostly to do with the TextBlock/Label components not being focusable that causes this issue. From a quick test, all telerik components actually work without any changes needed. I don't have a timeframe on this one as it looks like WPF apps in general suffer from a lack of accessibility support but will do some research and see what works. — Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALUYRA7Y4EAUCWRDTXHHIXLWAROZXANCNFSM6AAAAAAQUUHMLU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- hamidreza

[NiKola-UE]

In this regard, Freedom Scientific's JAWS has an advantage because it still handles different boxes, frames, text blocks and charts better, but it is a proprietary and commercial program. NVDA still has problems with all of that even though it's getting better and that should be discussed with the authors on their pages. But I agree that the OnionFruit's user interface should be adapted so that screen readers can cope better. But one should be fair and in defense say that the user interface and technical support of the OnionFruitare quite good. Just for the sake of comparison, a similar and interesting program called TorWall Tallow is not adapted to keyboard and screen readers at all. I have written to the author Basil several times at the his official e-mail address, I have also opened
this issue, ,
but still no one has given me any answer to this day; which cannot be said for DragonFruit Network team.