Kim Johannesen
@overflowhidden
Accessibility, usability, design systems, performance and progressive enhancement. Design Manager @ Workday. Views are my own. @[email protected]
You might like
I've moved to Mastodon and won't be posting here for the foreseeable future. mastodon.coffee/@therealkimblim
Next week Tuesday, January 31, I'm doing another Smashing Hour with @vitalyf ⏰ Free for everyone, so join us? 👇 smashed.by/smashinghour
Dear @filamentgroup — is there any chance you can revive your RSS feed?
I shouldn't laugh, but come on...
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.
What's the one attribute/element/trick that most people don't know about HTML? All answers are welcome...
Are you on Mastodon yet? Let me know so I can follow you :) (and you can follow me: mastodon.coffee/@therealkimblim)
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!
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:
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.
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.
My career in a sentence: It's all about the HTML folks!
Like Eric points out here, accessibility testing tools are throwing a ton of fouls. 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/yL… (Works fine in Firefox and Edge.) #SpeechSynthesis #JS
United States Trends
- 1. Kevin James 1,531 posts
- 2. Bubba 25.9K posts
- 3. Bill Clinton 109K posts
- 4. RIP Coach Beam N/A
- 5. #BravoCon 3,760 posts
- 6. #CashAppGreen 1,295 posts
- 7. Hunter Biden 18.4K posts
- 8. Last Chance U 2,874 posts
- 9. Hayley 18.2K posts
- 10. Metroid 9,940 posts
- 11. Wale 45.8K posts
- 12. Crooks 76.6K posts
- 13. Vatican 14K posts
- 14. Jack Hughes N/A
- 15. Rondo 2,635 posts
- 16. Paul Blart N/A
- 17. Jaylon Johnson 2,268 posts
- 18. Zverev 2,626 posts
- 19. Matt Taylor 1,645 posts
- 20. Oakland 7,179 posts
You might like
Something went wrong.
Something went wrong.