News for hackers. Stuff that matters.
Re:Leveraging Rust and the GPU to render user interfaces at ... by Gigachad on Thursday March 09, 2023 @04:18AM (#35079570)
I’ve heard it’s hard to even work this out as all of the screen reader tools are expensive, proprietary, and there are no standards. The typical way is to just make your program, and if it gets popular, the screen reader companies will find a way to make their product work.
Re:Leveraging Rust and the GPU to render user interfaces at ... by lukastyrychtr on Thursday March 09, 2023 @05:15AM (#35079869)
That's partially true, but fortunately not completely. There are widely use open-source screen readers for Windows and, of course, there's no proprietary screen reader on Linux. And, definitely, there are standard APIs which are used to communicate the accessibility tree between an app and a screen reader. Yes, they are specific for each platform, and Windows has multiple of these, but they are standardized at least for each platform.
Re:Leveraging Rust and the GPU to render user interfaces at ... by illiarian on Thursday March 09, 2023 @05:15AM (#35079870)
> work this out as all of the screen reader tools are expensive, proprietary, and there are no standards.

ARIA is a good start, and screen readers built into the OS are a good start.

Moreover, major OSes have accessibility APIs that screen readers will use:

- MacOS https://developer.apple.com/library/archive/documentation/Ac...

- Windows: https://learn.microsoft.com/en-us/windows/apps/develop/acces...

Re:Leveraging Rust and the GPU to render user interfaces at ... by pflanze on Thursday March 09, 2023 @06:46AM (#35080328)
Here are recent suggestions for Windows and Linux by a blind person: https://news.ycombinator.com/item?id=35008647
Re:Leveraging Rust and the GPU to render user interfaces at ... by mwcampbell on Thursday March 09, 2023 @09:03AM (#35081244)
This used to be the case on Windows, but hasn't been for at least 10 years, and has never been the case on Mac OS X (using the historical name for clarity) or Linux. On Windows, the open-source NVDA screen reader is widely used. Furthermore, the hacks that Windows screen reader developers historically used to "find a way to make their product work", particularly intercepting GDI API calls (either in user space or in a display driver) to build an off-screen model, are not applicable to modern UI stacks. And the other major screen reader hack, using application-specific COM object models, was mostly only applicable to Microsoft Office and Internet Explorer. So you basically have to implement platform accessibility APIs to make your UI accessible. (If you use native controls, that's more or less done for you.)
Re:Leveraging Rust and the GPU to render user interfaces at ... by GreedCtrl on Thursday March 09, 2023 @02:30PM (#35085517)
As someone who's doing some accessibility programming but has no background in the field, I do have a random question to throw your way if you are game.

Our team is developing voice control for a website. This is mainly requested by sighted users who want to use the site hands-free. But we also have an accessibility mode for better screen reader support.

We think voice control might be appreciated by screen reader users too, but we aren't sure how well it would work with a screen reader.

Are there common pitfalls we should be wary of?

One thing we're worried about is that the voice from the screen reader might interfere with the detection of the user's voice.

I know general dictation and voice control software already exists, so my initial assumption that screen reader users would benefit might be wrong. If the existing tools are good enough, perhaps this whole question is moot.

Re:Leveraging Rust and the GPU to render user interfaces at ... by mwcampbell on Thursday March 09, 2023 @03:44PM (#35086411)
Yes, the screen reader output will probably interfere with your speech recognition. You may be able to work around that on some platforms by enabling echo cancellation when getting mic input from navigator.getUserMedia, but I don't know if that actually works on any desktop platforms.

In general, you should assume that the user already has whatever assistive technologies they need, and you don't need to provide your own, just make the content and UI accessible using semantic HTML and (if needed) ARIA. Providing your own screen reader, for example, would definitely be a mistake. The same should ideally also hold for voice control, but apparently you're actually getting some demand for that.