5 ms·
> Prevalent reason is ignorance... > Second reason, which makes most sense, is availability I think these arguments are in wrong order. Availability and page p
by vogre 10y ago
> Prevalent reason is ignorance...
> Second reason, which makes most sense, is availability
I think these arguments are in wrong order. Availability and page performance are huge things in webdev. Accessibility profit from correct fonts does not always cover usability cost of waiting them to download.
Arial and Helvetica are good readable fonts which always exist on every platform and don't require additional download.
- Freak_NL 10y ago> Arial and Helvetica are good readable fonts which always exist on every platform […] This used to be the case, but it is no longer so. The Microsoft Core Fonts are not necessarily present on each OS (except for Windows of course), although on GNU/Linux and Android (IOS as well I guess?) you often do get a set of comparable replacements that are automatically substituted. Helvetica is always present on Apple devices, but it is certainly not present on each common OS. There are no fonts that are guaranteed to be present everywhere (and this is fine). In HTML/CSS (and many other GUI APIs) you can always rely on getting a serif, sans-serif, or monospaced font when you use their corresponding reserved family names, and with @font-face you can load whatever you want (providing you use a font that can be redistributed by you that way). So if you want all users to see text on your website in Comic Sans Neue, then that is (trivially) possible.