After reading these medium term goals, I'm honestly glad I stopped donating because I know some corporate thing will sponsor them now they will/want to add AI, even an AI Chat bot, to NVDA.

The below are just 2, but there's more AI stuff they have planned.

• Integrated AI image description: Free, secure, performant, private and VI-focussed on-device AI image description available out of the box.
• Help chatbot prototype: Exploring the development of an AI-powered chatbot to provide instant support and answer frequently asked questions about NVDA.

The second one is particularly nonsensical.

empyreanriders.com/feed/ #NVDA #AI #AIHype

in reply to Robert Kingett

They're things we're looking at exploring - they may or may not work out. And they're things we've been asked about repeatedly by USERS, not things we're doing to attract sponsorship. There are a handful of AI image description add-ons already, and have been for over five years. And as with any other functions, they would be there for those who wanted them, and can be ignored if not desired :)

1/2

in reply to NV Access

2/2 Aside from the "A large corporate will buy them out and push their own interests" concern (not possible due to the way NV Access is structured & overseen by a board who would prevent that) - what is your worry with image description and a chatbot which scours the user guide for you? (ITo be clear, such functionality wouldn't replace the existing documentation / training material etc)
Unknown parent

mastodon - Link to source

NV Access

The impetus for doing any of this is 100% user wants, not corporate sponsorship. Re the chat bot, yes I tend to feel the same, I'd rather refer to the manual or material - but others (probably younger than me!) like the chat bot style - so it's worth looking into. With Image recognition, like the existing add-ons, the intent would be "something is better than nothing" - not to replace people writing proper alt text - and yes, licensing of any AI model would be a key consideration
in reply to NV Access

@NVAccess Not to mention instances where the expectation isn't that good alt-text should be written, but the app should be accessible from a usability standpoint, but very much isn't. But waiting on the app to become accessible isn't an option since the thing you're trying to do with *insert inacccessible app here* can't wait. But before you ask for some sighted assistance you'd like to at least get an idea of what's on the screen so you know what to ask for.