ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: images with alt text
Date: Tue, 4 Feb 2025 15:03:35 +0100	[thread overview]
Message-ID: <4A5E33CD-A209-44B4-A4D4-6F67BACA4659@st.estfiles.de> (raw)
In-Reply-To: <0d3c437f-8930-4a56-b124-11f606a8f24c@freedom.nl>

Hi,

today my publishers ask for an example of how ConTeXt deals with accessibility.

I send them a PDF with

\setupbackend[export=yes]
\setupstructure[state=start,method=auto]

What they needed was like
<img src="example.jpg" alt="Example text">

What is the equivalent for this with ConTeXt?
Contextgarden ( https://contextgarden.net/Accessibility) is empty...

Yours, Steffen



> Am 23.09.2024 um 17:09 schrieb Hans Hagen via ntg-context <ntg-context@ntg.nl>:
> 
> On 9/23/2024 8:02 AM, Pablo Rodriguez via ntg-context wrote:
>> 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).
> 
> Imo it's useless:
> 
> (1) normally when a new abbreviation is intriduced one has the expanded meaning after it
> (2) after that it is suposed to be known
> (3) if one jumps into a document in the middle one cannot expect it to be repeated every time
> (4) if that *is* expoected there is no need to use abbreviations at all
> (5) so, why should a 'read out' document have all abbreviations with an expanded meaning and a typeset text not
> 
>> 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 assume that such a machine learning or pattern recognotion app can quite well figure out that it's an abbreviation
> 
>> I mean, no such as "\enabledirectives[backend.pdf.nounicode=❌]" allowed.
> 
> well, everything is allowed ... after all why do we typeset and visualize otherwise ... it depends on the audience
> 
> one can always generate multiple versions, one with two times the number of pages and all expanded
> 
> Hans
> 
> 
> 
> -----------------------------------------------------------------
>                                         Hans Hagen | PRAGMA ADE
>             Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>      tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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:[~2025-02-04 14:26 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
2024-09-23 15:09         ` Hans Hagen via ntg-context
2025-02-04 14:03           ` Steffen Wolfrum [this message]
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=4A5E33CD-A209-44B4-A4D4-6F67BACA4659@st.estfiles.de \
    --to=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    /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).