From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: PDF/UA-2, WTPDF
Date: Sun, 7 Apr 2024 09:31:30 +0200 [thread overview]
Message-ID: <f29b4a94-42ad-421b-bbbc-abdb366f887c@fiee.net> (raw)
In-Reply-To: <63446922-684c-4ccb-953d-e147461ca10a@xs4all.nl>
Am 07.04.24 um 08:06 schrieb Hans Hagen:
> On 4/6/2024 5:34 PM, Henning Hraban Ramm wrote:
>
>> 1. PDF/UA-2
>> https://pdfa.org/iso-14289-2-pdfua-2/
>
> looks likes one has to pay for it
Oh, as usual with PDF association…
That’s not how you promote open standards.
(Didn’t check, jost forwarded the message.)
>> 2. Well-Tagged PDF (WTPDF)
>> https://pdfa.org/wtpdf/
> well, tagging ...
Of course.
But you asked for wanted accessibility features:
We have \pdfbackendactualtext{visible}{alternative}, can we get
alternative text (ActualText) for images?
Not automatically, of course (if someone wants AI descriptions they can
implement a module), just as a keyword in \externalfigure?
Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2024-04-07 7:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 15:34 [NTG-context] " Henning Hraban Ramm
2024-04-07 6:06 ` [NTG-context] " Hans Hagen
2024-04-07 7:31 ` Henning Hraban Ramm [this message]
2024-04-07 9:17 ` Ulrike Fischer
2024-04-07 9:57 ` Henning Hraban Ramm
2024-04-07 10:28 ` Ulrike Fischer
2024-04-07 16:48 ` Hans Hagen
2024-04-07 17:11 ` Hans Hagen via ntg-context
2024-04-07 17:00 ` Hans Hagen
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=f29b4a94-42ad-421b-bbbc-abdb366f887c@fiee.net \
--to=texml@fiee.net \
--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).