Anselm Hannemann

@helloanselm
717 Followers
380 Following
533 Posts

Frontend lead / Engineering manager. Can help you with accessibility, scaling your product or your teams.
Open for freelance work!

In the past: Author of wdrl.info, Co-founder of Colloq.io, co-founder opendevicelab.com, co-host of Nightlybuild.io, Workingdraft.de podcast-host.

My Websitehttps://helloanselm.com/
Writer of WDRLhttps://wdrl.info/
What I love#Accessibility, effective teams, valuable products, organic farming, coffee and woodworking.
I’m specializing in#frontend, #accessibility, #CSS, #agile, #WebPerf

RE: https://front-end.social/@stefan/116765842145240238

This is amazing, can’t wait to have it

TIL recap: Did you know that incorrectly applied ARIA roles can nuke semantics entirely? The standard rule applies: if you're reaching for ARIA, make sure you know what you're doing.

https://www.stefanjudis.com/today-i-learned/aria-roles-can-remove-their-childrens-semantics/

For some UI elements closing behavior should be built in. A modal closes on `ESC`, but on mobile a native gesture (e.g. Android's swipe) can jump the browser back into history. How do you catch these? That's what `CloseWatcher` is for.

https://developer.mozilla.org/en-US/docs/Web/API/CloseWatcher

@webrocker wenn ich die crawler aussperre, sagt die KI meine Seite ist nicht erreichbar. Und das finden Recruiter und potentielle Kunden nicht so toll. Also schon gefangen in der Bubble.
@webrocker @webfussel meine Gedanken! Ich denke in 5 Jahren sieht alles anders aus, selbst wenn AI alles so bleibt. Aber bis dahin wird’s zäh.

TIL Firefox and Safari ship "quirks files" with site-specific fixes for sites that break in their browsers.

Thanks to Chrome's monopoly, testing in other browsers is often forgotten. And if things don't work, blame goes to the browser.

https://denodell.com/blog/browsers-treat-big-sites-differently

Browsers Treat Big Sites Differently

Safari and Firefox change how big sites render based on the domain. TikTok, Netflix, Instagram… even SeatGuru. Chrome doesn’t. Why is that?

Den Odell

The current state of AccentColor/AccentColorText:
4 browsers, 4 different color pairs

From left to right: Chrome 148 (stable), Chrome 150 (canary), Safari, Firefox.

- No browser uses the actual accent-color value (Sep 2025 spec change)
- Chrome removed support, but is re-adding it with a hardcoded blue and automatic AccentColorText
- Safari hardcodes blue and seems to always resolve AccentColorText to black? Yikes.
- Firefox actually uses my OS accent color and automatic AccentColorText

This is super sad!

https://2ality.com

I wish you good luck with finding new path @rauschma and I wanted to thank you for your contributions and sharing your knowledge for the past years. I learned a lot from you!

Thanks you.

2ality blog: temporarily offline

GitLab Act 2

A letter to our customers and our investors.

GitLab

Here's a strange situation:

thousands of #Rust developers use #bacon, #broot, #dysk, or #lazy-regex every single day — tools I wrote, maintain, and improve for free.

Their companies, though? None of them want to hire their author.

If you use my tools at work and your company does #Rust, I'd really appreciate a hand landing a job or freelance mission. A boost goes a long way. 🙏🦀

https://dystroy.org

dystroy

dystroy - Rust consulting