Its not documented but it seems you have robust and standard keyboard use on controls. It has undo, vertical arrow keys, start/end, 0-9... different ways to set a control only with keyboard and also mouse coordinates and mouse wheel (I only use wheel for everything i have not midi mapped, for me it is fast and precise enough in 98% of controls).
I have found that Keyboard use sends same values as mouse use so theres no difference about using one or the other. This is good! because proves me that mouse is not cause of the 6 options pots annoyance and GUI has no bugs itself.
About accesibility, Only by adding TAB key and CTRL+TAB for selecting controls sequentially (with automatic visual feedback also, oops!) as in Windows, and Scope could easily get the certification for accesibility. With this kind of certification you can avoid never ending trolling discussion about never perfect GUIs. MS Windows needed lots of refactoring, versions, updates to become the standard pc GUI.
Tips and advice for getting the most from Scope. No questions here please.