Re: Screen reader advice for a Linux sysadmin

[Linux for blind general discussion]

I agree VoiceOver does require a lot to interact with navigation commands but 
the speech output is amazing. Also I only ever use a laptop so I do not use a 
num pad with my machine. Another thing I will add in all this is that we all 
will be a bit partial or bias toward the OS, screen reader or tools we use so 
as long as we keep in mind everything we post is meant to share our personal 
opinions it is all useful information. I like to hear how Linux users do what 
they do so I hope my perspective on Mac is equally as useful to someone else. 
Bryan Duarte | software engineer

ASU Computer Science Ph.D Student
IGERT Fellow
Alliance for Person-centered Accessible Technology (APAcT)
Center for Cognitive Ubiquitous Computing (CUbiC Lab)
National Federation of the Blind of Arizona | Affiliate Board Member
National Association of Blind Students | Board Member
Arizona Association of Blind Students | President
Phone: 480-652-3045

> On Mar 1, 2018, at 3:36 PM, Linux for blind general discussion 
>  wrote:
> 
> Oh, yes, one can do this with Voice Over, but it's so very, very
> cumbersome compared to using Speakup's numeric keypad screen review.
> 
> I just don't have all day to fuss with VO. Just my experience.
> 
> Janina
> 
> Linux for blind general discussion writes:
>> -eric,
>> 
>> I honestly do not have any special software or configerations to interact 
>> with the Unix console. I have noticed that each person who is having issues 
>> with the Mac terminal have in common. Remember Voiceover requires that you 
>> use the VoiceOver keys to navigate the VoiceOver cursor. It is similar to 
>> the flat review in Linux but uses different keys. You have to hold down the 
>> CTRL + CMD keys to move the cursor. In addition to these keys you have to 
>> make sure you are interacting with the terminal window. VoiceOver requires 
>> that you are "interacting" with windows for VoiceOver to read the contents 
>> of that window. To do this you press the Shift key + CTRL + CMD + the down 
>> arrow. In terms of the terminal window you would listen for "Shell" and 
>> perform the interaction command. From this point you would use the VoiceOver 
>> navigation commands to move around the stdout including the man pages. 
>> 
>> To interact with the man pages simply execute the man page you are 
>> interested in then use the above commands to read it. Once you have read the 
>> currently displayed page you would press the space bar to bring up the next 
>> section of the man page. You can tell if there is additional pages not being 
>> displayed because at the bottom there will be a : displayed letting you know 
>> there are more pages to show. To exit the man pages you would simply type 
>> the letter q. I typically will execute this command to have more control of 
>> the man docs and can review them later.
>> $ man grep >> grep.txt
>> 
>> I am sure you understand what that is doing but in case someone does not it 
>> is basically redirecting the stdout from the man command to a file named 
>> grep.txt. I then will use vim or cat to read the documentation. Hope this 
>> helps
>> Bryan Duarte | software engineer
>> 
>> ASU Computer Science Ph.D Student
>> IGERT Fellow
>> Alliance for Person-centered Accessible Technology (APAcT)
>> Center for Cognitive Ubiquitous Computing (CUbiC Lab)
>> National Federation of the Blind of Arizona | Affiliate Board Member
>> National Association of Blind Students | Board Member
>> Arizona Association of Blind Students | President
>> Phone: 480-652-3045
>> 
>>> On Feb 28, 2018, at 5:03 PM, Linux for blind general discussion 
>>>  wrote:
>>> 
>>> -eric
>> 
>> ___
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
> 
> -- 
> 
> Janina Sajka
> 
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup: http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Platform Architectures  http://www.w3.org/wai/apa
> 
> ___
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

___
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list

Re: Screen reader advice for a Linux sysadmin

[Linux for blind general discussion]

Oh, yes, one can do this with Voice Over, but it's so very, very
cumbersome compared to using Speakup's numeric keypad screen review.

I just don't have all day to fuss with VO. Just my experience.

Janina

Linux for blind general discussion writes:
> -eric,
> 
> I honestly do not have any special software or configerations to interact 
> with the Unix console. I have noticed that each person who is having issues 
> with the Mac terminal have in common. Remember Voiceover requires that you 
> use the VoiceOver keys to navigate the VoiceOver cursor. It is similar to the 
> flat review in Linux but uses different keys. You have to hold down the CTRL 
> + CMD keys to move the cursor. In addition to these keys you have to make 
> sure you are interacting with the terminal window. VoiceOver requires that 
> you are "interacting" with windows for VoiceOver to read the contents of that 
> window. To do this you press the Shift key + CTRL + CMD + the down arrow. In 
> terms of the terminal window you would listen for "Shell" and perform the 
> interaction command. From this point you would use the VoiceOver navigation 
> commands to move around the stdout including the man pages. 
> 
> To interact with the man pages simply execute the man page you are interested 
> in then use the above commands to read it. Once you have read the currently 
> displayed page you would press the space bar to bring up the next section of 
> the man page. You can tell if there is additional pages not being displayed 
> because at the bottom there will be a : displayed letting you know there are 
> more pages to show. To exit the man pages you would simply type the letter q. 
> I typically will execute this command to have more control of the man docs 
> and can review them later.
> $ man grep >> grep.txt
> 
> I am sure you understand what that is doing but in case someone does not it 
> is basically redirecting the stdout from the man command to a file named 
> grep.txt. I then will use vim or cat to read the documentation. Hope this 
> helps
> Bryan Duarte | software engineer
> 
> ASU Computer Science Ph.D Student
> IGERT Fellow
> Alliance for Person-centered Accessible Technology (APAcT)
> Center for Cognitive Ubiquitous Computing (CUbiC Lab)
> National Federation of the Blind of Arizona | Affiliate Board Member
> National Association of Blind Students | Board Member
> Arizona Association of Blind Students | President
> Phone: 480-652-3045
> 
> > On Feb 28, 2018, at 5:03 PM, Linux for blind general discussion 
> >  wrote:
> > 
> > -eric
> 
> ___
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

-- 

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:   http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectureshttp://www.w3.org/wai/apa

___
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list

Re: Screen reader advice for a Linux sysadmin

[Linux for blind general discussion]

Here are the major adjustments I fund useful for using voiceover in terminal on 
a mac as a ssh base:

1. in vo preferences have all cursors follow each other, including the mouse 
cursor.

2. when in terminal go into text interaction mode.

3. Use the standard mac navigation and vo speech command key combinations to 
work anywhere on the visible screen.

For example, vo + home goes to the top of the screen, vo + end to the bottom.

Vo plus s for the current sentence, l for line and p for paragraph.  Vo +a read 
the screen starting with cursor position.

Many of these and more an be found by invoking the vo help menu with vo + h.

4. use vo key commanders to make custom navigation and speech commands with 
fewer key combinations and strokes.  This is done in vo
preferences.

Key commanders are used with an option key combined with a character, including 
punctuation, and including those on the numpad if you have
one; of one's choice whichh are less complex then the default key combinations. 
Many of the built in key commander default choices determine
how speech works, as well as navigation and many default os functions.

They can also be attached to apple scripts.

An example of the latter, instead of having seperate commands to go to the top 
of the screen, move down one line to avoid the title line and
start to read the entire screen.  These can be made one key commander which 
evokes an apple script that performs the above sequence of
navigation and speech commands.

On Wed, 28 Feb 2018, Linux for blind general discussion wrote:

> On Wed, Feb 28, 2018 at 08:31:23AM -0500, Linux for blind general discussion 
> wrote:
> >
> >
> >I concur with using a mac as a ssh base.  The bsd based terminal can
> >be made much more accessable using the mac's native voiceover with a
> >few minor system configuration changes.
>
> Which changes are necessary to make the textbased terminal work better
> with VoiceOver? With the default settings VO support for the terminal is
> not really good IMHO and everything I tried didn't it make better :-(.
>
> I'd really like to use my Mac to administrate my Linux servers at work
> via ssh, write scripts or edit config files with vi on the servers,
> e.g., but all those things are not possible because VO looses the focus
> while writing commands in the shell or editing files wit vi, keeps
> hanging when much output is provided by a system and so on.
>
> Every hint which makes things better in the terminal is highly wellcome
> :-).
>
> Cheers and thanks,
>
>   Schoepp
>
>

-- 
XB

___
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list

Re: Screen reader advice for a Linux sysadmin

[Linux for blind general discussion]

Tim here.  Eric wrote about issues with man formatting. There are a
couple options:

At least with GNU man (the default on most Linux systems, but not the
BSDs), you can have `man` open your page in your $BROWSER.  So you
can do something like

  $ export BROWSER=`which lynx`
  $ man -H strftime

to show the man page for `strftime` in lynx.  Works fine with other
browsers like Firefox as well as long as $BROWSER is set correctly.
If you want this behavior ALL the time, you can issue

  export MANOPT=-H

or

  export MANOPT="-Hlynx"

in your .bashrc (or other shell configuration file).

Alternatively, you can pipe the output of `man` to `col -b` to strip
out the formatting and then pipe that to your $PAGER

  $ man strftime | col -b | less

This does the stripping you describe wanting to use grep/sed to do,
but saves you the trouble of coming up with an appropriate regular
expression.  This works both on Linux and the BSDs (and not just
with `man` but with any output that uses the ^H to backspace and
overstrike, whether for bold or underline)

Hope this helps,

-tim



On February 28, 2018, Linux for blind general discussion wrote:
> that does help.
> However, given how the man pages are formatted, there are some
> issues dealing with the highlighted text inside those manages, as
> well as underlined links. What would appear, visually, to be a
> single word highlighted and in all caps turns into individual
> capitalized letters separated by spaces. the underlined text that
> is highlighted and underlined is even more problematic. I guess I
> am going to have to read on grep a bit in order to filter those out.
> 
> -eric
> 
> On Feb 28, 2018, at 5:23 PM, Linux for blind general discussion
> wrote:
> 
> > -eric,
> > 
> > I honestly do not have any special software or configerations to
> > interact with the Unix console. I have noticed that each person
> > who is having issues with the Mac terminal have in common.
> > Remember Voiceover requires that you use the VoiceOver keys to
> > navigate the VoiceOver cursor. It is similar to the flat review
> > in Linux but uses different keys. You have to hold down the CTRL
> > + CMD keys to move the cursor. In addition to these keys you have
> > to make sure you are interacting with the terminal window.
> > VoiceOver requires that you are "interacting" with windows for
> > VoiceOver to read the contents of that window. To do this you
> > press the Shift key + CTRL + CMD + the down arrow. In terms of
> > the terminal window you would listen for "Shell" and perform the
> > interaction command. From this point you would use the VoiceOver
> > navigation commands to move around the stdout including the man
> > pages. 
> > 
> > To interact with the man pages simply execute the man page you
> > are interested in then use the above commands to read it. Once
> > you have read the currently displayed page you would press the
> > space bar to bring up the next section of the man page. You can
> > tell if there is additional pages not being displayed because at
> > the bottom there will be a : displayed letting you know there are
> > more pages to show. To exit the man pages you would simply type
> > the letter q. I typically will execute this command to have more
> > control of the man docs and can review them later. $ man grep >>
> > grep.txt
> > 
> > I am sure you understand what that is doing but in case someone
> > does not it is basically redirecting the stdout from the man
> > command to a file named grep.txt. I then will use vim or cat to
> > read the documentation. Hope this helps Bryan Duarte | software
> > engineer
> > 
> > ASU Computer Science Ph.D Student
> > IGERT Fellow
> > Alliance for Person-centered Accessible Technology (APAcT)
> > Center for Cognitive Ubiquitous Computing (CUbiC Lab)
> > National Federation of the Blind of Arizona | Affiliate Board
> > Member National Association of Blind Students | Board Member
> > Arizona Association of Blind Students | President
> > Phone: 480-652-3045
> >   
> >> On Feb 28, 2018, at 5:03 PM, Linux for blind general discussion
> >>  wrote:
> >> 
> >> -eric  
> > 
> > ___
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list  
> 
> 
> ___
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

___
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list

Re: podcast client with search capability

[Linux for blind general discussion]

greg-git is available in the archlinux aur repository and builds 
successfully on archlinux.  No mention of search capability in the 
program no man page either.  Maybe info documentation or a doc file in 
/usr/share/doc/greg or /usr/share/greg but I haven't searched that far 
yet.


I have surfraw installed over here for searching and can run something 
like
google  on the command line and search google without the 
need to run lynx since surfraw runs lynx once lynx is stored in the 
right export variable.  When I search for podcasts I usually pass google 
 NEAR podcast to narrow down some sites; google tarot 
NEAR podcast could be used to find tarot podcasts as one example.  Once 
that's done I open each site and find the podcast urls.  and rss urls 
and I move onto each and hit the equals sign and check out the last line 
of text on the page starting with U
RL: and see if that url ends in /podcasts/ or .mp4 or .mp3 and if so, I 
save that in my podcasts feeds file and run the podcast catcher and see 
what if anything loads onto my computer.


On Wed, 28 Feb 2018, Linux for blind general discussion wrote:


Date: Thu, 1 Mar 2018 00:15:37
From: Linux for blind general discussion 
To: Linux for blind general discussion 
Subject: Re: podcast client with search capability

I fooled around with that miro site, couldn't completely download a version, 
but also, they say each user must donate to their foundation. Neither debian 
nor ubuntu have it. Also, I had no luck adding a launch pad ppa. Earlier 
today in my search on this topic, it mentioned a client called "greg"  but 
so-far I am getting nowhere with it. Thanks in advance for continuing 
guidance

Chime

___
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list



--

___
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list