We have the basics (exposing an accessibility tree that is visible to screen readers, a keyboard controllable focus system). There's a lot more work to do be done to make it work well (but that's also true of Blitz in general).

We're building upon https://github.com/AccessKit/accesskit which provides a cross-platform abstraction over the OS accessibility APIs.

Hi, lead AccessKit developer here. Thanks for prioritizing accessibility even at this fairly early stage of the project.

Thanks for building AccessKit and making this so much easier for us!

From the readme: "Blitz builds upon: [...] AccessKit for accessibility"

Why are you so hostile?

I think the hostility is understandable when you consider that blind and other disabled people, like myself (I'm partially blind) and the poster of that comment, live every day having to work around widespread indifference toward our needs. I'm not immune to it myself; see some of my older HN comments on GUI toolkit accessibility, before I started AccessKit.

Most newer GUI libraries entirely neglect accessibility and focus exclusively on rendering. Maybe accessibility is seen as too much effort for too little gain?

It's kind like most CLI programs nowadays don't come with a man page (nor an info page) and think that an autogenerated `--help` is enough. Except that nobody is excluded from using your application just because it doesn't come with proper documentation