Hey, welcome to the list!
I generally test my web API calls in the Chrome developer tools. I start
out in Notepad++ or VS Code or whatever, paste it into the JavaScript
console, and see how it works; or if my client isn't JS-based, I would use
the language's HTTP request-sending frameworks to test my API (so same
idea, just not in a browser). It's not ideal, but it does save time,
because the end result is a bare-bones SDK, a library of functions or
classes that I can use in my client-side code right away. This also solves
the accessibility issue, because you can use whatever tools you want. Hope
that helps. :)
On Sat, Mar 16, 2019 at 1:58 PM <westbchris@xxxxxxxxx> wrote:
HI all. I thought I would introduce myself quickly before asking my
question instead of just being rude and randomly asking a question as m
first post. I am totally blind and hearing impaired from Pennsylvania in
the US. I am a programmer employed for an advertising agency. I am
currently trying to learn more modern web programming techniques like
react, javascript, etc., I am primarily using asp.net c# on the backend.
I use sql server at work but am using postgres for my personal project. I
am wondering if you have found an accessible alternative to postman for
testing web apis? I tried using curl on windows, but I can’t get it to
redirect the output to a file so I can more easily read it with Jaws /nvda.
The documentation says -o should work, but it always seems to send the
output to the terminal. Postman seems pretty inaccessible unfortunately.
Thanks for any help.
