FAQ: Typography - Web Fonts

This community-built FAQ covers the “Web Fonts” exercise from the lesson “Typography”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Build a Website with HTML, CSS, and Github Pages
Full-Stack Engineer
Front-End Engineer

Learn CSS

FAQs on the exercise Web Fonts

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!
You can also find further discussion and get answers to your questions over in Language Help.

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head to Language Help and Tips and Resources. If you are wanting feedback or inspiration for a project, check out Projects.

Looking for motivation to keep learning? Join our wider discussions in Community

Learn more about how to use this guide.

Found a bug? Report it online, or post in Bug Reporting

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

One can’t figure out, is required to link free or paid fonts to our HTML doc, even safe?

1 Like

Link fonts, both free and paid versions, should be treated with the same industry-recommended cybersecurity precautions as those applied to third-party Android/iOS apps: do not install or use, even if you trust the source developers who created them.

Google’s ToS does not require them to maintain, protect or repair the integrity of their servers. Furthermore, Section 230 of the Telecommunications Act of 1996 provides Google with full legal immunity from any damages, injuries, harm or death caused as consequence of willful negligence, malpractice or outright intent to do so. As a result of this loophole, Google’s services and products have become well-documented vectors for malware campaigns, including font links like “Roboto”, and are generally considered unsafe for cybersecurity reasons.

While Adobe’s ToS has similar leeway, they do not have Section 230 immunity against malware campaigns deployed from their servers, Creative Cloud and iOS services. Remediation in such instances are extremely limited in alloted filing time, jurisdiction and damages awarded, primarily arbitration by a third-party industry representative which has an almost-guaranteed rate of failure.

The issue is an inherent feature of “software-as-a-service”, and it’s the standard of how the Internet operates at this point in time. Generally speaking, anything you can’t legally hold accountable is unsafe and should be avoided at all costs.

1 Like

you really really really need to change the content of the webpage…

using hosted fonts (at least from google) in europe is illegal! it does not comply with GDPR as personal data will be collected from google without the users consent!

1 Like

Thank you for feedback. We have flagged this to our team for review.

1 Like