From: "Rito Rhymes" <rito@ritovision.com>
To: "Jonathan Corbet" <corbet@lwn.net>,
"Rito Rhymes" <rito@ritovision.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
<linux-doc@vger.kernel.org>
Cc: "Shuah Khan" <skhan@linuxfoundation.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] docs: rework footer with semantic markup and responsive layout
Date: Wed, 25 Mar 2026 20:28:13 -0400 [thread overview]
Message-ID: <DHCAEAFI1J0N.KA5JCQIP7BWS@ritovision.com> (raw)
In-Reply-To: <87bjgbecgw.fsf@trenco.lwn.net>
> We are not going to fix Sphinx accessibility piecemeal in this
> way. If that is really the objective, I think the right thing
> is to work with the Sphinx project directly and come up with a
> proper plan for all of their major elements. Tweaking the
> footer - the contents of which will be read by the screen
> reader and understood just fine - doesn't really address that
> problem.
I see where you're coming from.
In that case, I can reroll this as a CSS-only override for the mobile
rendering issue and drop the markup change.
I agree that the semantic footer question is better handled upstream in
Sphinx rather than piecemeal here.
If that direction works for you, I'll send a reroll accordingly.
Rito
next prev parent reply other threads:[~2026-03-26 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 13:18 [PATCH] docs: rework footer with semantic markup and responsive layout Rito Rhymes
2026-03-22 18:22 ` [PATCH v2] " Rito Rhymes
2026-03-25 19:28 ` Jonathan Corbet
2026-03-25 22:33 ` Rito Rhymes
2026-03-25 23:06 ` Jonathan Corbet
2026-03-26 0:28 ` Rito Rhymes [this message]
2026-03-26 0:58 ` [PATCH v3] docs: restore and reflow footer on narrow screens Rito Rhymes
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=DHCAEAFI1J0N.KA5JCQIP7BWS@ritovision.com \
--to=rito@ritovision.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.org \
/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