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.
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.
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.
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().
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!
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 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