Re: href in custom elements

Can this problem not be solved in the caddy file or nginx?, specific to
what the source and target need to be tailored.

Op do 30 apr 2026 om 15:26 schreef David Woolley <[email protected]=
k
>:

> On 30/04/2026 00:14, Thorsten Glaser wrote:
> >> The funny thing is that they claim this complexity is done for the
> >> purpose of accessibility regulation in the EU =F0=9F=99=82
>
> > That=E2=80=99s ridiculous. Someone sold something overengineered to the=
m
>
> I think this will be the result of the normal (bad) way of designing web
> sites: design ignoring accessibility and retrofit it at the last minute.
>   Their hack is probably a way of conditionally enabling accessibility
> without disturbing the original structure.
>
> Unfortunately the W3C WCAG long ago decided that pages that only worked
> with EcmaScript/document object model/browser object model support were
> accessible, but Lynx doesn't generate anything close to a conforming
> document object model.
>
> I think they designed inaccessible sites, and were simply advised this
> was the minimum change to meet the EU requirements, which use W3C WCAG
> as a starting point.
>
> Technically, none of this is about graphical versus character cell text,
> but, in practice the latter ones used ad hoc ways of going from HTML
> stream to rendered output, and converting them to use a DOM would
> probably mean rewriting about 80% of the code.
>
> Consider yourself lucky that you are not getting an AJAX page.
>