mastodon - Link to source

I'm so glad NVDA, Narrator, Orca, VoiceOver, TDSR, and Fenrir exist. I'm so, so glad JAWS is not the only desktop screen reader, and that FS did not persue JAWS for Mac.

I'm so glad that NVDA not only supports addons, but shows them off with the addon store! I'm so glad that NVDA is so inescapably popular that even big corporations support them, like Google Docs and Microsoft Office and countless others that say in their documentation that NVDA is supported.

#accessibility #blind #nvdasr #nvda #technology

#Accessibility #blind #technology #nvdasr #nvda

reshared this

in reply to patricus

gotosocial - Link to source

Lukáš Tyrychtr

Okay, but then, either provide the logs from Orca's debug, tell us what is wrong via bug reports or mails on Orca list, or you'll have always the thing which annoys you, so you'll be posting these posts. For example, without any specifics, I can not reproduce (or anyone) your Orca responsiveness issues, which I, except for huge web pages (say a table with tens of thousands of rows) can not reproduce. And yes, it might be also hardware dependent, so hardware specs along with the Orca debug log would be best.
in reply to patricus

gotosocial - Link to source

Lukáš Tyrychtr

It of course can. Yes, you do not get a completely pythonic API (you'll have to look for the docs and likely for the Orca source), but the usage after you get hold of the proper DBus interface will be, say, using the dasbus library, quite Pythonic. Of course, when one person works on a project, don't expect polished docs and client side libraries, but of course, you are more than welcome to contribute them.
in reply to patricus

gotosocial - Link to source

the esoteric programmer

do you know what dbus is and what it can do? also, that would be true if we didn't have dbus introspection. I recommend you use a dbus python library, then maybe you'll see it's not that bad. There are performance issues with orca for sure, especially when you compare it to like, jieshuo on android or zdsr for windows, but for one, that's one of the reasons for which we're trying to get odilia off the ground, and for another, in most cases you wouldn't actually notice the orca latency because your system will generally be slower than orca by an order of magnitude. So yeah, there are issues with linux, accessibility, orca and all that stuff, but let's not invent issues where there are none, there are enough existing ones already.
in reply to the esoteric programmer

mastodon - Link to source

patricus

@esoteric_programmer @tyrylu even if there's a dbus lib that a mediocre dev can use, ok that's cool
I don't have a linux box so that'd be not feasible ATM.
and the perf hit is bad, on wayland. on x11/xorg it seems to work on par with NVDA
but let's be honest, not everyone wants to run old stuff that isn't supported anymore.
@Lukáš Tyrychtr @the esoteric programmer
in reply to patricus

gotosocial - Link to source

Lukáš Tyrychtr

Wayland can not introduce any performance differences, the a11y layer basically did not change between them (except for small differences), so, I'd vote for the audio emulation, some Vmware or Virtualbox sound drivers (I can not now remember which ones exactly) are quite bad with Pipewire without some obscure changes, so, yes, try some live distro, like Fedora with Gnome, or Ubuntu, but on a physical system.
⇧