I wrote an issue on the WCAG-github with a question about 1.4.11. The case is a solid-coloured logo used as a link, and if that would comply. I've mentioned this before, and now it's "official"
https://github.com/w3c/wcag/issues/4376
(Notice me writing 3∶1? Following the feedback I got!)
I'm fairly deep into QR-codes right now, and I'd like to share with you:
ChatGPT is -not- a QR-code reader. It can lie about QR-code specifics, including the URL it's supposed to send you
ChatGPT is always wonderful on first impression, and such an enormous disappointment when verifying its slop 😰
But Erik, issues from rescaling a website? Isn't that like a... pre-mobile web kind of thing?
Meanwhile, one of the most popular plugins (Google Site Kit), on the most popular platform (Wordpress):
Representation ♥️
@erikKroes 3∶1. No unnecessary decimals. Also proper ratio (∶) sign instead of a colon (:).
For better or worse, I’ve ended up as the unofficial owner of IKEA’s digital font implementation, so I’ve written up the six-year journey to the current setup of Noto IKEA: https://medium.com/flat-pack-tech/ikeas-web-fonts-8e3879f4ccbb
I strongly dislike being a gatekeeper. But I think only Dutch people understand how wonderful it is to get this -water bottle- as a birthday gift.
Unusual thought of the day... of the moment.
WCAG 2.5.8:
> The size of the target for pointer inputs is at least 24 by 24 CSS pixels
How does that apply to skip links? 🤔
Ah, a new “WCAG in Plain English” resource that is neither WCAG nor “in Plain English”.
It’s reformulation of WCAG understanding pages just in a way so that it’s misleading or confusing.
How useful!
Blessed are those who browse in English, for they have not wade through AI-translations.
When writing about contrast, what do you write?
- 3:1
- 3.0:1
- 3.00:1
- Something else?
(And why?)
#accessibility #wcag
A new meetup has been scheduled! 🥳
16th of April in Amsterdam. Nienke de Keijzer will present, and I'll share some practical fixes for common WCAG failures. Put it in your agenda!
https://www.meetup.com/inclusive-design-accessibility/events/307149158/
"You can do anything you set your mind to"
🤔
Guess who got an injury after going running three times?
I'm using an hgroup-element. Come at me.
An automated accessibility scan of 1 million websites. It teaches you more than scanning any individual website ever could. So very insightful!
Accessibility-santa doesn't spread gifts. We get the WebAIM Million yearly. And that might be even better.
Today I learned my kid that hands out sticks to kids in lower grades, because their school yard lacks them.
Proud and amused. We all deserve proper sticks!
Where can I pick up a stamp for my parenting scorecard?
You no longer need a plugin for checking color contrast in Figma!
I love how so many tools have these checks integrated. No plugins, extensions or anything else needed!
Couch to 5k attempt... 4?
Week 1 completed! 🚀
https://connect.garmin.com/modern/profile/ab073d18-8ffb-46ab-87e9-37952d6f9970
Musical running tip!
- Most dance/trance is around 130BPM. That translates to a low cadence
- Happy hardcore/gabber is mostly around 160BPM, much better already
- Want a higher cadence? Modern hardstyle and drum'n'bass do well for 170BPM!
(Yes, I have a playlist with 170 BPM songs for running 🚀)
For the last few weeks, I’ve been analysing almost 600 front-end and full-stack job openings to learn about which technologies are in demand and valued, how many years of experience is required, whether we need a degree, whether or not companies care about accessibility and DEI, and more.
It was a ton of work, so I’m very happy to wrap things up with a blog post where I share all my findings: https://tsev.dev/posts/2025-03-26-the-state-of-the-frontend-and-fullstack-job-market