public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: FreeBSD accessibility?
Date: Wed, 12 Dec 2018 15:38:37 -0500	[thread overview]
Message-ID: <alpine.NEB.2.21.1812121535170.10433@panix1.panix.com> (raw)
In-Reply-To: <20181212115940.652f0382@bigbox.christie.dr>

Can raspberry pi's do serial connections?  If so, for the price of one
of them and an accessible distro on it like F123lite if you haven't got
a braille display these distros may possibly be installed with speech
screen readers too.  If the raspberry pi only does serial through usb,
such an attempt might work but would be questionable.

On Wed, 12 Dec 2018, Linux for blind general discussion wrote:

> Date: Wed, 12 Dec 2018 12:59:40
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: Linux for blind general discussion <blinux-list@redhat.com>
> Subject: Re: FreeBSD accessibility?
>
> Tim here. It depends on the hardware you have. It can be booted with
> a serial console, so if you have a Braille terminal or hardware that
> presents as a serial port, you can make a modified installer image
> that will do the entire install over the serial port as described here
>
> https://forums.freebsd.org/threads/installing-freebsd-over-serial-console.62005/
>
> I've asked Devin Teske (the maintainer of the installer) whether the
> entire installer is TUI/curses-based or if there's a more linear way
> of doing it.  If I hear back, I'll follow-up here.
>
> I know the *Open*BSD installer is very linear and is quite accessible
> with the dumbest of serial consoles.
>
> Once installed, at least the console should be pretty accessible.  I
> haven't kicked the tires on the GUI with Orca yet.
>
> -tim
>
>
>
> On December 12, 2018, Linux for blind general discussion wrote:
> > Hi,
> >
> > I want to try FreeBSD 12.0. Is the .dvd image accessible for blind
> > users or not?
> >
> > Thanks,
> >
> > Pavel
> >
> >
> > _______________________________________________
> > 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
>

-- 

  parent reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion
 ` Linux for blind general discussion
   ` FreeBSD accessibility? [follow-up] Linux for blind general discussion
   ` Linux for blind general discussion [this message]
     ` FreeBSD accessibility? Linux for blind general discussion

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.NEB.2.21.1812121535170.10433@panix1.panix.com \
    --to=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).