Re our AI note

I consider the below useful to our note. It comes from the Humanware
Evolve list.


-- 

Janina Sajka (she/her)
https://linkedin.com/in/jsajka

Digital Accessibility Standards Lead,
Level Access https://www.levelaccess.com/

W3C Accessible Platform Architectures	(APA) CoChair,
http://www.w3.org/wai/apa

Linux Foundation Fellow
https://www.linuxfoundation.org/about/leadership#team-bio-janina-sajka

Forwarded message 1

  • From: Joseph Lee via groups.io <joseph.lee22590=gmail.com@groups.io>
  • Date: Wed, 16 Sep 2026 07:13:38 -0700
  • Subject: Re: [evolve] Updating NVDA
  • To: evolve@braillenote.groups.io
  • Message-ID: <546192.1789568018633048408@groups.io>
Hi,

Remember that Vispero releases major JAWS releases annually, and things can change between releases (such as changes to the scripting language or the infrastructure). We will see what JAWS 2027 brings in a month or two.

As for NVDA, I wonder what the adopted version of 2026.2 will look like. For the Evolve, the biggest change is automatic braille scrolling, and I hope HumanWare is working on ways to integrate this with KeySoft in a smooth way (automatic braille scrolling is a work of another third-party contributor). Considering the target audience of the evolve (or at least marketed as a tool for education), I understand the appeal of reading digital content like textbooks on a braille display without having to press thumb keys all the time.

Additionally, NV Access and the larger NVDA community is still figuring out how to deal with AI generated code spam. In recent months (as in June onwards), NV Access has received patch proposals (pull requests) with issues such as no manual testing plan. NV Access banned a couple of patch submitters after these submitters did not follow AI usage guidelines from NV Access (human review for patches by submitters themselves); at least one of the banned submitters admitted to not testing NVDA changes on their computers including building the screen reader from source code. Then in August, a huge debate occurred on the NVDA community regarding vibe coding of NVDA add-ons.

I mention these series of events, particular AI and coding for several reasons:

1. Adoption of AI in software development: people used AI to write NVDA patches and add-ons to mixed success. If one screen reader community is dealing with AI and coding, I imagine it will be applicable to other screen readers. While people don't talk about it a lot, I imagine Vispero is using AI in some capacity to code JAWS. I also imagine some would prompt chatbots to generate JAWS scripts.
2. HumanWare and AI: building from above, I imagine HumanWare is employing generative and/or agentic AI for part of their coding work. If yes, then I do foresee a moment in time in a not so distant future where HumanWare will prompt an AI system to write a series of NVDA patches to bring their fork of NVDA in line with the vanilla (official) version from NV Access to fulfill a community promise: contribute back to the NVDA community. I hope HumanWare people will review AI output thoroughly because one wrong code path can negatively affect BrailleNote Evolve's reputation.

Cheers,

Jsoeph


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#754): https://braillenote.groups.io/g/evolve/message/754
Mute This Topic: https://groups.io/mt/121255128/1676285
Group Owner: evolve+owner@braillenote.groups.io
Unsubscribe: https://braillenote.groups.io/g/evolve/leave/15334472/1676285/382061527/xyzzy [janina@a11y.nyc]
-=-=-=-=-=-=-=-=-=-=-=-

Received on Thursday, 17 September 2026 16:01:14 UTC