I will be using WinSCP for some government projects and it requires a software to be compliant with SEction 508. Is WinSCP compliance with Section 508?
Section 508 compliance is basically "does your program operate correctly under JAWS"? Can a person who is visually impaired (and uses JAWS) navigate the software entirely with the keyboard?
If you use all native Windows API calls and don't do custom UI components, then your software is most likely JAWS compatible and you don't need to do anything else except possibly find someone who is blind/impaired to use the software with their licensed copy of JAWS. If you have custom UI components or do weird crap with existing components, then you'll need to find someone with a copy of JAWS and see how it behaves. There are accessibility API calls you can make from your UI components to get information to JAWS to play the audio.
There are other products besides JAWS, but JAWS is the de facto standard. Don't install JAWS on your development machine - it'll drive you completely nuts. A virtual machine might be okay though but audio is generally shaky on VMs.
WinSCP is application designed to be used by keyboard only. That's one of its main distinctions.
I know that blind people do use WinSCP, because I occasionaly get requests for improvements from them.
Though I do not know about Jaws.
