PS:
If you shouldn't be visibly impaired and assumed you should have issues
with reading for what other reason ever, then consider to use less
command line, but more GUIs to do audio recordings.
The reason for this is, that GUIs for audio work usually don't require
reading and that it's harder to do audio work, if Mr. Hawking does
interrupt it by breaking in.
Having issues with reading (but even if reading should be an easy
pleasure) and the wish to use the computer to do audio work, GUIs are
much more pleasant to use, than command line, assumed the user isn't
visible impaired. Tools for audio related work are much more "visually"
then "verbally", so if possible users should use GUI based tools
instead of command line tool. Especially creative audio artwork (music)
is mostly done by the right cerebral hemisphere, so closer to the
"visually" way of thinking, then to the "verbally" way of thinking.
I'm usually using command line instead of file managers and similar
tools, since a few bash commands are easier to use, and give a
better overview, then to learn how to use complicated GUI tools with
confusing overviews. However for audio work, especially for artwork I
prefer GUIs over command line, since it does absolutely require no
verbally thinking and reading (assumed the GUI is self explaining,
following common standards), everything is plain visually, even signs
(play, record, scroll etc.) are not that confusing as letter put
together to words are (Ilbdpqmn).