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:09:06 +0100
Message-ID: <Yehh0hHvrC/HEUvk@prajna.paris.inria.fr> (raw)
In-Reply-To: <20220119180942.d3h4mrwpzlwqrbd6@posteo.de>

Sam Kuper (2022/01/19 18:09 +0000):
> Similarly:
>
>     We should never rely on anything but HTML.  CSS styles and
>     JavaScript should always be an additional layer which is not
>     essential for the service to function.
>
>
>https://accessibility-manual.dwp.gov.uk/tools-and-resources/govuk-resources

One thing worth noting is that, as far as I know, text-mode browsers are
far less maintained than mainstream browser. IN particular, I am very
much in doubt about how much of HTML5 they support. So, even if they are
in theory beter suited for visually impaired people (and themselves
would not agree on that) in practice we need a realistic and sustainable
solution and it looks more realistic and sustainable to make sure
accessibility works well in a GUI-based browser. I don't think
Javascript is necessary evil. You can do accessible Javascript-based
websites and you can do very poorly accessible HTML websites.

Sébastien.

  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 [this message]
2022-01-19 20:53                               ` Sam Kuper
2022-01-19 18:43                           ` Simon Cruanes
2022-01-19 19:03                           ` Sébastien Hinderer
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=Yehh0hHvrC/HEUvk@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