Linux for blind general discussion writes:
> 
> Voiceover can be made to act exactly like speakup using the numpad keys.
> 
On an Airbook? How?

> On Thu, 1 Mar 2018, 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 
> > > > <blinux-list@redhat.com> wrote:
> > > >
> > > > -eric
> > >
> > > _______________________________________________
> > > Blinux-list mailing list
> > > Blinux-list@redhat.com
> > > https://www.redhat.com/mailman/listinfo/blinux-list
> >
> >
> 
> -- 
> XB
> 
> _______________________________________________
> 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

Reply via email to