(Neglected to CC haskell-cafe, sorry Mario for the duplicate.)

The only plain-HTML solutions I’m aware of are the ‘title’ attribute and the HTML5 ‘<details>’ element. The latter may contain a ‘<summary>’ element for the content displayed by default, plus other content that the user can expand or collapse. Unfortunately, as far as I know Lynx doesn’t support either of these; not sure about other text browsers. In Lynx you could maybe get some nice UX for this with the ‘<fn>’ footnote element from HTML 3.0, but that’s deprecated and probably not supported in other browsers.

It doesn’t help with Lynx support, but I guess the right thing to do here for screenreader support in other browsers is to add the ‘tooltip’ role to the tooltip element, toggle its ‘hidden’ attribute with JavaScript to show and hide it, and use ‘aria-describedby’ / ‘aria-expanded’ on the anchor element to handle relating the two and announcing the tooltip correctly when it’s shown.

On Sat, Nov 14, 2020 at 4:20 PM Mario Lang <mlang@blind.guru> wrote:

Alec Theriault <alec.theriault@gmail.com> writes:

> Although I’m sympathetic to the accessibility, in this case wouldn’t just
> directly opening the sources (in a text editor) be simpler?

Following a link to a definition is convenient because there is an
anchor.
Of course I can just open the original sources in a text editor.
But then I am no longer reading documentation, I am reading sources!

> Is there a (simple) way to preserve the experience when browsing using
> Lynx without also holding back features aimed at a regular browsing
> experience?

I was expecting this sort of killer argument. I have to admit I am too
exhausted with this topic to try and give a meaningful answer. There
used to be a time when compatibility to existing technology was a goal
by itself. This is going away even in circles which usually have tried
to achieve some sort of technical excellence. I am sad. But I can not
do anything against the tides except for sometimes pointing at ships
while they are sinking, hoping to get someone to see reason and rescue
at least some of them.

Practically speaking, the problem is the visibility style attribute. As
far as I know, none of the text browsers (lynx, w3m, elinks, eww) have
CSS support. Barring any other HTML construct which would allow to hide
things by default for text browsers, all I can think of a plain
version in addition to a hip version. That should be easy to
autogenerate, but it has all the problems attached to a alternative
version.

--
CYa,
⡍⠁⠗⠊⠕
_______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.