New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome/Edge: NVDA unable to report the destination of various link types #14779
Comments
Confirmed in both Chrome and Edge. This does not occur in Firefox, and, as stated in the issue description, is not caused by #14723. The reason why this fails is that for these links the |
@lukaszgo1 @XLTechie Given the frequency of such links on various websites and considering the widespread use of Chrome/Edge, I'd appreciate it if the issue can be fixed. |
I'll look at it, but it may be a while before I get to it because of work.
|
Hi. Just submitted a pr which fixes this problem. The problem is that NVDA lands it's focus to a graphical element, which truely does not have a value containing url, but its parent element which is link, has such value. |
Closes #14779 Summary of the issue: destination of graphic links are not reported in chrome/edge Description of user facing changes Destination of graphic links now should be reported in chrome/edge browsers Description of development approach NVDA lands its focus to graphic elemeng "img" which does not have href value, but an element which is parent of that element is link. So one more check was introduced to ensure han if we are focusing a graphic element and its parent is a link, we are now replacing an object by its parent object
@beqabeqa473 @seanbudd @XLTechie @lukaszgo1 Given NVDA's inability to report links imbedded inside headings after graphic links, should I open another issue, or keeping this open is enough? To duplicate:
With Chrome 111/112, NVDA incorrectly says: "Not a link."
Again, NVDA incorrectly says "Not a link." |
@beqabeqa473 @seanbudd @XLTechie @lukaszgo1 As yet another example, NVDA can't report the destination of links on https://www.nvaccess.org for the following links: Basic Training for NVDA(eBook) heading level 2 link, NVDA Productivity Bundle heading level 2 link, NVDA Expert Certification heading level 2 link, and, Twitter Timeline frame Timeline region link NV Access. |
Normally, issue hijacking (even of your own issues :)) is a bad thing. I would
have said that the heading matter should be a separate issue, as #14783 closed
this one; but @seanbudd has re-opened this issue, so I'm guessing he thinks it's
related enough to be continued.
We could try a solution similar to what @beqabeqa473 used to resolve this as
well, but links inside of headings seem like the opposite direction to images
within links.
|
@XLTechie @seanbudd Please note that on https://www.nvaccess.org/ the NVAccess link at the beginning of the Twitter Timeline frame Timeline region isn't a heading, but its destination can't be reported either. I mean this link: https://twitter.com/NVAccess?ref_src=twsrc%5Etfw%7Ctwcamp%5Eembeddedtimeline%7Ctwterm%5Escreen-name%3ANVAccess%7Ctwcon%5Es1_c1 |
Suggest you update the title of this issue. I don't have that capability.
Something like "Chrome/Edge: NVDA unable to report the destination of various
link types"
|
@XLTechie I did - and also updated the original issue with an extra note to indicate the discovery of two relevant issues. |
@seanbudd @XLTechie @lukaszgo1 @beqabeqa473 et al, any chance of providing fixes for this issue? As things stand right now, the feature seems really limited unless some fixes are provided. |
Have you tested with alpha?
|
@XLTechie Yes, the "links inside headings" issue can be duplicated with the latest alpha. Check, for instance, www.npr.org or www.gsmarena.com for more. Also Twitter-related links on www.nvaccess.org are reported as being "not a link". |
This affects not only link in headings it is also reproducible in all browsers, but also buttons which act like links. are not considered. See for example these codepens which should ideally also be covered by nvda+k. Maybe it makes sense to cover everything that is wrapped inside a form and formaction attributes:
Button example
Form example with post action:
JavaScript onclick event and the Window.location.href:
Button example:
|
Conversation on Mastodon requesting this issue. Has anyone looked at what is still required here? |
Comment from Amir on Mastodon: more examples of that breakage.
|
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 comments for the two remaining issues.
Steps to reproduce:
Actual behavior:
NVDA incorrectly says, "Blank." If pressed twice, NVDA doesn't capture the link destination either.
Expected behavior:
NVDA should report the destination of the graphic link. Moreover, when pressed twice, the destination should be displayed in the text box.
NPR.org is just an example - this issue is duplicable on other websites such as https://www.gsmarena.com/
NVDA, with Chrome/Edge, is incapable of detecting/displaying the destination of graphic links, that is, links which are described by NVDA as "graphic links."
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Both installed and portable
NVDA version:
2023.1, portable without add-ons, and Alpha 27996, installed, with/without add-ons
Windows version:
Windows 11, 22H2 (OS Build 22623.1485)
Name and version of other software in use when reproducing the issue:
Google Chrome/Microsoft Edge V111/112
Other information about your system:
I haven't tested this with Firefox as I don't have it.
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes - as mentioned above
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tried
The text was updated successfully, but these errors were encountered: