Hot answers tagged


Not only is Helvetica not safe, but it is also a copyrighted font, so you need a license to use it if you load it as webfont. As a matter of fact, there are no 100% safe web fonts, since it will depend on the fonts the user have on his/her device, and different operative systems have different font sets. Hence, you need to do something like this: p{font-...


As mentioned there is no such thing as a safe web font. But there is a way to load in missing fonts from your server through the use of @font-face. @font-face was first introduced in CSS2, includes fallback file types, and is widely supported. This wouldn't be a 100% solution but it would be more promising than depending on the machine's font selection. ...


be accessible on any device Really no such thing as 'available on any device'. If you're not using embedded fonts, then you need to use a font-stack, so you have some back up options in case the first isn't available.


Helvetica is not part of any Windows default font-set, therefore Windows users are likely to see another secondary font. If that's not a concern for you, use Helvetica.


I cannot answer #2, but I can take a stab at #1 with some explanation. Background The Web Content Accessibility Guidelines (WCAG) 2.0 (the basis for Section 508 in the US, some international regulations, and the ADA guidelines that the DoJ has used in recent lawsuits) have some guidelines on this. Success Criterion (SC) 1.4.1: Use of Color: Color is ...


There are many ways to address this, essentially the aim is to differentiate links from other text on a site. While an underline is the default way that browsers make this apparent, you could use a high contrast color difference, a 'highlight' effect, a custom bottom border, or a link icon. I think the best approach to this is to think of your aim and why ...

Only top voted, non community-wiki answers of a minimum length are eligible