“Fix web accessibility systematically · Eric Eggert”

“Learning to build conviction - benkuhn.net”

I guess winter has arrived.

The view from my kitchen window. A snow-covered, parking lot, buildings, trees, and landscape.

“Blaming Screen Readers 🚩×5 - Adrian Roselli”

“Joyce and Walky! » The baby can hear stuff now”

“Software developers have stopped caring about reliability”

This x1000. There’s been a shift in software dev away from reliability and usability. All of the incentives line up against them.

Remember this Chrome headless bug that I’ve been obsessing about?

Turns out that this is a known bug in Chrome headless on Linux. To fix it either turn off hinting or subpixel positioning

github.com/puppeteer…

Screenshot from Chrome headless where the text rendering is all over the place Another screenshot of unreadable text

“Some reasons to work on productivity and velocity”

“Custom properties with defaults: 3+1 strategies – Lea Verou”

I don’t mind the verbose solution, personally, but these are all good tactics.

“Implementing form filling and accessibility in the Firefox PDF viewer – Attack & Defense”

PDF.js is an amazing library. I just wish it were better documented.

“The dark side of Eureka: Artificially induced Aha moments make facts feel true - ScienceDirect”

“Was it easier to build websites a decade ago? - Go Make Things”

Absolutely agree with this. The modern web is capable of amazing things. You don’t have to do it the hard way. (I mean, yeah you do if your boss is dead set on it, but you know what I mean)

“Every search bar looks like a URL bar to users – Terence Eden’s Blog”

So, it looks like the kerning/spacing problems I saw in the PDF output of puppeteer/headless chrome on Linux wasn’t just an issue with a single font. Snaps from a test file: Literata, EB Garamond, and Inter

A screenshot of a sample text showing very ugly spacing issues. Literata, which is a readable serif font.A screenshot of a sample text showing very ugly spacing issues. EBGaramond, which is a pretty but less readable serif font.A screenshot of a sample text showing very ugly spacing issues. Inter, which is a very nice sans-serif font.

“CSS is Going Gosh-Darned Hog Wild, I Tell Ya What - CSS-Tricks”

CSS is easily my favourite part of the web stack.

“Appwalls and their apps are destructive to the open web. - Airbag Industries”

So, it turns out that the typographic quality of Chrome’s PDF output varies quite a bit OS to OS.

Subjective assessment:

  • macOS: really good
  • Windows: not bad, though not as good as macOS
  • Desktop Linux: same to marginally worse than Windows
  • Headless Linux: quite bad.

As always, I am a goddamn bug magnet. Not only have I run into a known Chrome bug in my PDF testing (no hyphenation on linux when headless/puppeteer) but I seem to have discovered a ligature bug in weasyprint. Justifying text with a custom font seems to disable ligatures.

“Discovery - Feedback - Silicon Valley Product Group”

“About TypeScript Hype. Are you happy about TS? Good, really…”

TS is a very useful JS superset. Its fanbase, however, is extremely annoying, even tho it feels a bit like they’ve toned it down a bit of late. Maybe that’s just the folks I follow, tho.

Working on a series of reviews of various free/OSS tools for generating print-ready PDFs from HTML and CSS. First up is will be weasyprint. Can you guess which of these is which: latex, weasyprint, and Chrome/puppeteer?

A sample paragraph. The text is unimportant. What matters is that the word spacing on the second sample is absolutely horrible

“Heading off confusion: When do headings fail WCAG? - TPGi”

People with smarphones: use all sorts of fancy software and machine learning to fake a shallow DoF.

Me with an expensive camera: deep focus everywhere! Sharp!

Also met one of the friendly neighbourhood cats A cat. Looks serious

Walk around the neighbourhood 3: not the only person on an autumn walk

Two people walk through Hveragerði's tiny park