From: ali abdul ghani6 <blade.vp2020@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>,
21113@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#21113: emacs Inaccessibility to Screen reader(orca)
Date: Thu, 21 Jan 2021 06:37:02 -0800 [thread overview]
Message-ID: <CAHWa5ueTTn_ywa_DMkVWSkXNRwD7uY-=NHeTeQnOYwg75iBSmQ@mail.gmail.com> (raw)
In-Reply-To: <874kjal6dj.fsf@gnus.org>
> I know nothing about these things, so I wonder: Is Orca used much?
yes
> there other competing screen-reader APIs that would be better to focus
no
> Is Orca more convenient to use than Emacspeak?
yes
2021-01-21 6:19 غرينتش-08:00, Lars Ingebrigtsen <larsi@gnus.org>:
> 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
>
--
Emacs is the ground. We run around and act silly on top of it, and
when we die, may our remnants grace its ongoing incrementation.
prev parent reply other threads:[~2021-01-21 14:37 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
2021-01-21 14:37 ` ali abdul ghani6 [this message]
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='CAHWa5ueTTn_ywa_DMkVWSkXNRwD7uY-=NHeTeQnOYwg75iBSmQ@mail.gmail.com' \
--to=blade.vp2020@gmail.com \
--cc=21113@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.