I'm all for accessibility-first, but Oleg's solution won't help. Here's a test page for some features that are frequently discussed in this context:

https://sjcjoosten.nl/tmp/test.html

Opening this in a browser shows the following content:

This content is perceivable by all browsers but should not be copiable by most.

The standard says this content should not be perceivable by screen readers.

This content is rendered via JavaScript and is not perceivable for those without JavaScript

Here's what Lynx users see (line-wraps are due to the width of my terminal):

This content is perceivable by all browsers but should not be copiable

by most.

The standard says this content should not be perceivable by screen

readers.

The standard says this content is not perceivable, following the HTML

hidden tag.

The standard says this content is not perceivable, using CSS.

There are separate issues that passed this thread:

- on Lynx, some things that are tooltips are displayed inline, they should not be displayed at all

- using select+copy, some things are selected and copied (when I tried this in Chrome, this only happens if I copy while my mouse is over the Show/Eq element)

There is actually a third use-case to consider, namely brower+screenreader combinations. Using apple's screen reader with Safari simply reads the 'should not be perceivable' line to me as well.

Johannes created an issue for this here: https://github.com/haskell/haddock/issues/1250

I'll put my suggestions on how to fix this there.

Best,

Sebastiaan

On Sun, Nov 15, 2020 at 1:49 PM Oleg Grenrus <oleg.grenrus@iki.fi> wrote:

About hiding some parts of the DOM tree with aria-hidden attribute.
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-hidden_attribute

I'm :+1: to making accessibility-first designs / markup. We forgot that
completely when accepting new color scheme for haddock. The accessible
and pretty-looking are not in conflict, but not easy.

- Oleg

On 15.11.2020 17.19, M Douglas McIlroy wrote:
>> I am pretty sure nobody writes code like this
>> I confirmed your example, reading with lynx and w3m.
>> wouldn’t just directly opening the sources (in a text editor) be simpler? 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 second that. I have always been annoyed by the ransom-note
> appearance of colorized listings. But that's just my taste. I
> suspect, though, that lots of people have been frustrated when they
> discover they can't use the code they see because it's festooned with
> markup. Golang.org offers similar listings, but also provides a button
> for selecting the underlying plain text. I would like hackage a lot
> better if it did so, too.
>
> Doug
> _______________________________________________
> 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.
_______________________________________________
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.