James Please

Thanks for the issue @Muhnad ! We are _definitely_ open to making changes to make the components more accessible. In general, my approach would be to value accessibility _over_ making...

Cross-referencing this with #253 . One of the goals before the v1.0.0 release is to improve accessibility.

We have it in a [few places](https://github.com/jamesplease/materialish/blob/c908684b1481e0e7dad381ef27f4c5400d767bab/src/button/button.css#L12). I'd be open to adding it to more places. //cc @JPorry

To be completely honest, I haven't put _any_ thought into what that component will look like yet. We plan to build a "basic" dropdown first, to keep the problem space...

Closing for now. This is blocked due to Google not updating their icons repository. https://github.com/google/material-design-icons/issues/786

To get all of the icons, we could write a scraper that pulls the names somewhere, and then scrapes them from URLs of [this format](https://material.io/tools/icons/static/icons/sharp-accessible_forward-24px.svg).

Reopening. I've begun work on this over [here](https://github.com/jamesplease/material-design-icons)

Note: this could _still_ support changes derived from the previous state. Imagine this API: ```js disableThing = () => { return { active: false } } ``` or... ``` toggleThing...

Won’t be able to look into this for a few months (spring 2024), sorry!

Closing, sorry won’t fix this.