It's honestly shocking to me that there are humans in the world who are comfortable defending such evil with some perceived amusing fact from history. This is happening today! The killing of people in their thousands based on their ethnicity is happening today. There is no defence for that. It's not war, it is genocide.

That isn't some wild internet conspiracy theory, it is a consensus of genocide scholars.

But I guess you will go on with being "amused" at any argument about stolen land, even though there isn't a human on earth who's ancestors haven't done terrible things.

We should be better than that in the 21st century.

I do use ChatGPT to research things, but I don't usually see that as accessibility solution. I completely agree that screen readers and browsers would benefit from AI, as they already are; Chrome and Edge can generate missing image descriptions. AI can certainly enhance accessibility, but it can't replace the existing technology that already works quite well a lot of the time.

The other positive about AI for accessibility is that the frontier models have a good understanding of what works. Instead of learning all the guidelines, you can just ask an agent to review the page for accessibility and fix any problems.

I realise I am only looking at it from a screen reader point of view, and yes, we are quite a small minority. But good universal design helps everyone, whether they just need to zoom the page for comfort without it breaking, their eyes are not that of a young person, they have dexterity issues using a mouse, and many more. Accessibility in general isn't serving a tiny minority,. I imagine most of us will come to appreciate it in some way.

Not all accessibility tools are expensive:

   - NVDA is free and open source
   - Narrator is included with windows
   - Voiceover is included with macOS and iOS
   - Orca is free and open source.
   - Talkback comes with Android
   - Chromevox comes with Chrome OS

Thanks for considering a11y for your toolkit - it really makes a difference to those of us who are disabled. Are you implementing a11y separately for each platform? If you use accesskit[1] you only have to implement it once for all platforms. I recently vibe coded accessibility for the Swell toolkit[2] used by Reaper. I have a branch using accesskit and a branch implementing at-spi. Accesskit made things a lot easier and more performant.

Let me know if you would like a screen reader user to help with testing your toolkit.

[0] https://lwn.net/Articles/1025127/

[1] https://github.com/AccessKit/accesskit

[2] https://github.com/RDMurray/WDL/tree/accesskit

and my fork of accesskit with some features and fixes for unix: https://github.com/RDMurray/accesskit/tree/swell-fixes

If this includes improvements to the screen recognition feature in Voice Over, it could provide accessibility for apps where the developer doesn't care about accessibility, which is extremely common.

The vision capabilities could be useful if they are done well, but I suspect that will always be covered better by 3rd party apps.