nvda

ARIA and the web group define title to be used. [0][1] It's just that many agents just don't use it correctly. JAWS and NVDA do. Microsoft Speech used to ignore it, but I think they fixed that around Windows 11 release. I'm not sure about VoiceOver. Most braille readers I've used... Well, you'll be lucky if they read anything correctly. With the three big ones, JAWS, NVDA and Speech using it correctly, I'm pretty happy guiding people to use it today. > The title attribute represents advisory information for the element, such as would be appropriate for a tooltip. On a link, this could be the title or a description of the target resource; on an image, it could be the image credit or a description of the image; on a paragraph, it could be a footnote or commentary on the text; on a citation, it could be further information about the source;

> NVDA looks like it is open source, it shouldn't be too hard to port. Yup. Just gotta invent a Win32-compatible Wayland first. This... Is sorta a "whole fucking owl" moment. > As explained above NVDA relies heavily on Windows specific API's and cannot be converted to run under Unix based systems without a lot of work. Given how small NVDA development team is spending time on making NVDA work under Linux at a level at which Orca works currently would take years and mean much less development for the version for Windows. In short the more reasonable course of action is to spend time on improving Orca or other Linux screen readers rather than porting (which in practice would mean almost rewriting from scratch) NVDA to run under a non Windows system. [1] Accessibility in Wayland is still in staging. [0] There is not the APIs you need, to por

It depends. Windows: Definitely NVDA (github.com/nvaccess/nvda) Linux: AT-SPI, ATK, Orca for the graphical side of things. The console/terminal is pretty well supported.

If on Windows, opening tickets on NVDA repo works wonderfully well, as long as they find them valid. https://github.com/nvaccess/nvda

After some brief research it seems the issue you're seeing may be a known bug in at least some versions/release of espeak-ng. Here's some potentially related links if you'd like to dig deeper: * "questions about mandarin data packet #1044": https://github.com/espeak-ng/espeak-ng/issues/1044 * "ESpeak NJ-1.51’s Mandarin pronunciation is corrupted #12952": https://github.com/nvaccess/nvda/issues/12952 * "The pronunciation of Mandarin Chinese using ESpeak NJ in NVDA is not normal #1028": https://github.com/espeak-ng/espeak-ng/issues/1028 * "When espeak-ng translates Chinese (cmn), IPA tone symbols are not output correctly #305": https://github.com/rhasspy/piper/issues/305 * "Please default ESpeak NG's voice role to 'Chinese (Mandarin, latin as Pinyin)' for Chinese to fix #12952 #13572": https://github.com/nvaccess/nvda/issues/13572 * "Cmn vo

Hey there, just to assume there are not enough blind or visually impaired musicians out there is not true. If you enpower people to do what they want then you will see how many these are. i mean there are more than 300 Million people worldwide living with a visual impairment, out of which more than 45 million are fully blind. I am a blind artist and would love to see improvements in Ableton live. I have also a proposal on how this could work with the NVDA, screen reader but for that the ableton installation should come with the NVDA controllerclient.dll. Here is the documentation https://github.com/nvaccess/nvda/tree/master/extras/controll... There is also the file NVDAController.h which lists the definitions for C. There are also some examples on how this is being implemented practically, the software must call the functions from the NVD

And there's still a lot of work for the third-party tools to do, too. https://github.com/nvaccess/nvda/issues/5186#issuecomment-20... https://bugzilla.mozilla.org/show_bug.cgi?id=381888 https://github.com/nvaccess/nvda/pull/9933 I read somewhere that screen readers look for a flashing vertical line, to detect the caret position in systems that don't expose it via the OS's APIs. I can't find a reference for that right now, though.

Article from 2020... many of these issues are no longer a thing and/or are just really weird to call out. From their accessibility bullets: > cannot be dictated or selected when using Dragon Naturally Speaking Isn't this just a speech-to-text engine? I can say that I haven't ran into anyone using this for web control in my entire career. I'm certain it has an accessibility use-case and all, but I haven't ran into a practical example. I'm very apt to write this off as "moot," and would also suspect it may have been addressed since 2020. Does anyone here use Dragon Naturally Speaking for web control? Good faith real question. > appears as unlabeled in NVDA's element list Fixed - https://github.com/alphagov/reported-bugs/issues/41#issuecom... > appears as a spin button in NVDA's object navigation, which has an edit field and two buttons insi

Permanent link (press 'y' anywhere on Github): https://github.com/nvaccess/nvda/blob/b5f82f878f344ab26004f3....

Some Windows screen readers used, and maybe still use, the same technique to get data out of the SysListView32 common control, since the parameters and results of that control's window messages aren't marshaled by the OS. Edit: Looks like NVDA still does. https://github.com/nvaccess/nvda/blob/master/source/NVDAObje...

https://github.com/nvaccess/nvda If there's one open source project that changed blind people's lives, that's it. It made screen readers go from about $1000 to practically free, at least if you're an individual, not a corporation. Alternatively, learn accessibility APIs for <platform>, and then start fixing bugs in open source apps. The meetings/messaging space could definitely use some work, for example. Stuff like Signal/Telegram, accessibility wise, is much worse than WhatsApp, same with Zoom vs. Jitsi.

> There are a number of browsers that run in Docker and that I can remote control (using Selenium, Playwright, Puppeteer or whatever) ... > > Does anyone know if something like that is available for screen readers - at least for a free and open source one? Nothing in this space is really mature yet, but there are some efforts to make it a reality. The ARIA-AT project[1], which aims to test assistive technology support for various WAI-ARIA and HTML constructs, is aiming to automate its testing across multiple screen readers [2]. NVDA, the free and open source screen reader mentioned in the article, also includes some integration-style tests[3]. [1] https://github.com/w3c/aria-at [2] https://github.com/w3c/aria-at/issues/349 [3] https://github.com/nvaccess/nvda/tree/master/tests/system

It is a problem, and: https://github.com/nvaccess/nvda

I can't speak for the OP. And while I'm visually impaired, I'm not totally blind, and I do my programming visually (though I often use a screen reader for other tasks). Still, I can point you at some projects by blind programmers. The largest project I know of that's written primarily by blind people is the open-source NVDA screen reader, written primarily in Python with some C++. It's on GitHub here: https://github.com/nvaccess/nvda For a fairly large, and long-running, project developed primarily by a single blind programmer, check out Emacspeak, written in Emacs Lisp with some Tcl, available on GitHub here: https://github.com/tvraman/emacspeak Edit: I almost forgot about brltty, a Linux console screen reader designed primarily for braille rather than speech output, written in C: https://github.com/brltty/brltty Now for a few small proj