Replace some CSS borders with <hr />

The thematic break is appropriate there and it trims down my CSS a bit.

assets/css/main.css

@@ -344,17 +344,6 @@ picture > img {
 	image-rendering: pixelated;
 }
 
-/* WCAG Technique C25: use borders to separate sections.
- * Also use "content-visibility: auto" to improve performance by
- * reducing the number of DOM nodes rendered at once. */
-aside nav,
-footer,
-section[role="doc-endnotes"],
-section[aria-labelledby="webmentions"] {
-	border-top: 1px solid;
-	content-visibility: auto;
-}
-
 /* Make search box and submit button as wide as possible while keeping
  * them next to each other. */
 
@@ -362,6 +351,7 @@ section[aria-labelledby="webmentions"] {
  * single-row flexbox that supports more browsers. Kanged this CSS from
  * ww.gov.uk. Give the entire width of the row to the search box, but
  * allow the minimum width for the submit button. */
+legend, /* Makes the <legend> wrap text in some browsers. */
 form > div {
 	display: table;
 	width: 100%

content/privacy.gmi

@@ -81,8 +81,6 @@ By default, web browsers may share arbitrary information with a server through H
 
 By default, web browsers can share near-arbitrary identifying data with a server by executing near-arbitrary JavaScript, or store this information for future transmission. I have disabled this behavior with a "Content-Security-Policy" HTTP header that forbids script loading ("script-src: none"), script execution ("sandbox"), and making connections for any purpose other than downloading a page a user navigated to ("connect-src").
 
-By default, web browsers may "pre-fetch" DNS queries for links on a page, potentially leaking information to third parties without a user's consent; I have disabled this behavior with the "X-DNS-Prefetch-Control" header. This header is respected by Chromium, Firefox, and Chromium derivatives (e.g. Google Chrome, Microsoft Edge).
-
 By default, user agents using HTTPS may contact a certificate authority to check the revocation status of an TLS certificate. I have disabled and replaced this behavior by including an "OCSP Must-Staple" directive in the TLS certificates used by my Web servers.
 
 By default, user agents using HTTP or HTTPS may share a "referring" location with the destination website when following a link. I have disabled this by sending a "Referrer-Policy: no-referrer" header.

content/privacy.md

@@ -87,8 +87,6 @@ By default, web browsers may share arbitrary information with a server through H
 
 By default, web browsers can share near-arbitrary identifying data with a server by executing near-arbitrary JavaScript, or store this information for future transmission. I have disabled this behavior with a `Content-Security-Policy` HTTP header that forbids script loading (`script-src: none`), script execution (`sandbox`), and making connections for any purpose other than downloading a page a user navigated to (`connect-src`).
 
-By default, web browsers may "pre-fetch" DNS queries for links on a page, potentially leaking information to third parties without a user's consent; I have disabled this behavior with the <code>X-DNS-Prefetch-<wbr />Control</code> header. This header is respected by Chromium, Firefox, and Chromium derivatives (e.g. Google Chrome, Microsoft Edge).
-
 By default, user agents using HTTPS may contact a certificate authority to check the revocation status of an TLS certificate. I have disabled and replaced this behavior by including an "OCSP Must-Staple" directive in the TLS certificates used by my Web servers.
 
 By default, user agents using HTTP or HTTPS may share a "referring" location with the destination website when following a link. I have disabled this by sending a `Referrer-Policy: no-referrer` header.

layouts/partials/footer.html

@@ -1,3 +1,4 @@
+<hr />
 <footer>
 	<p>
 	Copyright <time itemprop="copyrightYear" datetime="{{now.Year}}">{{now.Year}}</time> {{ partial "indieweb-author.html" -}}

layouts/partials/prev-next.html

@@ -2,6 +2,7 @@
 {{- if eq .Page.Section "notes" -}}
 	{{- $name = "note" -}}
 {{- end -}}
+<hr />
 <aside aria-labelledby="continue-hd">
 	<nav aria-labelledby="continue-hd">
 		<h2 id="continue-hd">Continue reading</h2>

layouts/partials/processed-content.html

@@ -10,7 +10,8 @@
 -->
 {{- $referencesWithoutHeading    := `(<div class="footnotes" role="doc-endnotes">
 <hr />)` -}}
-{{- $referencesWithHeading := printf `<section role="doc-endnotes" aria-labelledby="note-hd">
+{{- $referencesWithHeading := printf `<hr />
+<section role="doc-endnotes" aria-labelledby="note-hd">
 <h2 id="note-hd">%s</h2>` ($footnote_heading) -}}
 
 {{- $endnotesClosingDiv := `</a></p>

layouts/partials/webmentions.html

@@ -1,7 +1,9 @@
+<hr />
 <section aria-labelledby="webmentions">
 		<h2 id="webmentions" tabindex="-1">Webmen&#173;tions</h2>
-		<p>This site supports <a href="https://indieweb.org/webmention">Webmentions</a>. Webmentions received for this post will appear in the following list after I approve them. I sometimes send Webmentions to myself on behalf of linking sites that don't support them. Check the <a href="https://web.archive.org/">Wayback Machine</a> if any links are broken.</p>
+		<p>This site supports <a href="https://indieweb.org/webmention">Webmentions</a>, a backlink-based alternative to traditional comment forms.</p>
 		{{ partial "webmention-form.html" . }}
+		<p>Webmentions received for this post will appear in the following list after I approve them. I sometimes send Webmentions to myself on behalf of linking sites that don't support them. Check the <a href="https://web.archive.org/">Wayback Machine</a> if any links are broken.</p>
 		<details>
 			<summary>Toggle Webmentions</summary>
 			<dl>