True though the confusion about that is largely when you're not dealing with words like passwords or hashes. In the context of words it's going to be generally disambiguated by context, I can't think of an example off hand in writing where I and l will that ambiguous. The removal of serifs probably has a higher impact to more people unless I'm missing some common situation where they'd be easy to confuse in context.

▲

adrian_b 2 days ago | parent [-]

On the Web I see very frequently foreign names, user handles or URLs where I am confused about whether there is an I or an l, because that Web page has chosen to use a bad sans serif font that does not differentiate these letters.

Sometimes there is no problem because the words or links containing ambiguous letters can be copied and pasted. Other times there is an annoying problem because either the stupid designer has disabled copying (or like in the output of Google and some other search engines, copying does not copy the visible text, but a link that cannot be used in a different context, outside the browser), or because I want to write on my computer a link or name that I have received on my phone.

	▲	zzo38computer a day ago \| parent \| next [-]
		I disabled fonts on the web browser on my computer, in order to avoid that and other problems. I also disabled the display of non-ASCII characters in URLs (which required adding some codes to make it do that; the built-in settings will only work for the domain name and not the rest of the URL), and changed the font used for URLs, which also helps.
	▲	rtkwe 2 days ago \| parent \| prev [-]
		Yeah I understand it's an issue other places but I don't think it's actually a significant issue in government documents and forms written in English which is the usecase here. The choice doesn't have to satisfy all requirements it just needs to be a good choice for government writing.