What determines if a link will be visited?

I had a problem while testing our webapp for accessibility, although it seemed to be very simple, I could not find a clear answer to Google.

The problem is that the screen reader (in particular, Voice Over on iOS and OSX Safari) reads each internal link in the application as “Visited Links” even before the user clicks on any of them. All links have the same base (something like http://domain.com/path/index.html#what-the-link-does ), so my first instinct is that since these links indicate to different hashes in one file, links as viewed since this file was visited.

However, this is not the desired behavior. We would like all links to be simply referred to as a “link”. So here are my questions:

  • What determines whether a link is considered visited? Will it just visit the domain? Will this help visit a specific file? Or should different hashes of the same file have different visited statuses?

  • Is there a way to control this behavior and prevent reading links as visited? Perhaps some Aria parameter?

+6
source share
3 answers

Perhaps I misunderstood the question, but if your links are on index.html in your example, can you replace

 http://domain.com/path/index.html#what-the-link-does 

just

 #what-the-link-does 

The visited logic probably only applies to URIs excluding string / anchor request tags

+1
source

It depends on the implementation. According to specification ,

Perhaps style authors may abuse the: link and: visited pseudo-classes to determine which sites the user visited without user consent.

Thus, UAs can treat all links as invisible links or implement other measures to maintain user privacy when rendering and undisclosed links in different ways.

The specification requires that :link and :visited be mutually exclusive, but without specifying how.

0
source

I think the problem you are facing is the misuse of the accessibility tag. I assume that you are coding a one-page application, and each link to another view is an anchor. You must use the tag instead of some ninjitsu CSS. Here is a fantastic article about this:

http://www.karlgroves.com/2013/05/14/links-are-not-buttons-neither-are-divs-and-spans/

0
source

All Articles