From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
Received: (qmail 10793 invoked from network); 6 Jul 2022 14:40:25 -0000
Received: from bsd.lv (HELO mandoc.bsd.lv) (66.111.2.12)
  by inbox.vuxu.org with ESMTPUTF8; 6 Jul 2022 14:40:25 -0000
Received: from fantadrom.bsd.lv (localhost [127.0.0.1])
	by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 59e1f30d
	for <ml@inbox.vuxu.org>;
	Wed, 6 Jul 2022 09:40:24 -0500 (EST)
Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173])
	by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 1fb9f9c9
	for <tech@mandoc.bsd.lv>;
	Wed, 6 Jul 2022 09:40:22 -0500 (EST)
Received: by mail-oi1-f173.google.com with SMTP id y77so20169318oia.3
        for <tech@mandoc.bsd.lv>; Wed, 06 Jul 2022 07:40:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=imca-cat.org; s=google;
        h=date:from:to:cc:subject:message-id:references:mime-version
         :content-disposition:in-reply-to;
        bh=035ym2ZtZS1Tkjhz3v5PRqLRCb2jWp74INaTHcha4eg=;
        b=OqpklUVVHDXLcFVlxooK7Jf9ztohl8NI0HYmh+VnUZYZ75NooPbjuuy6IBel3SQu/X
         eufWjGuOSo2brEE/ylctZuBKCbcuzcDpC4kN5Zg5fWMWGFkX32hJqUrFJLaBPSms43Na
         Vb/6dPOvpH7d7KxXc9AdkmWS0dRgUIhC9L8Gk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=x-gm-message-state:date:from:to:cc:subject:message-id:references
         :mime-version:content-disposition:in-reply-to;
        bh=035ym2ZtZS1Tkjhz3v5PRqLRCb2jWp74INaTHcha4eg=;
        b=tDjk2043+HFBFdZMYfLd7xWhR9Ah82IlxfES6grSig6ePr30EkFtzcxfaZQgYtS/Wy
         Juq+LPzv6Q0c9UwK9v+N/L1kbHSrohgzj6VNODzB0GkwQsLNK9SRtCqk25P96IH1PiQx
         6CwdJ5xQC8iBNcYwQd7xuy3VjtAtxBVOa4xuWLo0BrMY39o7pqfwnWkcAyy/W2vy9R1u
         FZESzbCNCG+LtGEAtjoXTkPNSfSkM5UIbM9oaR6r/nVEU1XjRA1gP87UPVDs2pDsU++U
         S3BJpi6EibUgFkAN5dtxR+aOh8yN29ttyRk5s+IPF9N5FeC3w5kSZLBgNQn1Q1hphfyf
         usUA==
X-Gm-Message-State: AJIora/9+JXnpR4jV6XN/RbW+OV8BJGa8bPVwrVMjfmi3X/VuZbV13/m
	lGIiE/ISaBqCzBYreZ3Z2UbZtW/I1gXJmA==
X-Google-Smtp-Source: AGRyM1up8Ad9c3Fx3TwBiVvIoFrs5huXUqWk3UZq4IblQ8KhgiwpVt1Wl0xi4sLkf/AX/ZFTXy3lfA==
X-Received: by 2002:a05:6808:1148:b0:339:b283:a1e7 with SMTP id u8-20020a056808114800b00339b283a1e7mr797819oiu.92.1657118421594;
        Wed, 06 Jul 2022 07:40:21 -0700 (PDT)
Received: from localhost ([66.138.188.81])
        by smtp.gmail.com with ESMTPSA id v202-20020acaacd3000000b0033326435494sm15085856oie.41.2022.07.06.07.40.20
        (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
        Wed, 06 Jul 2022 07:40:21 -0700 (PDT)
Date: Wed, 6 Jul 2022 09:40:20 -0500
From: "J. Lewis Muir" <jlmuir@imca-cat.org>
To: tech@mandoc.bsd.lv
Cc: Anna <cyber@sysrq.in>
Subject: Re: patch: avoid multiple <h1>
Message-ID: <20220706144020.hkwn7vrxadhtz3xu@mail.imca-cat.org>
References: <YsWDjxGjXhNvV5lw@asta-kit.de>
X-Mailinglist: mandoc-tech
Reply-To: tech@mandoc.bsd.lv
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YsWDjxGjXhNvV5lw@asta-kit.de>

On 07/06, Ingo Schwarze wrote:
> While the HTML standard explicitely allows documents containing more
> than one <h1>, it contains several examples of header hierarchies,
> and only a single one among these examples contains more than one <h1>.
> That example seems a bit contrived, too.
> 
> Most users expect to find a single <h1> containing the main title
> of the document.  As far as i understand, if there is more than
> one <h1>, that may easily confuse blind users.
> 
> I see no good reason why mandoc should write multiple <h1> headers
> in a single manual page.

Hi, Ingo!

The MDN page at

  https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements

seems to agree with you; in the "Usage notes" section, it says

  Use only one <h1> per page or view.  It should concisely describe the
  overall purpose of the content.

and

  Using more than one <h1> is allowed by the HTML specification, but is
  not considered a best practice.  Using only one <h1> is beneficial for
  screen reader users.

  The HTML specification includes the concept of an outline formed
  by the use of <section> elements.  If this were implemented it
  would enable the use of multiple <h1> elements, giving user
  agents--including screen readers--a way to understand that an <h1>
  nested inside a defined section is a subheading.  This functionality
  has never been implemented; therefore it is important to use your
  headings to describe the outline of your document.

Regards,

Lewis
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv