diff --git a/assets/css/main.css b/assets/css/main.css
index 2679b87..d5accf5 100644
--- a/assets/css/main.css
+++ b/assets/css/main.css
@@ -305,7 +305,7 @@ picture > img {
 /* 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,
+aside nav,
 footer,
 section[role="doc-endnotes"],
 section[aria-labelledby="webmentions"] {
diff --git a/content/notes/answer-engines.md b/content/notes/answer-engines.md
index 9e2ef7d..0751f31 100644
--- a/content/notes/answer-engines.md
+++ b/content/notes/answer-engines.md
@@ -2,9 +2,11 @@
 title: "Answer engines"
 date: 2022-05-25T19:59:08+00:00
 ---
-<p role="note">
+<aside role="note">
+
 Reply to {{< mention-work itemprop="about" itemtype="BlogPosting" reply=true >}}{{<cited-work name="Is DuckDuckGo, DuckDuckDone?" extraName="headline" url="https://kevq.uk/is-duckduckgo-duckduckdone/">}} by {{<indieweb-person first-name="Kev" last-name="Quirk" url="https://kevq.uk/about/" itemprop="author">}}{{</mention-work>}}
-</p>
+
+</aside>
 
 I read your article and share similar concerns. Using Microsoft Bing and Google Search's commercial APIs generally requires accepting some harsh terms, including a ban on mixing <abbr title="Search Engine Result Pages">SERPs</abbr> from multiple sources (this is why Ixquick shut down and the company pivoted to the Google-exclusive Startpage search service). But the requirement to allow trackers in a companion web browser was new to me.