claviska

They rejected mine too for the exact same reason, despite press-to-talk being a legitimate accessibility issue.

I wrote about this here [1], and even called out some of the most common disabilities that clearly benefit from it.

They also don’t allow microphone access from keyboard extensions in iOS, which prevented me from shipping an iPhone target (that I really wanted for myself tbh).

It’s a shame and I can only assume they’re trying to protect their built-in dictation, which historically has been laughably bad.

[1] https://tonguetype.app/accessibility

Thank you! For the components, I use the Custom Elements Manifest Analyzer to get data from JSDoc comments and TypeScript. This populates properties, events, methods, slots, etc. All the examples and other pages are hand-made. Docs are generated with 11ty.

Thanks! I’ll look into this.

I launched Quiet UI this week:

https://quietui.org/

It prioritizes accessibility, longevity, performance, and simplicity.

With the autoloader, one script tag loads components dynamically without downloading the entire library. (npm also available.)

Theming uses color-mix() and OKLAB to create uniform color palettes from a single CSS property. Adaptive palettes are used for dark mode.

All form controls are form-associated via ElementInternals and work with native validation APIs (required, pattern, etc.).

Dialogs, popovers, tooltips, etc. use Popover API for top-layer access without having to portal or hoist.

Some of the more fun components include: Joystick, Stamp, Mesh Gradient, Flip Card, Random Content, Intersection Observer, Typewriter, Lorem Ipsum, Slide Activator

The library is free for personal, educational, non-profit use. Commercial use requires a license.

Thank you! <3

I enjoy building components and exploring new concepts.

Oh, a secret admirer! Thank you <3

Shoelace has matured into Web Awesome and has a whole team behind it, as well as an attractive pro offering. Quiet is my creative outlet. Some components from Quiet have been adapted to Web Awesome, but many probably don't make sense to such as joystick, mesh gradient, stamp, etc.

The theming layers are completely different. Web Awesome's theming system is more robust, with over a dozen pro themes already available with interchangeable, professionally-curated palettes. In contrast, Quiet has just one theme with a palette that's generated with color-mix().

Oh, hey. I made that :D

I’ve been quietly working on this for the last two years. It started as a creative outlet and a way to discover and learn modern Web APIs. It ended up as an addiction.

I built Quiet from scratch to improve my design skills. To learn new APIs. To try different approaches that may or may not in my main focus, which is Web Awesome.

I learned so many new things building it. It let me explore newer APIs such as `color-mix()`, the Popover API, and Element Internals. It let me use newer CSS features such as `:has()` and nesting before they were baseline. It taught me about color, especially OKLAB and OKLCH, which is still a mysterious box of wonder, but slightly less intimidating now.

Quiet has given me the freedom to explore ideas that make me a better developer and designer, many of which would be out of scope for a more established product.

I’d love to hear what you think, and I'm happy to answer any questions!

Oh wow! I used this last year to generate the sound effects for https://rocketblaster.app/ and it gave it a great retro vibe.

I would imagine the subtle daily increase or decrease in daylight, even in extreme latitudes, is more natural and healthier than an immediate one hour shift in either direction.

I had a similar but more concerning experience. I enabled family sharing (years ago when it was newer) and suddenly my spouse had access to many (all?) of MY passwords in HER keychain. I never knowingly granted access or put any passwords in a non-personal group — it just happened like magic.

I loved mine. Found one at a yard sale as a kid (with the book!) and taught myself how to program with it. Eventually, I learned about QBASIC and my world — and love for programming — got so much bigger.

I hope they bring back goooooooooooogle

When the hard-working little swimmers encounter the thicker vaginal mucus, their path is slowed. So the sperm often join together at their heads, which gives them greater swimming speed (up to 50 percent faster) than if they were to carry on individually.

Teamwork makes the cream work.

This has been fixed in a PR that made it into React’s experimental release. They’ve been promising support since 16, but keep bumping it back. It’s now slated for React 19. You can read the discussion here. [0]

Per Dan’s comment [1], they began rolling out the flag to test support at Meta in February and, barring any major problems, they’re still targeting 19.

0: https://github.com/facebook/react/issues/11347

1: https://github.com/facebook/react/issues/11347#issuecomment-...

Check out Web Test Runner [0]. It uses Puppeteer to test in real browsers and is easy to setup. I test in Chromium, Firefox, and WebKit concurrently.

[0] https://modern-web.dev/docs/test-runner/overview/

The goal is to handle as much accessibility as possible with smart defaults and by making it easy for users to get right. Currently, all aria stuff is handled internally the components. For example, look at <sl-input> and you’ll see that the input, label, and help text are automatically linked in the shadow root. The minimum the user needs to provide is a label and assistive devices work as expected.

Creator of Shoelace [0] here. As someone who’s built multiple design systems and component libraries, I assure you that unstyled (or “headless”) components are often much more time consuming and painful to adopt than those with good default styles.

That said, I commonly find that most folks don’t want unstyled components because it’s quite a bit of work to style every single state of every single component. Most people just won’t do it or, if they try, they don’t do it right and they don’t do it completely.

What many folks do want are components that have simple, generic styles you can quickly tweak to match your site/app using a skill you already know: CSS. (This is something you can do with Shoelace’s 50+ web components already, but we’re working to make it even easier with additional CSS custom properties.)

[0] https://shoelace.style/

Years ago, I stupidly got rid of my entire South Park DVD collection because they were on Netflix. Until they eventually weren’t. Chris was right.

This started when people discovered they could style <input type=checkbox> to look like a switch with pure CSS. (And, as a component library author, I can confirm it continues because we, perhaps lazily, don’t bother implementing the slide.)

Huge plus one for Proraso. Absolutely the best shave of my life.

I’ve done this for a long time now. One keypad in front and another in back. I proactively change the batteries once a year. I also have a keypad for the garage. I haven’t carried a house key in years.

I appreciate the concept, but I can’t help but feel that the page is loading and getting “stuck” as I fill out the form. Probably a result of the many top bar-style page loaders, but still feels a bit awkward.

I appreciate the intent, and I understand that many people will do the wrong thing so this was probably an attempt to get such folks to actually read and adhere to the TOS, but the obnoxious consent dialog with a mandatory countdown turned me off. It’s probably not effective, either.

On desktop, maybe I’d open dev tools and remove it. On mobile, I won’t be bothered. I hate that this is what the web has become and I choose to simply miss out on websites that behave this way.

The author mentions:

I miss Away Messages. This nostalgia is layered in abstraction; I probably miss the newness of the internet of the 1990s, and I also miss just being … away.

The difference is that Slack has a mobile app so when you step away from your computer, you’re not really “away” like you used to be before smartphones were a thing.

Yes, you can disable notifications or try to ignore them, but that’s not the author’s point. I read it more as them longing for “a better time,” similar to an expression of nostalgia for the simplicity of one’s childhood.

Some of the best experiences of my childhood were learning how to code, which ultimately turned into a career that has opened up more opportunities and experiences than I would have known otherwise.

Came here to say this. The fake, automated voices are awful and make me immediately turn the video off.

Similar story, but with tea. I used to dump sugar into it but eventually I just stopped. Now I have plain black tea every morning. I really can’t stand drinking it with sugar now.

I also ditched soda (except for an occasional mixed drink) and when I want something cold and fizzy I pour a can of seltzer water with lime, orange, cherry, etc. It’s a game changer if you can kick the sugar habits.

They are both DOMTokenLists so parts look a lot like classes. The difference is parts are used in a shadow root to expose internal elements for styling. I’ve written a bit about CSS parts here: https://www.abeautifulsite.net/posts/when-to-create-css-part...