1 hour ago · Tech · 0 comments

Every so often I need to put an SVG with text on a website — an infographic, a diagram, a data visualisation with labels. Each time, I end up staring at the same bad choice. Option A: Convert the text to outlines. The SVG renders identically everywhere. No font loading, no layout surprises. Done. But now the text is a pile of path data. Screen readers see nothing. Search engines see nothing. Language models see nothing. Translation is impossible. A single typo fix means going back to the source file, regenerating, re-exporting. For every character in every label. Option B: Leave the text as text. Clean, accessible, editable. But on any device that doesn't have the font installed, the browser falls back to whatever comes first in the system stack, and your carefully spaced infographic turns into a broken layout that looks like someone used Times New Roman on a web 1.0 site. I've been choosing Option A for years and feeling bad about it. I couldn't find a good third option, so I built…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.