Notons ainsi que les Captcha semblent en voie de disparition (ouf !) et qu’on est passés au contrôle assez opaque par les serveurs, DNS ou proxy qui tentent comme un Firewall de filtrer les robots avant même que la page ne soit servie (Cloudflare ou Anubis sont devenus communs au chargement d’une page au cours de cette année d’attaque du web par les robots). Moins de travail pour nous pauvres humains.

Et nous voilà fin 2026, les robots règnent sur le web (les statistiques de ce blog me le montrent chaque fois) que ce soit en lecture, en ingestion, ou en écriture d’ailleurs, puisque environ un tiers des textes du web seraient écrits par ou avec une IA (étude Pewresearch d’août 2026).

En 2013, le designer Sang Mun a crée normalement discernable uniquement pour les humains avec la police ZXX.
En 2016 est apparu Fungal de Jeremy Landes et Raphaël Bastide, bien plus réussi et poétique, mais qui nous parle de tout autre chose, et est pour sa part finalement plus clair pour les robots.
En 2026, Eric Lu qui a créé Mixfont, une fonderie de typographies faites par IA à San Francisco (ironie encore) propose coup sur coup deux caractères, Ghost Font, un bruit uniforme mais qui une fois mis en mouvement révèle un texte très pénible à discerner.
Quelques semaines pls tard, Decoy font utilise un texte net et un texte flou.
Shieldfont devient extrême et utilise les ligatures pour remplacer certains mots par d'autres. Elle est cependant triviale à décoder pour un LLM.

C'est toujours un jeu du chat à la souris puisque les IA arrive à lire ces fonts petit à petit.

A recap of the font specification.

With text-box-trim we gain control over which boundary line text boxes are cropped to, and finally we can trim away this extra space to work with a font’s actual visual height.

One of the most common use cases for a lot of us is visually centering text within elements like buttons or notifications. This is especially handy for fonts that have awkward spacing like Josefin Sans.

There are plenty of creative uses [...] I placed headings with their baseline flush against sections below using negative margins. [Using text-box-trim remove the use of margins and put the heading just on the line of the next section, https://quarterre.com/studio]

Another example is to put the line on the font baseline like https://www.wepioneer.co/

A collection of small, low stakes and low effort tools.

No logins, no registration, no data collection. I can't believe I have to say that. Long live the handmade web.

This tool calculates font metrics for an uploaded font. The values it outputs, such as aspect ratio, can be used with the CSS font-size-adjust property. For more details see MDN.

Ok, FreeType renders font on LCD screens 40% faster

Some examples

They have banned the Calibri font (which was chosen for its legibility) and reverted to the old Times New Roman.
The reason? Calibri is “too inclusive.”

* {
  letter-spacing: clamp(
    -0.05em,
    calc((1em - 1rem) / -10),
    0em
  );
}

Before algorithmic playlists and AI-generated headlines, there was a time of idiosyncratic grotesk typefaces full of texture and character. The period’s designers embraced these quirks through novel approaches to typography rather than trying to suppress or normalize them away.

It's a font based project that somehow seeds other projects?

The website scroll animation is also awesome.

They have other projects near https://gt-era.com/#:~:text=More%20from%20Grilli%20type

A font editor

If the maximum font size is less than or equal to 2.5 times the minimum font size, then the text will always pass WCAG SC 1.4.4, at least on all modern browsers.

The author also cites https://utopia.fyi/type/calculator/

Only transfer the useful part of a font. It subsets static Unicode-ranges, so only a part of the font will be downloaded.

text-wrap: pretty avoids short last lines, bad rag, poor hyphenation and typographic river.

pretty can be applied to anything on the page.
balance should be used for anything where you want all the lines to be the same length

Avoid layered text-shadows for text outlines.

Use paint-order: stroke fill instead!

The browser provides a default text size based on user preferences, and our text should be relative to that preference. Establishing our root font-size with an em value helps keep that relationship intact.

About the definition of one rem:

I really do want sites to usually just give me text around 24px (or ‘large’), because that’s a pretty good default for me.

Sites with smaller body text would ideally increase their font size, but sites with the same size or larger text certainly shouldn’t get even bigger.

Yes I share this assumption.

I slightly better approach:

html {
  font-size: clamp(1em, 0.9em + 1vw, 1.5em);
}