unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Jude DaShiell <jdashiel@panix.com>
Cc: Emanuel Berg <incal@dataswamp.org>, help-gnu-emacs@gnu.org
Subject: Re: rcd-box.el for box drawings and tables
Date: Thu, 10 Nov 2022 16:02:34 +0300	[thread overview]
Message-ID: <Y2z2akUM7kUPyZ3q@protected.localdomain> (raw)
In-Reply-To: <e58f91c2-3d67-51ab-7b70-e769dd6d7197@panix.com>

* Jude DaShiell <jdashiel@panix.com> [2022-11-09 18:50]:
> On the screen reader I use, this message only spoke the text that was in
> the table.  That for screen reader users is especially useless since yes
> there's a table but what is where in that table?  The relationship data
> gets stripped in this form.

Is the screen reader software in Emacs?

Or you read e-mails by some other software?

Is it free software?

In case that screen reader is software in Emacs, there would be way to
improve it to avoid reading some characters.

Emacs has those hidden text properties, one can see what it is by
evaluating (buffer-string) so in my opinion, there is way to save the
whole Emacs buffer with text properties, and transfer such to other
person. I know it is not really what we do in practice, but that way
one could transfer also text properties which say "this char is part
of table" and would indicate to screen reader running within Emacs
that such char shall not be read by screen reader.

Then each cell could have it's text property in Emacs buffer. In that
case the spreadsheet with text properties would then be "readable" by
screen reader. Condition is that screen reader knows how to read
tables.

Screenreader could then say something like "Cell A1 with value US
$87.42". Or it could say "Moved to cell A2" or "Moved to cell B3 from
A3".

That makes sense to me.

Sadly we do not have software that generally cooperates with each
other in such way as to provide accessibility to blind.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2022-11-10 13:02 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 16:04 Elisp Reference Manual on inserting tables Christopher Dimech
2022-11-04 16:39 ` Eric S Fraga
2022-11-04 17:07   ` Christopher Dimech
2022-11-05 12:57     ` Fraga, Eric
2022-11-06  4:18       ` Heime
2022-11-06 20:48         ` Michael Heerdegen
2022-11-07  6:23           ` Jean Louis
2022-11-07 16:05             ` Michael Heerdegen
2022-11-07 16:49               ` Emanuel Berg
2022-11-08 15:57                 ` Michael Heerdegen
2022-11-07  7:24           ` Heime
2022-11-07 12:32             ` Emanuel Berg
2022-11-07 13:53               ` Heime
2022-11-07  7:32           ` Heime
2022-11-07 18:02             ` Michael Heerdegen
2022-11-07 18:07               ` Heime
2022-11-07 18:10               ` Heime
2022-11-07 21:12                 ` Michael Heerdegen
2022-11-08  4:09                   ` Heime
2022-11-08  4:12                     ` Emanuel Berg
2022-11-08 16:06                       ` Heime
2022-11-08 20:38                         ` Jean Louis
2022-11-09  0:49                         ` Emanuel Berg
2022-11-08 22:49                     ` Michael Heerdegen
2022-11-04 20:26   ` Heime
2022-11-04 16:43 ` Akib Azmain Turja
2022-11-05 19:37   ` Emanuel Berg
2022-11-06  6:48   ` Jean Louis
2022-11-06  8:31     ` Heime
2022-11-06  9:48       ` Jean Louis
2022-11-06 10:12         ` Heime
2022-11-06 12:26           ` Jean Louis
2022-11-06 12:54             ` Heime
2022-11-06 13:01               ` Emanuel Berg
2022-11-06 14:48                 ` Heime
2022-11-06 15:20                   ` Emanuel Berg
2022-11-07  5:38                   ` Jean Louis
2022-11-07  7:05                     ` Heime
2022-11-07  7:35                       ` Jean Louis
2022-11-07  5:37               ` Jean Louis
2022-11-08  6:39       ` rcd-box.el for box drawings and tables Jean Louis
2022-11-08  7:58         ` Heime
2022-11-08 12:29           ` Jean Louis
2022-11-08 15:29             ` Heime
2022-11-08 20:31               ` Jean Louis
2022-11-08 15:42           ` Jude DaShiell
2022-11-08 20:33             ` Jean Louis
2022-11-09  3:34               ` Jude DaShiell
2022-11-09  4:03                 ` Jean Louis
2022-11-09  4:28                   ` Emanuel Berg
2022-11-10  6:07                     ` Jean Louis
2022-11-10 18:22                       ` Emanuel Berg
2022-11-11 22:28                         ` [External] : " Drew Adams
2022-11-08  9:49         ` Emanuel Berg
2022-11-08 11:54           ` Jean Louis
2022-11-09  0:52             ` Emanuel Berg
2022-11-09 15:48               ` Jude DaShiell
2022-11-10 13:02                 ` Jean Louis [this message]
2022-11-10 13:13                   ` Jude DaShiell
2022-11-10 14:13                     ` Jean Louis
2022-11-09 15:49               ` Jude DaShiell
2022-11-09 16:03                 ` Emanuel Berg

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=Y2z2akUM7kUPyZ3q@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=incal@dataswamp.org \
    --cc=jdashiel@panix.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).