Looks nice, but like almost all promising new UI toolkits accessibility is not even mentioned.
And then accessibility brings with it the integration with different OSes via disparate APIs, so it will take some effort to offer a cross-platform API to the library user.
You'll notice that Iced is not >= 1.0 yet, so you shouldn't expect it to be fully-baked.
Neat! I really like the Rust ethos of creating modular cross-platform adopters (e.g. winit, getrandom), and from a brief skim this seems to fit that model.
It’s out there, so whether you finish it, someone forks it, or it just serves as inspiration for another project, you’ve contributed.
When you have an accident waterskiing and end up on crutches, you'll be glad for the accessibilty of doors that open with a button press. When you poke your eye hiking and need to wear an eyepatch for a few weeks, a screen reader might not seem such a niche use case.
These are even kind of extreme examples: frankly, even stuff like dark mode that we take for granted at this point is an accommodation to how some people need or want to use their computers. Migraines are a good example of an (astonishingly) common condition that benefits from flexibility around having to stare at a screen.
None of us gets younger as the days go by, either, and that comes with changed needs. I'm still thirty years from retirement and I find that the 10 point font I used to prefer isn't good enough anymore. Bumping up text size is a quotidian action for me and millions of other people.
ADDITION: Ah, finally found the quote I was looking for. Maybe not directly relevant, but thought-provoking:
> SMS texting was invented [to] figure out a way for deaf people to communicate with one another without speaking. ... Now text messages are universal.
https://blog.ai-media.tv/blog/why-designing-for-accessibilit...
I am person, who in last few days tried out to use VoiceOver and move responsibility on it to navigate me and read contents, when I could code while I had closed eyes. Ironically the most annoying interface was CLI, because I had to extend my focus on contents of the terminal. Imagine running docker-compose up and you are going to spammed with reading all logs. Next, usually I had problem to find some relative point that I could mark a "milestone" in my head, which will be further point from I will be reading.
Also, not all commands are read after executing them. Such command is silly pwd. Everytime I write it down I had to move the VO cursor to read the contents. Also many characters I would recognize as a programmer VO reads differently. Nano editor was complete unusable for me. While in vim I had notable problem to recognize indentations characters (sometimes they are read and sometimes they don't) and to know in what mode am I actually. brew update+upgrade was a nightmare for me. All kind of separators like #### are read as "number", "number" spam. The same situation was with "clear" command. It was read a hundreds of "space", "space", "space"... I was starting to think I am going to the Moon or I play Portal 2 [0].
I could continue writing down my disappointment about the CLI interface that was among my favorites in past but now after this week with VoiceOver I think it is terrible to be blind, because most of time I had to use my eyes to help myself to recognize where I am and what I need to click to move to next element. I was very surprised by the rofi-like find of elements that are on the screen (named as Rotor feature, CapsLock+U). With VO I don't any longer needed to use mouse, which for anybody who has problem with wrists is also a nice thing to consider.