Ticket #360 (new enhancement)
When loading a URL with a target anchor, NVDA should jump to that anchor
| Reported by: | mohammed | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Browse mode | Version: | development |
| Keywords: | Cc: | ||
| Operating system: | Blocked by: | ||
| Blocking: |
Description
Currently, when NVDA encounters html anchors, (typically links that jump to parts of the same loaded page), it reports them as links. Nvda should distinguish between links and anchor links. it should report them more discriptively like "same page link".
Also, NVDA doesn't seem to jump to the relevant part of the page that those anchor links refer to. take for an example any wikipedia page, which are full of such anchors: http://en.wikipedia.org/wiki/Comparison_of_screen_readers#References
tested with nvda r3040 and both IE8 and firefox 3.5.
Change History
comment:1 Changed 3 years ago by jteh
- Summary changed from NVDA should report and jump to Html anchors accurately to When loading a URL with a target anchor, NVDA should jump to that anchor
comment:2 Changed 11 months ago by jteh
This already works in IE (changeset:main,3033).
It still doesn't yet work in Firefox. We need MozillaBug:617544 to fix this.
comment:3 Changed 4 months ago by jteh
After MozillaBug:691734 (fixed in Gecko 10) and changeset:main,4719, we will get this right as long as the document is loaded while NVDA is running. We still need MozillaBug:617544 to get this right for documents loaded *before* NVDA is started.


The reporting of same page links is a duplicate and was reported in #141. As I noted there, browser users in general cannot differentiate between same page and external page links unless the site marks them in some way, so I don't believe it is important to implement this. Please continue discussion on this part of the issue in #141.
I'm hijacking this ticket to cover the jumping to anchors issue. For me, if I press enter on a same page link in Firefox, it does correctly jump to the anchor. However, it often doesn't when you access the URL directly. I assume the latter is what you are referring to? Unfortunately, Firefox doesn't expose sufficient information for us to do this via accessibility APIs, so we'll need to discuss this with them.