mastodon - Link to source

According to NVAccess, there are over 2,000 #NVDA open issues and if seeing one fixed is "particularly important" to me, they would "encourage hiring someone to work on it."

So how about it, #blind programmers? Your serious quotes for fixing this bug on a freelance basis:

github.com/nvaccess/nvda/issue…

#accessibility


Can't review/spell text of accessible names applied with aria-label/labelledby in focus mode · Issue #15159 · nvaccess/nvda

When a control on a web page is given an accessible name via aria-label or aria-labelledby, and NVDA's focus mode is active, the text of the control's name cannot be spoken or spelled with the "rep...
GitHub
#Accessibility #blind #nvda
in reply to James Scholes

mastodon - Link to source

Talon

I probably tried to rephrase some super snarky message about AI image descriptions and chatbots and magnification and NVDA remote which are all on the roadmap and apparently more important than fixing this bug and others, some of which have been open for 10 years (!) which affect real users right now like 5 times but I am slipping further into sadness so I think I'll stop trying now and utter a sigh of defeat for what could have been instead.
in reply to Talon

mastodon - Link to source

James Scholes

Sadness is definitely the word.

The pipeline seems to be: say something on social media, get told to open an issue, follow up on issue years later, get told in clipped tones to arrange a fix for it yourself (that they'll need to review) because there are too many open issues.

(Edited to remove previous comment about secure add-ons that was probably a bit much.)

This entry was edited (1 week ago)
in reply to James Scholes

mastodon - Link to source

Jamie Teh

@talon I'd point out that there are a huge number of users complaining (quite aggressively) about the current add-on ecosystem because of compatibility breaks. That's been a major point of contention for years now. The new ecosystem is designed to fix that, plus make corporate folks happy who apparently have significant security concerns. There are times when you can't win either way.
@Talon
in reply to James Scholes

mastodon - Link to source

NV Access

@Jage @jcsteh @talon the new add-on API is a different issue to Eloquence - Code Factory decided to abandon their users with no notice or explanation - as I gather they did on Android at the same time, so I don't know that it was even anything to do with us per-se. Worth mentioning that Tiflotecnia are offering a discount on their newest offering to those who had either older versions or the Code Factory Eloquence / Vocalizer license. See tiflotecnia.com/ for more details

Tiflotecnia Voices for NVDA | Home

Tiflotecnia Voices for NVDA is a multilingual synthetizer based on Serence TTS.
www.tiflotecnia.com
@Talon @Jamie Teh @Jage
in reply to NV Access

mastodon - Link to source

James Scholes

@NVAccess Sure. But back in the day, I remember NV Access trying to make a deal with whoever owned Eloquence at the time, only to be hamstrung by infeasible requirements. I don't know if those had anything to do with security, whether the new secure add-on ecosystem would resolve them, whether any of those things still apply given new ownership, or even if NV Access will ever try such a thing again. @Jage @jcsteh @talon
@Talon @NV Access @Jamie Teh @Jage
in reply to James Scholes

mastodon - Link to source

Jamie Teh

@talon github.com/nvaccess/nvda/issue…

Can't review/spell text of accessible names applied with aria-label/labelledby in focus mode · Issue #15159 · nvaccess/nvda

When a control on a web page is given an accessible name via aria-label or aria-labelledby, and NVDA's focus mode is active, the text of the control's name cannot be spoken or spelled with the "rep...
GitHub
@Talon
in reply to aaron

mastodon - Link to source

Munchkinbear

@fireborn @amir nope, most certainly not, and even I know that, with my *really* limited python experience, and that code may have been from another issue linked to the original posters issue, or something else entirely, but no PR was ever linked to the original posters issue indicating a fix so it remained open even after the fix was implimented. SO the take away. do better at triaging issues, guys not in this thread who I won't mention so they don't bite my head off.
@aaron @Amir
in reply to Munchkinbear

mastodon - Link to source

Amir

@munchkinbear @fireborn This is an intrinsic NVAccess issue or, to be fair, this is something which tends to affect open-source projects. Of course, commercial products have long-standing issues of their own, but, for instance, simply check the responses posted to a very irksome and serious NVDA bug affecting Start menu's search feature in newer Win 11 24H2 updates. JAWS was updated few months ago to fix it, whereas people on Github are suggesting that: A: Microsoft should fix it. B: There's not enough info to catch the bug, and that people don't understand how to file bugs. github.com/nvaccess/nvda/issue…

NVDA behaves erratically in the start menu · Issue #17951 · nvaccess/nvda

Steps to reproduce: Use NVDA to go to the start menu, try searching for something, and make sure you are on Windows 11, 24H2, and have the latest updates installed. Actual behavior: NVDA usually wo...
GitHub
@aaron @Munchkinbear
This entry was edited (1 week ago)
in reply to Amir

mastodon - Link to source

NV Access

@amir @munchkinbear @fireborn Nowhere in that issue is there an accusation that the issue wasn't filed properly? There is some confusion (between contributors) as to whether it is a Microsoft bug and the general consensus is that it was AND they've fixed the worse part of it. No intrinsic NV Access issue, just that we, like ANY project, open-source or not - needs clear information to resolve issues :)
@aaron @Munchkinbear @Amir
in reply to Jens Oliver Meiert

mastodon - Link to source

NV Access

@j9t If this was commercial software, we would need to prioritise issues just like we do now. What we do approach differently to a lot of other projects is we don't just close issues because we won't get to them in the next six months - THAT alone is why we have so many open issues. No-one is saying James' issue isn't valid or important. Sean's comment (on the issue) was not that we don't want to fix it, but that outsourcing it is one potential way to have it fixed sooner.
@Jens Oliver Meiert
in reply to Jens Oliver Meiert

mastodon - Link to source

NV Access

@j9t Thanks Jens, I appreciate that. We don't expect it as an option for most users (including James). We work hard to accurate triage issues, & prioritise staff time to those which affect the largest number of users in the most severe manner. While this may mean that annoying issues may persist for longer than desired, it is also important to mention that some 40% of NVDA code contributions come from the community, and the community is welcome to prioritise any issues they wish to work on.
@Jens Oliver Meiert
in reply to Jens Oliver Meiert

mastodon - Link to source

NV Access

@j9t And in fairness, we DO endeavour to be communicative & engage in discussion (as I am now). Can you say every software company does? (And no, I'm not doing this instead of fixing this issue.... Perhaps doing this instead of updating the Excel training material, but it's important, so here I am).

Yes, donations are very much appreciated - and for those who can benefit from it, the training & support in the shop: nvaccess.org/shop

And of course, developer time where possible

NV Access | Shop

www.nvaccess.org
@Jens Oliver Meiert
⇧