caml-list - the Caml user's mailing list
 help / Atom feed
From: Sébastien Hinderer <Sebastien.Hinderer@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Wed, 19 Jan 2022 20:03:24 +0100
Message-ID: <YehgfIbXEeA05g2A@prajna.paris.inria.fr> (raw)
In-Reply-To: <20220119175121.zrug7wumxfsxl62x@posteo.de>

Hello,

Sam Kuper (2022/01/19 17:51 +0000):
> On Wed, Jan 19, 2022 at 05:31:39PM +0100, Sébastien Hinderer wrote:
> > Simon Cruanes (2022/01/18 15:55 +0000):
> >> By the way Sam, I opened https://discuss.ocaml.org/about in a TUI
> >> browser and it looked kind of ok.
>
> That suggests to me that Discourse relies on browser-sniffing (probably
> based on the user-agent string) to decide what to serve to the browser.
>
> So, users whose browsers (or browser-settings) don't match the Discourse
> devs' assumptions may be served non-accessible page content.
>
>
> Did you manage to create an account, via a text-mode browser, btw?

If you are asking me: I didn't even try that. I use Firefox with Orca
under Linux. I uselynx (text-mode browser) only for simple google
searches and for Wikipedia, almost all the time I end-up using Firefox.
I don't feel at ease with it because I feel too far away frmo the
information (it's hard to explain, sorry), but that's what gives the
best user experience, I think.

> > Well thei=re is no real equivalence between the ability to view a page
> > in a text-mode browser and its accessibility. NOt even an implication
> > in one direction or another.
>
> For people who use text-mode browsers for accessibility reasons, it's
> crucial that websites work in those browsers.

I am not sure such people exist nowadays. The visually impaired persons
follow, for most of them, the general tendency and use Windows or Mac
with screen-rendering solutions (NVDA and Jaws under Windows, VoiceOver
under MacOSX). Even among the minority of blind persons using Linux,
most of them work in the GUI. And for the minority of the minority who
uses the console, most of the time they do run X just to run Firefox. I
belong to this last category.

> (Likewise, for people who use screen-readers, it's crucial that websites
> work with screen-readers.  Mutatis mutandis.)

But working with screen-readers and being Java-script-free have become
two quite different things nowadays. Think about stuff like ARIA.

> > Similarly, I don't think it's expected, nowadays, that a website is
> > browsable without JS support for it to conform to WCAG.
>
> WCAG 1 explicitly required websites to be usable without scripts.

Yes but now the reference is WCAG 2.1, see

https://www.w3.org/WAI/standards-guidelines/wcag/

> WCAG 2 fudges the issue (due to pressure from Big Tech, IIRC), but very
> strongly implies it.
>
> The UK Government says:
>
>     Some users turn off features in their browsers deliberately. You
>     should respect their decision and make sure those users can still
>     use your service.
>
> https://www.gov.uk/service-manual/technology/using-progressive-enhancement#do-not-assume-users-turn-off-css-or-javascript

I, to, would prefer to be able to continue using lynx. I'm way more
comfortable than with Firefox. But there are so many aother batles that
I don't feel brave enough to invest energy in this one, nowadays. But I
am glad others do.

Sébastien.

  parent reply index

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 18:57 [Caml-list] Type Error in OCaml Code mukesh tiwari
2022-01-15 21:19 ` Nicolás Ojeda Bär
2022-01-16  9:40   ` [Caml-list] Ask questions on the mailing lists too orbifx
2022-01-16 14:32     ` Sam Kuper
2022-01-17  9:20       ` Sébastien Hinderer
2022-01-17  9:34         ` Daniil Baturin
2022-01-17 14:30           ` Sam Kuper
2022-01-17 14:56             ` Daniil Baturin
2022-01-17 17:36               ` Sam Kuper
2022-01-17 21:08                 ` Gabriel Scherer
2022-01-18  1:51                   ` Sam Kuper
2022-01-19 15:46                     ` Sébastien Hinderer
2022-01-18  9:49                   ` orbifx
2022-01-18 15:55                     ` Simon Cruanes
2022-01-19 16:31                       ` Sébastien Hinderer
2022-01-19 17:55                         ` Sam Kuper
2022-01-19 18:09                           ` Sam Kuper
2022-01-19 19:09                             ` Sébastien Hinderer
2022-01-19 20:53                               ` Sam Kuper
2022-01-19 18:43                           ` Simon Cruanes
2022-01-19 19:03                           ` Sébastien Hinderer [this message]
2022-01-19 20:50                             ` Sam Kuper
2022-01-20 20:56                         ` Edwin Török
2022-03-11  8:46                           ` Sébastien Hinderer
2022-03-11  9:38                             ` Vasilis Goumas
2022-03-11  9:43                               ` Gabriel Scherer
2022-01-19 15:33                   ` Sébastien Hinderer
2022-01-19 21:43                     ` Gabriel Scherer
2022-01-19 22:02                       ` Sam Kuper
2022-01-19 22:38                         ` Sébastien Hinderer
     [not found]                 ` <50AF4FEF-5CD6-40E7-9FA3-78814CBEE230@etorok.eu>
2022-01-17 22:47                   ` Sam Kuper
2022-01-17  9:54         ` Alan Schmitt
2022-01-17 13:53           ` Sam Kuper
2022-01-19 15:18             ` Sébastien Hinderer
2022-01-19 15:54           ` Sébastien Hinderer
2022-01-20  9:13             ` Alan Schmitt
     [not found]             ` <87pmom7sz7.fsf@m4x.org>
2022-01-20 14:16               ` Sébastien Hinderer

Reply instructions:

You may reply publically 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=YehgfIbXEeA05g2A@prajna.paris.inria.fr \
    --to=sebastien.hinderer@inria.fr \
    --cc=caml-list@inria.fr \
    /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

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror https://inbox.ocaml.org/caml-list

AGPL code for this site: git clone https://public-inbox.org/ public-inbox