mastodon - Link to source
Finally, NVAccess has agreed to separate links from the adjacent non-link text and display them on separate lines as a toggleable option. It’s still unclear when this will be implemented, but it's a good step forward in my opinion. I opened this issue in April 2020, and many users really want it.
Their comment states:
"We appreciate the constructive community feedback. We've triaged this issue, meaning we would accept this feature as a toggleable option."
github.com/nvaccess/nvda/issue…
@NVAccess

Issue displaying text after links when the Screen Layout mode is turned off

Steps to reproduce: First and foremost, make sure the Screen Layout mode is turned off. It can be done via Insert+V when placed on a webpage. The issue can be duplicated everywhere but, as an examp...
amirsol81 (GitHub)
@NV Access
This entry was edited (3 days ago)
in reply to Dennis long

mastodon - Link to source

Amir

@Dennislong82 With all respect, complaining will get us nowhere. Yes this should have been implemented earlier, and yes I don't know if this will be done soon. But such is the status of JAWS, NVDA and VoiceOver on the Mac. Personally I'm not willing to even touch VoiceOver on the Mac given its horrible issues and limitations. If you feel Apple will deliver something more efficient compared with NVDA and JAWS - something which they have consistently failed to provide, go for it.
@NVAccess
@NV Access @Dennis long
in reply to Amir

mastodon - Link to source

Kaveinthran

@Dennislong82
I agree on this, working directly on the issues, debating constructively which should happen with what kind of priorities, bringing up feature request to ad-on authors if the core hesitates, learning to write our own code is a better anger channeling rather than making statements that go nowhere. The complexity underlying open source software is beyond explanation, this is not a hobbiest project that can make everything a reality for sure.
@Dennis long
in reply to Kaveinthran

mastodon - Link to source

Kaveinthran

@Dennislong82 the project is too large, too complex and too much is happening around it. You can get overwhelm quicly if you look at the issues filed daily. Adding to that, donations, priorities, availability of people to code with their own experience and ability make this a more complex endeavor. The least that we can do is learn how this project work and happen in day to day bases.
@Dennis long
in reply to Kaveinthran

mastodon - Link to source

Kaveinthran

@Dennislong82 one thing that is less discussed here sadly is the philosophy behind jaws and NVDA. jaws wants to be more than a screen reader, it appears to solve even access issues, that needed to be solvedd by the software /website coders. NvDA underlying philosophy since its inception, at least from what I know is very different. Why we want things to be same for every screen reader? it don't have to be same to win the users.
@Dennis long
in reply to Kaveinthran

mastodon - Link to source

Kaveinthran

@Dennislong82 The philosophy for Jaws definitely works for its commercial appeal. Nvda, on the other hand, has not been vocal about their financial or man power difficulty, has they? do we really know what it takes to run or develop opensource software this big or are we too occupied with our own smaller worldview. There has been many commercial #screenReaders but till now, only one #openSource screen reader? why is that? #nvdasr
#opensource #nvdasr #screenreaders @Dennis long
in reply to Kaveinthran

mastodon - Link to source

Kaveinthran

@Dennislong82 I am old enough to remember sometime in 2010 or 2011 nvda posted a blog post saying that their future is unsure and they need a donation to sustain them after the July of that year. I couldn't find the blog post verbatim, but you can look at this, nvaccess.org/post/a-more-certa…

NV Access | A more certain future for free screen reader NVDA

www.nvaccess.org
@Dennis long
in reply to Kaveinthran

mastodon - Link to source

Kaveinthran

@Dennislong82
here's extract
"Jamie and Mick, the core developers of NVDA, are essentially paid minimum wage for their experience, knowledge and skills, which they are prepared to accept because they love the fact that they are making a positive contribution to the blind community and the accessibility industry more generally. Despite their willingness to carry on, however, there will be no money to pay them after July 2011 unless we receive some financial assistance." #nvdasr
#nvdasr @Dennis long
in reply to Dennis long

mastodon - Link to source

Kaveinthran

@Dennislong82 One reason that I can think of why they're not adding this or any other toggle options is that the settings would get too large and complicated, as I said, the philosophy underlying two screen readers are different and understandable. The larger the project, the harder and more complicated than it to maintain, it's an infinite testing mechanisms to toggle or not to toggle and how things change when some things got added in the future. (1/2)
@Dennis long
in reply to Kaveinthran

mastodon - Link to source

Amir

@kaveinthran Still bad argument IMO. If a feature is worth adding, it should be added with all of the complications involved. And NVAccess has already done more complicated things which might not end up to be that useful. Just look at their Image describer in 64-Bit alphas. A lot of efforts and development time for a local AI interpreter which is the worst and the least accurate AI describer I've ever seen in an accessibility-oriented product. That effort could have gone into making Outlook, MS Word, or web/ HTML verbosity better.
@Dennislong82 @NVAccess
@NV Access @Kaveinthran @Dennis long
in reply to Amir

mastodon - Link to source

Kaveinthran

@Dennislong82 I guess the current team at least are hesitating to venture on the speech refactoring or verbosity part, a bit slower than once excitement.
In the other world, say, firefox, or linux, people make thousands of forks and distros, I wish more of that happens in the screen reader world. Forks of #nvdaSR would allow different design philosophies to flourish together.
#nvdasr @Dennis long
in reply to Kaveinthran

mastodon - Link to source

Jamie Teh

@kaveinthran This isn't even a question of design philosophy, so a fork wouldn't help that. This is ultimately about what a very small team of developers has the capacity to handle. The fact that this (and other issues) have been triaged means that pull requests would be accepted for them, so I don't see how a fork would change anything here. @amir @Dennislong82
@Kaveinthran @Amir @Dennis long
⇧