Yes, I would say this is harsh.

Primarily because OP actually did call out accessibility as a concern. That is the opposite of teaching the reader to ignore people who use a11y features. Nor is it OP's responsibility to teach their readers anything they don't care to.

And yeah, where are the tutorials you'd like to see? That could have been a more constructive thing for you to share yourself instead of demanding it from no one in particular.

It's unfortunate that accessibility is so often neglected, but at the same time this tutorial seems to be more about the basic concepts of how a UI library works, not a complete overview of every aspect.

They also didn't include text rendering for scripts that are written right-to-left, nor for scripts that are written vertically, and that affects far more people than those who use screen readers.

Clearly they are not intending to provide a complete and comprehensive course on every aspect of the ideal UI library.

Please can you post a link to your own tutorial on this?

You're being unfair and need to get off your high horse or your wheelchair. I'm sure the accessibility can be iterated upon the basics of UI, not have to rewrite the whole thing from scratch; this tutorial only covers the basics, can't blame OP for that.

Rather, why don't you make your comment constructive and tell us about accessibility? I am sure there is an "accessibility for noobs" tutorial out there that the rest of us haven't discovered. I, for one, just recently learned about colour blindness in games and was absolutely mad when I saw what the example game in the book looks like to a colour-blind person. Not that I'm much of a designer, but I'll be sure to choose a universally-good colour palette next time I do any UI. So teach us instead of yelling at us.

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.

I don't know if you're harsh, but one thing I've thought before I've clicked the link was "oh, another gui toolkit reinvention, I wonder how many times it will reinvent what's already invented and how many already solved problems it will simply ignore".

Well, I guess accessibility is one thing it skipped. It's a huge topic, I admit, so I'm not particularily surprised, but I think a better way for the author of this series would be to promote already existing huge toolkits that do have lots of functionalities built-in, including accessibility, like Qt for example.

That would be good also because already established huge toolkits have already answered a lot of important questions, questions which "modern" GUI toolkits simply ignore. New generations won't even know what we had when we were young.

[dead]