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

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

Open
hamidrezaabroshan opened this issue Sep 24, 2022 · 6 comments

Comments

@hamidrezaabroshan
Copy link

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
Copy link
Member

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
Copy link
Author

hamidrezaabroshan commented Sep 28, 2022 via email

@NiKola-UE
Copy link

NiKola-UE commented May 31, 2024

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.

@hamidrezaabroshan
Copy link
Author

hamidrezaabroshan commented Jun 1, 2024 via email

@NiKola-UE
Copy link

Yes, of course I did. I am also a blind computer user and I know well how screen readers work even though I am not a programmer. I also know where to download the crack of JAWS, but I can't promote it here.

@aspriddell
Copy link
Member

There's now a complete rewrite using Avalonia UI that's now available on this repo and as an update when Cutting-Edge releases are enabled on supported devices (x64 processor running Windows 10 22H2 or later).

I am still interested in improving accessability and if anyone has a go using the new version I'd love to know opinions on whether it's an improvement over the previous version. There's a thread on the Avalonia repo talking about automation/screen reader support but nothing recent (and was opened nearly 8 years ago).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants