From: npostavs@users.sourceforge.net
To: Glenn Morris <rgm@gnu.org>
Cc: 21113@debbugs.gnu.org, Ali Abdul Ghani <blade.vp2020@gmail.com>
Subject: bug#21113: emacs Inaccessibility to Screen reader(orca)
Date: Fri, 02 Sep 2016 19:32:53 -0400 [thread overview]
Message-ID: <87r391op22.fsf@users.sourceforge.net> (raw)
In-Reply-To: <ppshtic2jm.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 02 Sep 2016 01:07:41 -0400")
# restoring severity from before mistake merge
severity 21113 important
quit
Glenn Morris <rgm@gnu.org> writes:
> npostavs@users.sourceforge.net wrote:
>
>>> I can't tell what is meant by "emacs inaccessibility" exactly. Is this
>>> bug the same as #1015, and #4103 (Emacs gtk hangs Orca)?.
>>
>> I will assume yes.
>
> I don't think this has anything to do with 1015.
> It seems pretty clear to me from the original report.
>
> When run in graphical mode, Emacs is not accessible to the Orca screen reader.
> Ie, Orca cannot read the text in Emacs.
>
> One has to run "emacs -nw" in eg a gnome-terminal to get things to work.
>
> Ref eg https://mail.gnome.org/archives/orca-list/2015-October/msg00278.html
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).
next prev parent reply other threads:[~2016-09-02 23:32 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 [this message]
2021-01-21 14:19 ` Lars Ingebrigtsen
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=87r391op22.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=21113@debbugs.gnu.org \
--cc=blade.vp2020@gmail.com \
--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).