ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: images with alt text
Date: Mon, 23 Sep 2024 08:02:05 +0200	[thread overview]
Message-ID: <24512567-005b-48a2-baf6-516a2e2c3f3b@gmx.es> (raw)
In-Reply-To: <32165af3-e6f1-45fa-bf23-eb7f90b16298@freedom.nl>

On 9/22/24 21:58, Hans Hagen via ntg-context wrote:
> On 9/22/2024 2:43 PM, Pablo Rodriguez via ntg-context wrote:
>
>> It would be great to have synonyms added the /E information by default.
>> I think this may be a requirement for text-to-speech conversions.
>
> even more crap .. let's wait till abbreviations are completely forbiddeb
> (and also units and such )

From what I see, /E may be helpful (similar to /ActualText).

For me, the real problem with accessibility (and penalties for
non-accessible documents) is that it will force all documents to be
machine-readable (so we have to feed AI with all our public documents,
whether we like it or not).

I mean, no such as "\enabledirectives[backend.pdf.nounicode=❌]" allowed.

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-09-23  6:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-21 17:16 [NTG-context] " Steffen Wolfrum
2024-09-22 11:15 ` [NTG-context] " Hans Hagen via ntg-context
2024-09-22 12:43   ` Pablo Rodriguez via ntg-context
2024-09-22 19:58     ` Hans Hagen via ntg-context
2024-09-23  6:02       ` Pablo Rodriguez via ntg-context [this message]
2024-09-23 15:09         ` Hans Hagen via ntg-context
2025-02-04 14:03           ` Steffen Wolfrum
2025-02-04 15:40             ` Florent Michel
2025-02-05 11:27               ` luigi scarso
2025-02-05 12:11                 ` Hans Hagen
2025-02-05 14:44                   ` Steffen Wolfrum
2025-02-05 16:35                     ` Hans Hagen
2025-02-05 17:49                       ` Steffen Wolfrum
2025-02-05 18:13                         ` Keith McKay
2025-02-05 20:51                           ` Henning Hraban Ramm
2025-02-05 21:53                             ` Keith McKay
2025-02-05 18:18                       ` Thomas A. Schmitz
2025-02-05 19:44                         ` Steffen Wolfrum
2025-02-06 11:22               ` Steffen Wolfrum
2025-02-06 11:56                 ` Florent Michel
2025-02-06 12:06                   ` Steffen Wolfrum
2025-02-06 13:17                     ` Steffen Wolfrum
2025-02-06 13:30                       ` Florent Michel

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=24512567-005b-48a2-baf6-516a2e2c3f3b@gmx.es \
    --to=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /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 NNTP newsgroup(s).