Joseph Lee

Software development is a form of communication. Grad student, speech coach, pianist, member of the NVDA, CSULA comm-ma, CU-CMDI comm-phd student communities.

[Joseph Lee @joslee]

#NVDASR guide: porting add-ons to 64-bit NVDA (2026.1): [email protected] | Guide: how to port add-ons to 64-bit NVDA @nvaccess #nvdaaddons

[Joseph Lee @joslee]

Build 26x20.6682 and later: installed copy of #NVDASR starts without UI Access privilege: https://t.co/lSNlHlfPDW

[Joseph Lee @joslee]

@seeingwithsound @NVAccess Hi, the task is done (NVDA 2025.x compatible AudioScreen, requires NVDA 2024.1 or later): https://t.co/SxBfh7XfDi

[Joseph Lee @joslee]

@seeingwithsound @NVAccess For libaudioverse, this means someone must write code to let 64-bit NVDA work with 32-bit DLL's, and this requires using a dedicated program (executable) for that.

[Joseph Lee @joslee]

@seeingwithsound @NVAccess One strategy adopted in recent years is to leave these commands unassignes. NvDA users can add custom keyboard commands (or touch commands) via input gestures dialog in NVDA.

[Joseph Lee @joslee]

@seeingwithsound @NVAccess NVDA is licensed under GPL 2 (there is an ongoing conversation to update to "GPL 2 or later"), and most add-ons are released under GPL 2. As for keyboard commands, you can look at commands quick reference.

[Joseph Lee @joslee]

@seeingwithsound @NVAccess For now, I think a quick code review should get folks on NVDA add-ons list going (due to life priorities, I cannot fork and update this add-on myself, but hope that my initial quick code review gave some folks a sense of direction).

[Joseph Lee @joslee]

@seeingwithsound @NVAccess Probably not for a while as he is working on a number of higher priority work (including reviewing 64-bit transition). I have done a quick code review, and suffice to say that it will take a while before 2025.x compatible release might be ready.

[Joseph Lee @joslee]

@seeingwithsound @NVAccess I see- thanks for the reminder (we should also discuss code cleanup and other topics there).b

[Joseph Lee @joslee]

@seeingwithsound @NVAccess Hi, I think it would be a good idea to check for keyboard command conflict as two of them (NVDA+Shift+A and Control+NVDA+A) conflict with existing NVDA commands. Thanks for updating the add-on.

[Joseph Lee @joslee]

Notice link: https://t.co/uFSMZlf2ga

[Joseph Lee @joslee]

IMPORTANT #NVDASR add-ons notice: Office Desk 25.09 (add-on end of life): Office Desk 25.09 (IMPORTANT: add-on end of life)

[NV Access @NVAccess]

NV Access is pleased to announce that version 2025.2 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

Full info & Download at: https://t.co/JnrPxjt0Tr

#NVDA #NVDAsr #ScreenReader #A11y

[Joseph Lee @joslee]

It's a source code change - affected synthesizer drivers continue to think that output device is part of speech settings. Thus, source code for these add-ons must be edited; in other words, manual manifest edits (no longer recommended) or forcefully enabling add-ons will fail. 5/

[Joseph Lee @joslee]

Writing in response to https://t.co/97yObuu71k 1/

[Joseph Lee @joslee]

The big reason: the location of speech output device setting has changed in NVDA configuration database. In NVDA 2024.4.2, output device was part of speech settings, but with 2025.1, this has moved to audio settings. This affects speech synth add-ons, specifically source code. 4/

[NV Access @NVAccess]

NV Access is pleased to announce that version 2025.1 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

Full info & Download: https://t.co/tdpatuLk2d

#NVDA #NVDAsr #ScreenReader #Accessibility