Emil Björklund

@thatemil@front-end.social
22 Followers
59 Following
13 Posts

Living in a small village on a large island off the east coast of a medium-sized country.

Building webby stuff. Into CSS, accessibility, humanity.

Currently working as tech lead for a team at Bonnier News.

Websitehttps://thatemil.com
Pronounshe/him
Heading into town in a minute with @paulrobertlloyd, aiming for Basketmakers Arms or thereabouts. #PatternsDay @sturobson @dletorey
Sitting in Pelicano on Lewes Road. @sturobson
Heading out to some Brighton coffee shop with @paulrobertlloyd . More on this story as it develops!
Heading to Brighton for #PatternsDay. Travel jitters aplenty, seem to have multiplied since having a kid.

Opening the door of an unknown pub, full of the people you used to drink with at The Ol’ Bird Site until it turned into a cesspool.

Some are friends, some feel like friends ’cause you’ve heard all their stories about their lives, but are often just aquaintances, or don’t know your name. Many you haven’t seen in years.

Anyway, you tip your hat here and there, sometimes geta tip of the hat back, or a ”hey buddy, cool to see you here too”. You sit down to mostly listen, older now, and sober-ish.

Okay, here is my take on Nielsen's latest post.

"Accessibility has failed as a way to make computers usable for disabled users." Thus begins a newsletter by Jakob Nielsen. And had it not been written by someone a great many people take seriously in the UX industry I likely would just have dismissed it. But seeing how harmful I consider the post to potentially be, I would like to nip this in the bud. My reflection is that the published post is misleading, self-contradictory and underhanded. I'll walk you through the whole of it and provide my commentary and reasoning. 👇

https://axbom.com/nielsen-generative-ui-failure/

#accessibility #a11y #ux
On Nielsen's ideas about generative UI for resolving accessibility

"Accessibility has failed as a way to make computers usable for disabled users." Thus begins a newsletter by Jakob Nielsen. And had it not been written by someone a great many people take seriously in the UX industry I likely would just have dismissed it. But seeing how harmful I

Axbom • Digital Compassion
I have a question: why are pretty much all published web components insisting on both defining and registering the class, including element name, at the same time? Why not export the JS class and let authors decide what element to register it as? Why not offer a default, but allow authors to change it?
Time for an #introduction, new instance and all. I’m Emil, I’m from Sweden, where I live with my family –my partner, our son and our 7/8ths Maine Coon cat. I do web stuff during working hours, unsurprisingly front end-y web stuff to a large degree. I once wrote a 500-page book on CSS, for example. I also care deeply about accessibility, and try very actively to become better at it. I’ve been missing the community of pre-2016-or-so Twitter, hope this network can give me some of that back.