Then it's an outdated materialized view. If you don't refresh your view from a browser is it a consistency issue? No. Not in in the way the term is usually used.
Read the first paragraph on eventual consistency on wikipedia, it describes the agreed upon definition.
"Eventual consistency is a consistency model used in distributed computing to achieve high availability that informally guarantees that, if no new updates are made to a given data item, eventually all accesses to that item will return the last updated value"
It refers to the same concept and technically and colloquially its referring to databases or things similar to databases. If it didn't then every system on the face of the earth is eventually consistent because of browsers and caches and timing. Every browser eventually presents an outdated view if it's not refreshed. If that's the case what is the point of the word? The word is obviously used for categorization.
Thus The scope is usually and colloquially a database systems or some combination of services that represent a source of truth.
If you read further into the article you cited you will encounter this:
"In order to ensure replica convergence, a system must reconcile differences between multiple copies of distributed data. This consists of two part..."
Literally the article assumes we are talking about distributed systems where replicas can exist.
Is a cache a replica? Is a browser a replica? No. The scope is obviously the source of truth at the resolution where you can have replicas aka: two or more sources of truth.
Read the first paragraph on eventual consistency on wikipedia, it describes the agreed upon definition.
"Eventual consistency is a consistency model used in distributed computing to achieve high availability that informally guarantees that, if no new updates are made to a given data item, eventually all accesses to that item will return the last updated value"