@vgjh2005: Would you be able to reword your initial comment a bit? I'm afraid I don't completely understand what you were trying to say.

Hi:
My meaning is that support mouse wheel controlling with keyboard. The second thing is enable to set two point ( a start point and an end point) to drag down the mouse from those point with mouse clicking.

Windows has a feature called mouse keys which allows you to control the mouse with the keyboard. Furthermore, you can route and click and hold the mouse with NVDA, which allows you to drag and drop with the mouse. I still don't see why supporting a scroll wheel would be helpful. Scroll wheels aren't available on laptops, for example.

cc @Qchristensen, what do you think about this from a visual/low vision perspective?

Hi:
Actually, there are more scenes that will use the mouse click. NVDA can't do anything for those software that no content can be found and browsed in. For example native kontakt.
Windows mouse keyboard isn't used for blind. Because they don't know which place should be clicked. Or mouse is unuseless for those clickable scene. The reason is that we can use navigator object to insted of it. However, we just used to those scenes that can't be controlled. But for the blind, they don't know which place should be clicked in those unsupported software. So:

1. We need a function to remember the clickable place to perform some specific action. However, we need help from other people to help us locate them.
2. There are more software that can't use keyboard to scroll in the control, but mouse wheel is OK. For example, add external controller control just like this in samplitude.

Does golden cursor help with this at all?

Derek, no, golden cursor doesn't emulate or do anything with the mouse wheel. I must admit I'm not exactly sure what use case the original poster has in mind either?

You could use Windows' mouse keys to select and drag an item. The question then is, are there any situations where either the program in question or NVDA cannot provide a keyboard alternative, and if so, is it worth implementing our own version of it, over directing affected users to the Windows feature?

Hi:
I have tried the add-on Golden cursor. Quesstion is that possition of it is based on the screen, if the window is moved, and the remembered possition is unuseful.
It need to remember the possition based on the window edge.
Second, I think windows mouse key is unuseful.
For regular UI, we can use navigator object to insted of it. For unregular ui(for example don't support MSAA/UIA/IA etc.), window mouse key can't do anything. Because we will not know which place should be placed. Thanks!

@vgjh2005, For unregular ui(for example don't support MSAA/UIA/IA etc.), NVDA would not report the mouse position even if you scroll down with the wheel. So I think this is actually not possible to implement because the application itself needs to provide some information in order for the accessibility API to interpret it correctly. I think you want inaccessible applications to become more accessible through scrolling functionality and saving mouse positions. Right? I don't know if display model would improve such applications. But at least such applications like samplitude are made to be used together with a coresponding audio interface. So I think with such interfaces you could change the controls without using the mouse.