Skip to main content

The "Report link destination" command in NVDA 2023.1 is very popular. Press NVDA+k to report exactly where a link goes. This is an important #security feature for users. Do you use it? Read more in our In-Process blog: nvaccess.org/post/in-process-6… #a11y #ScreenReader #NVDA

In-Process 6th April 2023

The big news this time around is the release of NVDA 2023.1! But there’s plenty more exclusive news below so let’s get into it: NVDA 2023.1 It’s new release time! NVDA 2023.1 is n…
NV Access
#a11y #security #screenreader #nvda

modulux reshared this.

in reply to NV Access

Mohamed Al-Hajamy 💾
Mohamed Al-Hajamy 💾
• •
Yep, definitely do. Prior to this, I used a Firefox-specific trick where if you navigated down into a link, the destination would be exposed, but that also included the text of the link and didn't always work reliably.
in reply to Mohamed Al-Hajamy 💾

NV Access
NV Access
• •
@MutedTrampet The other main workaround used to be open the context menu, copy the URL and either read the clipboard, or paste it somewhere. But either way they were all clunky options :)
@Mohamed Al-Hajamy 💾
in reply to NV Access

Amir
Amir
• •
It's broken for various types of links - PLS check this issue: github.com/nvaccess/nvda/issue…

Chrome/Edge: NVDA unable to report the destination of various link types · Issue #14779 · nvaccess/nvda

Note: the "graphic link" issue has been resolved. But as mentioned in later comments, "heading links" and at least one unknown link type exhibit the issue described with NVDA+K. Please check the co...
GitHub
in reply to NV Access

Amir
Amir
• •
It's broken for various link types - PLS check this issue: github.com/nvaccess/nvda/issue…

Chrome/Edge: NVDA unable to report the destination of various link types · Issue #14779 · nvaccess/nvda

Note: the "graphic link" issue has been resolved. But as mentioned in later comments, "heading links" and at least one unknown link type exhibit the issue described with NVDA+K. Please check the co...
GitHub
in reply to Amir

NV Access
NV Access
• •
@amirsol Thanks Amir (and particularly for providing the issue link!) As a new feature, and particularly a web-related one, it is in some ways not surprising there are cases it doesn't for. It looks like there is a flurry of activity around it though, so hopefully there will be a fix in Alpha builds soon and in a stable build in the not too distant future!
@Amir
in reply to NV Access

Dave Taylor
Dave Taylor
• •
This is the one thing I am looking forward to, when I can upgrade, but since some of the addons I most rely on are not updated yet, I can't
in reply to NV Access

Andre Louis
Andre Louis
• •
I switched from one screen-reader that had it, to NVDA that at the time, didn't. I mentioned it on twitter and within weeks this update came out with it in. Now some might call that coincidence. I just call it 'speaking things into existence' haha. Seriously though, yes. Yes I do, all the time.
in reply to NV Access

Sarah Russell
Sarah Russell
• •
Sometimes, but most of the time I just get back that a thing is not a link, though it is registered as a link.
in reply to Sarah Russell

NV Access
NV Access
• •
@blindbat84 We're aware of an issue in chrome affecting certain types of links. It's being worked on and hopefully we'll have a resolution for it sooner rather than later. Here's the issue, do feel free to comment on it with any extra info: github.com/nvaccess/nvda/issue…

Chrome/Edge: NVDA unable to report the destination of various link types · Issue #14779 · nvaccess/nvda

Note: the "graphic link" issue has been resolved. But as mentioned in later comments, "heading links" and at least one unknown link type exhibit the issue described with NVDA+K. Please check the co...
GitHub
@Sarah Russell
in reply to NV Access

Sarah Russell
Sarah Russell
• •
Oh, this is lovely, thank you! I do use Brave myself mostly, so chromium based for sure, basically just Chrome in adifferent wrapping. I do fid it useful when it works though. It is great for email links.
⇧