From: Lars Ingebrigtsen <larsi@gnus.org>
To: npostavs@users.sourceforge.net
Cc: Ali Abdul Ghani <blade.vp2020@gmail.com>,
Glenn Morris <rgm@gnu.org>,
21113@debbugs.gnu.org
Subject: bug#21113: emacs Inaccessibility to Screen reader(orca)
Date: Thu, 21 Jan 2021 15:19:36 +0100 [thread overview]
Message-ID: <874kjal6dj.fsf@gnus.org> (raw)
In-Reply-To: <87r391op22.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net's message of "Fri, 02 Sep 2016 19:32:53 -0400")
npostavs@users.sourceforge.net writes:
> Oh, I see, the term "accessibility" has a very particular meaning in the
> context of screen readers (I had thought it was just odd word choice in
> the original report).
I found this bug report pretty confusing, too, but the request is for
Emacs to support the Orca screen reader, which is a Gnome thing.
To do this, Emacs has to implement a Gnome API:
https://help.gnome.org/users/orca/stable/introduction.html.en
The report states that "emacs -nw" works fine -- but according to some
experimentation, that seems to be because Terminal (the Gnome
xterm-a-like) supports Orca. Emacs itself doesn't support Orca at all.
I know nothing about these things, so I wonder: Is Orca used much? Are
there other competing screen-reader APIs that would be better to focus
on? Is Orca more convenient to use than Emacspeak?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-01-21 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 9:08 bug#21113: emacs Inaccessibility to Screen reader(orca) Ali Abdul Ghani
2015-07-23 4:45 ` Xue Fuqiao
2015-07-23 15:35 ` Ali Abdul Ghani
2016-07-14 1:01 ` npostavs
2016-09-02 3:00 ` npostavs
2016-09-02 5:07 ` Glenn Morris
2016-09-02 23:32 ` npostavs
2021-01-21 14:19 ` Lars Ingebrigtsen [this message]
2021-01-21 14:37 ` ali abdul ghani6
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kjal6dj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21113@debbugs.gnu.org \
--cc=blade.vp2020@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=rgm@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).