A client audit flagged Arial, Verdana and Segoe UI in our fallback font stacks. My understanding was that the browser only uses them if they're already available on the visitor's device. Does naming them create a licensing issue?
Do paid fonts need a license if they're only CSS fallbacks?
Answers
Just naming a font in a CSS stack generally doesn't distribute the font. It tells the browser to use that font if it's available locally, then move down the stack if it isn't. That is different from sending a font file to the visitor.
Check how each flagged font is being loaded before responding. If there are font files bundled with the site or loaded through a font service, check the applicable license for that use. If they're only local fallbacks, explain that distinction to the client.
Reply to this answer
Ask the auditor to identify the exact file or request they think needs a license, and the license terms they're relying on. A report that only flags a font name doesn't establish that you're serving its font file.
Reply to this answer
If the named fallbacks aren't essential to the design, a stack ending in system-ui, sans-serif is another option. It lets the browser use a system interface font where available, with a generic sans-serif fallback. The result can look different across devices, so check the layout before changing it.
kev:
That could simplify the stack, though changing it isn't necessarily required just because the audit flagged a name.
Reply to this answer
I'd be careful about turning this into a broad claim that fonts can't be copyrighted or that licenses never apply. Copyright and license terms can be complicated. The practical distinction here is whether you're merely referencing a local font or actually providing a font file.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Nervik~4c:
That helps. I'll check whether the audit found font files or just the names in the CSS.