From: Sam Kuper <sampablokuper@posteo.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Wed, 19 Jan 2022 18:09:42 +0000 [thread overview]
Message-ID: <20220119180942.d3h4mrwpzlwqrbd6@posteo.de> (raw)
In-Reply-To: <20220119175121.zrug7wumxfsxl62x@posteo.de>
On Wed, Jan 19, 2022 at 05:51:21PM +0000, Sam Kuper wrote:
> On Wed, Jan 19, 2022 at 05:31:39PM +0100, Sébastien Hinderer wrote:
>> 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.
>
> 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
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
--
A: When it messes up the order in which people normally read text.
Q: When is top-posting a bad thing?
() ASCII ribbon campaign. Please avoid HTML emails & proprietary
/\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
next prev parent reply other threads:[~2022-01-19 18:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 18:56 [Caml-list] Type Error in OCaml Code mukesh tiwari
2022-01-15 21:18 ` Nicolás Ojeda Bär
2022-01-16 9:40 ` [Caml-list] Ask questions on the mailing lists too orbifx
2022-01-16 14:31 ` Sam Kuper
2022-01-17 9:20 ` Sébastien Hinderer
2022-01-17 9:33 ` 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:06 ` Gabriel Scherer
2022-01-18 1:51 ` Sam Kuper
2022-01-19 15:46 ` Sébastien Hinderer
2022-01-18 9:48 ` orbifx
2022-01-18 15:55 ` Simon Cruanes
2022-01-19 16:31 ` Sébastien Hinderer
2022-01-19 17:51 ` Sam Kuper
2022-01-19 18:09 ` Sam Kuper [this message]
2022-01-19 19:09 ` Sébastien Hinderer
2022-01-19 20:53 ` Sam Kuper
2022-01-19 18:42 ` 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:37 ` Vasilis Goumas
2022-03-11 9:42 ` Gabriel Scherer
2022-01-19 15:33 ` Sébastien Hinderer
2022-01-19 21:43 ` Gabriel Scherer
2022-01-19 22:01 ` 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:53 ` Alan Schmitt
2022-01-17 13:52 ` Sam Kuper
2022-01-19 15:18 ` Sébastien Hinderer
2022-01-19 15:54 ` Sébastien Hinderer
2022-01-20 9:12 ` Alan Schmitt
[not found] ` <87pmom7sz7.fsf@m4x.org>
2022-01-20 14:15 ` Sébastien Hinderer
Reply instructions:
You may reply publicly 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=20220119180942.d3h4mrwpzlwqrbd6@posteo.de \
--to=sampablokuper@posteo.net \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).