From: Philip Kaludercic <philipk@posteo.net>
To: John Haman <mail@johnhaman.org>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: Improvements to Emacs documentation accessibility
Date: Wed, 12 Oct 2022 17:17:21 +0000 [thread overview]
Message-ID: <87y1tl6jxa.fsf@posteo.net> (raw)
In-Reply-To: <da367710-3561-e534-f555-d8f73d9c2729@johnhaman.org> (John Haman's message of "Wed, 12 Oct 2022 12:16:43 -0400")
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
John Haman <mail@johnhaman.org> writes:
>> AFAIU that means you somehow landed on an outdated page
>
> I don't think it is outdated. Attaching an image that shows an example.
>
> To me, it does not look like a mobile website.
I just tried it out in Firefox using the "Responsive Design Mode" (that
allows you to preview how a page looks like on a mobile device).
Interestingly enough the page did at first appear just like in your
screenshot, but when I slightly resized the frame it did appear like a
regular "mobile site" (hopefully attached below).
The site is missing a viewport-meta tag which is regretfully necessary
for normal pages to behave like normal pages on mobile screens. Adding
that ought to help, but that should be done by the texinfo/makeinfo
maintainers.
> On 10/12/22 9:44 AM, Po Lu wrote:
>> John Haman <mail@johnhaman.org> writes:
>>
>>> I noticed while browsing the Emacs manuals on my mobile phone that the
>>> accessibility is very poor. The text is very small which makes it hard
>>> to read without zooming and scrolling.
>>>
>>> The layout of the texinfo html is classic, but would the community
>>> would be open to making the docs more readable on small devices? (like
>>> mobile phones and tablets)
>>>
>>> I'm not a web developer, but I believe the solution would involve some
>>> improvements to the CSS of the documentation to add word-wrapping and
>>> maybe increase the font size.
>>>
>>> I'm happy to help.
>> AFAIU that means you somehow landed on an outdated page, since the
>> latest ones have been generated to work well on mobile browsers as well.
>>
>> At least that's the conclusion last bug report about this led to. Feel
>> free to correct me if I'm wrong.
[-- Attachment #2: Type: image/png, Size: 249127 bytes --]
next prev parent reply other threads:[~2022-10-12 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 12:37 Improvements to Emacs documentation accessibility John Haman
2022-10-12 13:44 ` Po Lu
2022-10-12 16:16 ` John Haman
2022-10-12 17:17 ` Philip Kaludercic [this message]
2022-10-12 17:29 ` Eli Zaretskii
2022-10-12 18:20 ` Philip Kaludercic
2022-10-12 18:38 ` Eli Zaretskii
2022-10-12 13:47 ` Eli Zaretskii
2022-10-13 3:31 ` Stefan Kangas
2022-10-13 6:08 ` Eli Zaretskii
2022-10-13 18:13 ` Bastien
2022-10-13 18:23 ` John Haman
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=87y1tl6jxa.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=mail@johnhaman.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.