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>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: Accessibility
Date: Fri, 20 Sep 2024 21:22:43 +0200	[thread overview]
Message-ID: <9C2C3237-B346-4023-B7F6-3F9E7FD4D454@st.estfiles.de> (raw)
In-Reply-To: <5230241e-ff53-483d-b4d3-14d02b930672@gmx.es>

Hi Pablo,

sorry, I do not understand anything...

> Am 18.09.2024 um 19:47 schrieb Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>:
> 
> On 9/18/24 08:04, Steffen Wolfrum wrote:
>> It is a «new» European law: European Accessibility Act (EAA). Until
>> 28th of  June 2025  it has to be transposed by EU-members  into
>> national law. E.g. Germany will have a
>> «Barrierefreiheitsstärkungsgesetz» (BFSG) in June 2025.
> 
> Hi Steffen,
> 
> this is Directive UE/2019/882
> (https://data.europa.eu/eli/dir/2019/882/oj), which requires national
> law to be enforced (so it seems weird [at least to me] to call UE
> directives “laws“).
> 
> Incorporation into national law (sorry, this is “transposition” in
> EU-ideolect [https://www.eca.europa.eu/Other
> publications/EN_TERMINOLOGY_PUBLICATION/EN_TERMINOLOGY_PUBLICATION.pdf#page=56])
> was due more than two years ago (28/06/2022).
> 
> These legal texts shall enter into force in 28/06/2025 (according to
> article 31 of the said directive
> [https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32019L0882#d1e2828-70-1]).
> 
> Incorporations into national law by each State may be found at
> https://eur-lex.europa.eu/legal-content/EN/NIM/?uri=CELEX:32019L0882.
> 
> BTW, according to these data, Germany seems to have changed even its
> »Grundgesetz« because of this accesibility directive.

What do you mean by all of this?
My question was about how «alt text» can be provied by ConTeXt.

Why do you repeat and list all these legal details?



> Just another comment, please avoid hijacking message threads, since they
> break how message threads are displayed.
> 
> When starting a message with a new subject, avoid replying to a message
> from the list erasing the old subject and body.
> 
> In that case, the old message header (with references and in-reply-to
> fields) remains the same.
> 
> In this case, your message contains the in-reply-to the message-id value
> from
> https://mailman.ntg.nl/archives/list/ntg-context@ntg.nl/message/UFWZUB6WLY3PITODFSK2QCKSK3EX7UIE/
> and the reference to the original thread opening
> (https://mailman.ntg.nl/archives/list/ntg-context@ntg.nl/message/A3FVUDZVLZXBVXMWZAY4HYS3XXG57U2O/).
> 
> The more detailed explanation only intends to show why replying to a
> message to create a new thread breaks the display of message threads.

When I click on one of the two links you have posted, it will open «Same font for metafun as document».
What is this?

I never saw or read this thread, so why do you think my email hijacked something?
What have I done wrong?

Yours, Steffen


___________________________________________________________________________________
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-20 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17  6:05 [NTG-context] Same font for metafun as document Shiv Shankar Dayal
2024-09-17  6:10 ` [NTG-context] " Henning Hraban Ramm
2024-09-17  6:23   ` Shiv Shankar Dayal
2024-09-17 10:48     ` [NTG-context] Accessibility Steffen Wolfrum
2024-09-17 11:34       ` [NTG-context] Accessibility Henning Hraban Ramm
2024-09-18  6:04         ` Steffen Wolfrum
2024-09-18 17:47           ` Pablo Rodriguez via ntg-context
2024-09-20 19:22             ` Steffen Wolfrum [this message]
2024-09-21 13:26               ` Pablo Rodriguez via ntg-context
2024-09-21 19:48                 ` Henning Hraban Ramm
2024-09-22 12:25                   ` Pablo Rodriguez via ntg-context

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=9C2C3237-B346-4023-B7F6-3F9E7FD4D454@st.estfiles.de \
    --to=context@st.estfiles.de \
    --cc=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).