[kvuj]

I think you're being disingenuous. The author could have made this tutorial for the 90% of people that do not have these concerns. Time isn't free and projects people work on in their spare time shouldn't have these snarky comments in response.

> Am I being harsh? Well where's the tutorial that teaches people how to do it properly? Where do people actually learn the right way if not here?

I would love to read your blog post on how to do so! After all, since you seem to imply that time is free for everyone, you shouldn't have any problem making that blog post.

[robin_reala]

Leaving accessibility out of an UI library tutorial is like leaving security out of an API tutorial. It’s perfectly possible to build something that’s probably not a problem if you’re building a toy application, but if you haven’t done it right from the start it will absolutely bite you hard, and it’ll broadly be quicker to start over from scratch than try to fix the mess.

[ctoth]

The math: There are N tutorials written per year. There are M accessibility experts willing and able to write tutorials. N >> M by orders of magnitude. The ask is for M people to produce N parallel accessible versions of everything, forever, as a prerequisite for being allowed to point out the gap exists.

[poly2it]

This doesn't make sense. Why do M people need to write N accessibility tutorials to point out the gap in accessibility support? The same isn't true for localisation for example.