From: Luis Felipe via Guix-patches via <guix-patches@gnu.org>
To: "39635@debbugs.gnu.org" <39635@debbugs.gnu.org>
Subject: [bug#39635] website: Modify use of H1 headings
Date: Tue, 06 Oct 2020 14:03:19 +0000 [thread overview]
Message-ID: <zwSeB545QcCtpauE6pSf6fAdsylZt_mkH78bdpKIcE2jGVUAU1ivLdIGOgsEc0SnyCO8dLLyfWRsED20HlO1tR7O_0T7VaaC0JslSGc4ezw=@protonmail.com> (raw)
In-Reply-To: <20200216182649.25068-1-sirgazil@zoho.com>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Ping...
Regardless of whether this change is applied, I think it would be good to suggest blog posters to use heading levels to convey structure, not style. Currently, post headings are often used for the latter (for instance, to make a heading text smaller). I haven't tried myself, but it seems that using headings in this way can make it harder for people using assistive technologies.
So, when writing a blog post, the title has the highest level (currently H2, but H1 if this patch is applied), and the headings in the body should use lower levels accordingly, without skipping levels.
[-- Attachment #2: Type: text/html, Size: 663 bytes --]
next prev parent reply other threads:[~2020-10-06 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 18:26 [bug#39635] [PATCH] website: Modify use of H1 headings sirgazil via Guix-patches via
2020-10-06 14:03 ` Luis Felipe via Guix-patches via [this message]
2020-10-09 2:49 ` Maxim Cournoyer
2020-10-10 19:51 ` Luis Felipe via Guix-patches via
2020-10-12 8:02 ` zimoun
2020-10-12 14:08 ` Luis Felipe via Guix-patches via
2020-10-13 1:36 ` Maxim Cournoyer
2022-10-18 15:58 ` zimoun
2022-10-18 21:34 ` Luis Felipe via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='zwSeB545QcCtpauE6pSf6fAdsylZt_mkH78bdpKIcE2jGVUAU1ivLdIGOgsEc0SnyCO8dLLyfWRsED20HlO1tR7O_0T7VaaC0JslSGc4ezw=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=39635@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).