Accessibility, usability, design systems, performance and progressive enhancement. Design Manager @ Workday. Views are my own. @therealkimblim@mastodon.coffee

København, Danmark
Joined March 2010
Next week Tuesday, January 31, I'm doing another Smashing Hour with @vitalyf ⏰ Free for everyone, so join us? 👇 smashed.by/smashinghour
1
4
21
5,760
Dear @filamentgroup — is there any chance you can revive your RSS feed?
74
I shouldn't laugh, but come on...
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
Question for my #a11y friends: is the <dialog> element ready for use if I want to create a modal? It seems to work with keyboard navigation and VoiceOver, but I don't have access to NVDA/Jaws right now, so can't test. Please retweet.
1
1
What's the one attribute/element/trick that most people don't know about HTML? All answers are welcome...
I've just installed @ShellFishApp for MacOS and absolutely love it. Worth every penny (that I had already paid for the iOS app). Go Get!
2
My reason: @codepen is a "drafts" folder for me. A place where I can instantly try something out without having to deal with NPM packages, Browsersync, git etc. — it's development without the tooling chain.
Howdy folks, co-founder of @CodePen here. 🤘 Why would you, fellow front-end designer & developer, want a CodePen account? Well it’s my job to make sure that has a clear answer, so I’m gonna thread 🧵 it up for ya to explore and understand.
Hey #a11y tweeps — I haven't been keeping an eye on <dialog> progress, but can see that it's supported by all modern browsers now. Is it actually accessible as well, or should we keep using polyfills/libraries?
Day 1 of me Day 3 of me debugging debugging the issue: the issue:
20
796
55
6,061
Just to be clear: I was not referring to myself here. Sure, I'll add my opinion on stuff, but I was talking about the "originators" who helped push web standards back in the days and continue to do so today — people like @zeldman, @meyerweb, @adactio etc.
Replying to @overflowhidden
Another note: please listen to some of the experienced people who have been along for most of this journey. I dare you to find many of those people, who agreed that CSS-in-JS was a good idea in the first place. Yes, it solved a problem, but it solved it in a bad way.
If I had a blog, I would write a long blog post about this article, but now it's only going to be a few tweets instead. The blog post in question: dev.to/srmagura/why-were-bre…
1
2
11
Another note: please listen to some of the experienced people who have been along for most of this journey. I dare you to find many of those people, who agreed that CSS-in-JS was a good idea in the first place. Yes, it solved a problem, but it solved it in a bad way.
1
2
15
That's it. Thanks for coming to my TED Talk. Now, I'm off to write some HTML/CSS/JS, which I still love doing after all these years.
1
6
My career in a sentence: It's all about the HTML folks!
Replying to @chriscoyier
Like Eric points out here, accessibility testing tools are throwing a ton of fouls. xitter.cf/ericwbailey/status/156… Looks like a lot of it can be cleaned up with some HTML work. It's all about the HTML folks!
I'm playing around with speechSynthesis and can't get it to work in Safari (MacOS) — anyone able to see what I'm doing wrong here: codepen.io/kimblim/pen/yLjJW… (Works fine in Firefox and Edge.) #SpeechSynthesis #JS
1
2