What new work do you want to do? Do you want to continue in your current field? Are there particular kinds of projects you'd like to work on? Answering these questions can help determine what programming language you'll learn first.
The choice of a first programming language is somewhat arbitrary. By "somewhat arbitrary" I mean that you could do well in any of the most popular programming languages for which there are accessible software development packages. However, some professional fields favor particular languages. If you feel drawn to a particular field or a particular project, then choose the language mentioned most frequently in job listings, forum posts, and academic papers for that subject. I'd recommend digging a little bit into a particular field and then writing a new post about what you've found.
"Front end" doesn't have to mean visual. User interface and user interaction design are still heavily biased toward visual design, but principles of good interface design and good interaction design relate to non-visual design as well. If you became a front end designer specializing in non-visual designs, you could fairly quickly be sought out for your expertise.
Pick a language, learn it steadily, create one project after the other, and ask and answer questions on
$1.
Another thing to keep in mind is that the everyday practice of programming involves more than just typing out code. You'll learn about "source control" or "version control," a part of your work related both to how you build up software projects over multiple versions. It's also related to how you coordinate work with other programmers.
You have likely found blog posts and stories about blind programmers. The following posts may already be familiar to you, but I'll post a few:
Here's one called "The Tools of a Blind Programmer":
$1 On
$1, a site developers are quite familiar with, here's a post called "How can you program if you're blind"
$1 From Perkins School for the Blind, here's an article called "Accessible Coding":
$1 If you're passionate about some subject, you almost certainly can find some way to combine your interest in that subject with programming. Learning by doing is critical in becoming a developer, so go ahead and learn programming by doing development work that keeps you motivated.
Even as a beginning programmer, set an ambitious goal to one day complete a software project specific to one of your interests or hobbies. Then as you learn new concepts you can practice them by creating simple projects related to the grand goal.
For example, if your passions are polka music and goldfish, then your grand goal might be to create an app in which tapping on the screen of a mobile device plays polka music that "feeds" virtual goldfish. (Years from now, the two dozen people intensely interested in both polka music and goldfish may find this Reddit post and wonder why this app still doesn't exist.)
Imagine breaking your PolkaFish app into its simplest components. If you want audio in your app, what is the simplest sound you can imagine having your app make, and how do you write code to do that? What basic math do you need to keep track of how much goldfish have eaten? How do you keep track of multiple goldfish? If the goldfish change over time, how do you keep track of time? How do you assign a name to each goldfish? Each such question could drive you to study a particular programming question, or the questions may come to mind as you're working through the lessons in some formal programming course.
And if you end up creating a PolkaFish app, it may not sell millions, but fellow polka music and goldfish lovers will be ecstatic. And that's great motivation to continue developing and learning.