Feels as if the real achievement were the team behind the initiative, while the product itself is “just” a positive side-effect 😄
30.01.2026 08:12
👍 2
🔁 0
💬 0
📌 1
Feels as if the real achievement were the team behind the initiative, while the product itself is “just” a positive side-effect 😄
Fascinating! Imagine the impact this could make on accessibility if all the semantics are wired up correctly.
The only prop I couldn’t wrap my head around was `$mix={15}` 😅
Imagine following AI advice without a second opinion for the sake of “compliance” to avoid legal fines.
I heard about a company having an enthusiastic blind customer reaching out about a11y issues. A coworker proposed hiring them. Sadly, the firm rather contracted an infamous a11y company instead.
At Wise we had plenty of internal presentations on how the majority of customer support inquiries can be resolved by AI agents
See also anti-fraud startups like SEON or Fingerprint, both of which use AI in their core pattern matching algos
Perhaps the lack of publicity is for ensuring compliance?
It tells a lot that their flagship campaign slogan ‘the safe choice’ leaked and so the opposition registered the corresponding domain biztosvalasztas.hu, despite Fidesz trying to cope in digital spaces. Funnily enough the opposition even filed a patent for the slogan above to benefit from propaganda
So far so good! The name choice might be a bit of a stretch considering the small amount of authors the project was influenced by.
I have my own flavor based upon the comparison of UA stylesheets if interested: github.com/kripod/css-h...
Looks neat! Keep up the great work 🙌
Today marks the first illegal Budapest Pride march 🏳️🌈 🇭🇺
Just a reminder how brittle democracy can be, despite the citizens becoming more inclusive over time. Evil triumphs when the good do nothing…
Styling HTML form controls is something web designers & developers have wanted for years! My team is working on a solution — apply `appearance: base` and switch to a new interoperable consistent default control. Then override it using new pseudo-elements. See the details: drafts.csswg.org/css-forms/
Could be a coincidence but ‘Réka’ is also a Hungarian given name for females 😄
Here's the math needed to adjust a color's lightness and eliminate the gray area where WCAG2 and APCA conflict on black/white foregrounds.
Yes, it's CSS. And yes, it's blazingly fast.
Usage:
background: oklch(from <color> var(--_ak-safe-l) c h);
There’s even an @eslint.org rule which prevents using labels in general but has the options ‘allowLoop’ and ‘allowSwitch’ to exempt those constructs: eslint.org/docs/latest/...
I agree. Just tried putting my thoughts more concisely, using a shorthand for ‘in my opinion’.
The answer here, like for most engineering problems, is ‘it depends’ 😄
Reduce should never be used with a non-primitive accumulator imo. We have more semantic alternatives like:
• Object.fromEntries() + entries.map()
• Object.groupBy() / Map.groupBy()
Even for primitives we’ll have Math.sumPrecise() soon ⏳ github.com/tc39/proposa...
Visually-hidden elements should be preferred over explicit labeling.
Despite being aware of that, I could never explain the “whys” before this article.
Had to use Safari for browsing the @npmjs.bsky.social ‘Versions’ tab of @astro.build
The ‘astro’ package has 1,000+ releases and the associated page just froze while searching on Chrome: www.npmjs.com/package/astr...
Perhaps the ‘content-visibility’ CSS property could help? web.dev/articles/con...
It was all fun until missing the flagpole top in the invisible bit of “that” level 🙃
Just upgraded kripod.dev to Astro v5. While the migration took some effort, I could pull it off in one go thankfully to the well-written guidelines. It took less than an hour, running stronger than ever 🚀
Literal unions ("a" | "b") are a thing while literal intersections aren’t 😅 The former has a certain ring to it, I hope that might help.
Also, @joshwcomeau.com wrote extensive guidance on the subtleties of px vs. rem www.joshwcomeau.com/css/surprisi...
‘Reflow’ deserves more spotlight as a WCAG criterion.
Visitors of a website should be able to browse content comfortably on a 320×256px viewport. That equals 400% zoom on a 1280×1024px screen but such an enlargement may also consist of 200% text-only + 200% UI zoom. www.w3.org/WAI/WCAG22/U...
I wish the @tailwindcss.com will revise some changes before releasing v4, especially concerning accessibility. It’s such a responsibility to get things right at their scale.
Perhaps advanced features like breaking out of atomicity might be put behind a flag or at least discouraged by the docs? 🤔
I wish more rules had convenient defaults nudging us to write better code 😄 (some are just a matter of preference, though) github.com/kripod/eslin...
That’s also why I use the ‘always’ option in my own linter config: github.com/kripod/eslin...
That isn’t exactly the case as typescript-eslint’s docs refer to this example on MDN which throws an error asynchronously. The `await null` line makes a difference for the stack trace: developer.mozilla.org/en-US/docs/W...
I never really found an ESLint config that’s fairly strict without going overboard
So I went through hundreds of core + @typescript-eslint.io rules 1 by 1, hand-picking the severity and options for each. This project culminates all my years of experience with JS/TS so far github.com/kripod/eslin...
Guess who got lucky today, @jamie.build 😄 bsky.app/profile/jami...
The deterministic nature of feeds here feels underappreciated in comparison to X. Finally I don’t lose track of where I’ve been when refreshing.
I wish there was a catch-up marker splitting read and unread posts apart, like on Slack.
Great article, thanks for the idea 🙌
I also have my own reset built upon the line-by-line comparison of user-agent stylesheets: github.com/kripod/css-h...
