public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: Newbie to linux and a question
Date: Tue, 18 Dec 2018 10:11:46 +0000	[thread overview]
Message-ID: <CAO2sX32K3CramjrAb2XBAyycScUNC0KWv0yqRgsqof1O_Pnjrg@mail.gmail.com> (raw)
In-Reply-To: <7778669D-A783-4795-BF2F-52B42CC5DF90@pipkrokodil.se>

Don't worry, this list has everything from people dipping their toes
in Linux for the first time to veterans who remember when GUIs were
the new fad, and I'd estimate the majority of the list's activity is
asking for blind-friendly ways of accomplishing a task or getting
braille and/or speech up and running.

I've only really used Orca with Firefox(even before going blind six
years ago, I was on a trend towards doing more-and-more from the
command-line anyways), but the impression I get is that GTK
applications are kinda hit-and-miss and that QT applications are
completely non-Accessible(though, I get the impression the former has
more to due with UI developers having a tendency to make mouse driven
interfaces while keyboard controls are treated as an afterthought,
moreso than the status of assistive technology, while the latter is
due to QT simply not having the mature accessibility layer GTK does).
Of course, most text mode applications are accessibile thanks to being
mostly what text-to-speech is best at working with, though admittedly,
some ncurses-based applications don't always put text where it is
easily read or make use of non-language characters and text layouts
that don't parse well.

-- 
Sincerely,

Jeffery Wright
Bachelor of Computer Science
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.

  reply	other threads:[~ UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
           ` Linux for blind general discussion
             ` Linux for blind general discussion
               ` Linux for blind general discussion [this message]
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
           ` Linux for blind general discussion
             ` Linux for blind general discussion
         ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
           ` Linux for blind general discussion
             ` Linux for blind general discussion
           ` Linux for blind general discussion
           ` Linux for blind general discussion
         ` 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=CAO2sX32K3CramjrAb2XBAyycScUNC0KWv0yqRgsqof1O_Pnjrg@mail.gmail.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).