Archive

This is everything I posted in: thoughts

Why it's good for users that HTML, CSS and JS are separate languages on 25 November 2020

A response to an idea to merge HTML, CSS and JavaScript into one language.
22281 on 07 July 2020

My browser blocked 22281 trackers since July, 2019.
Minimum Viable Data Collection on 09 March 2020

What if more website-owners used Minimum Viable Data Collection as their strategy for complying with privacy regulations?
More accessible defaults, please! on 01 March 2020

Useful HTML elements like date inputs and <video> could make the web a much better place, if browser accessibility bugs in their implementations were prioritised.
Could browsers fix more accessibility problems automatically? on 04 February 2020

Let’s explore which accessibility issues browsers could fix automatically!
Meaning without markup: Accessibility Object Model on 22 July 2019

Proposals for the Accessibility Object Model include a new way to convey semantics: without markup, directly in JavaScript. This post looks at the proposals and their current status.
Baking accessibility into components: how frameworks help on 24 May 2019

Some thoughts on seeing declarative component frameworks as a way to make the web more accessible, not less.
Component frameworks and web standards on 28 February 2019

Are component frameworks at odds with a vanilla approach to web development? Well, partly, but not as much as I used to think. Some thoughts after I tried a framework.
Content-based grid tracks and embracing flexibility on 23 February 2019

A bit about designing min-content, max-content and auto, and how they can be used.
Three ways to build Crouwel's Hiroshima poster in CSS on 31 January 2019

Recreating old posters, I figured there are at least two approaches to deciding how many grid tracks your component or page needs: one can make it visually perfect, the other is more flexible if content is bound to change.