emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [accessibility] worg obscures text
Date: Thu, 16 Jun 2022 16:30:31 -0700	[thread overview]
Message-ID: <CAJcAo8vK=pZwCauD0ohrdsXSOUq9TNcKS54Z50e4ZsruB3k0Bw@mail.gmail.com> (raw)
In-Reply-To: <87mtedi8pl.fsf@gmail.com>

thank you.  classic works best for me.  a tiny bit made for smaller
fonts [perhaps ragged right or 1 column would work better] but it is
completely usable and i would not mention such a nit except for your
interest.

[as an indicator of right column column width in classic page style,
with smallest legible font size during daylight, worg toc currently
takes 26 mouse pagescroll clicks to get to end from top.  toc at top
taking whole page [a 1 column design] and the items flowed but with
decent margins would take fewer clicks as that would be a bit more
width.  larger fonts would make the number of clicks more.  just fyi.]

[of the other styles, one is white bg so cannot use at night [because
i have not found a good
darkerner extension that does not require running a binary blob to
install it which i stubbornly refuse to do.  the one i use, dark
reader, does not work on some pages for some reason, and it
has other issues re blue on black and too much blue or so]; zenburn is
too bright and uncontrasty for me; and one or
two are obscuring as mentioned.  for my personal use, with my current
settings, classic is definitely good enough.  also, for some reason i
rarely go to worg.]


On 6/15/22, Tim Cross <theophilusx@gmail.com> wrote:
>
> Samuel Wales <samologist@gmail.com> writes:
>
>> on this page, i cannot read the rhs of paragraphs near the top because
>> the menu and up home elements obscure the text.
>> https://orgmode.org/worg/org-faq.html#keeping-local-changes-current-with-Org-mode-development
>> .
>>
>> i use very large fonts.  i have latest esr firefox maximized to the
>> large monitor.  an even larger monitor is not an option.
>>
>> this is probably a minor issue for me as i can probably use ublock to
>> completely remove those elements.  of course that would mean not
>> having those elements but that is ok if there is a table of contents
>> in teh text.  i think there is not though.  also, o that particular
>> patge i can scroll, read paragraph, scroll again.  so i am just
>> reporting so that the issue is known.  i blieve i mentioned it yers
>> ago but idk if it got notated.
>
> Something worth pointing out in case you were not aware of it is that
> the worg pages are defined with alternative stylesheets. Unfortunately,
> alternative stylesheet support is not well supported by browsers.
> However, firefox is one that does support them and as you are a firefox
> users, you may be in luck.
>
> From the 'view' menu, you can select the "Page style" option, which will
> let you select from 1 of three provided styles - default, zenburn and
> classic.
>
> In your case, you will likely find the classic style easier to work with
> as the fonts can be scaled without some content obscuring other (it
> doens't use the Z index to keep things 'on top').
>
> Note that I am working on improving the look of worg and all of this
> will likely change. However, it turns out it isn't as simple as a few
> patches. There is quite a bit of work required to get things 'up to
> spec', especially with respect to accessibility and responsiveness for
> multiple screen sizes.
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com


      reply	other threads:[~2022-06-16 23:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 21:51 [accessibility] worg obscures text Samuel Wales
2022-06-12 19:35 ` Rudolf Adamkovič
2022-06-13  0:22 ` Tim Cross
2022-06-13  0:34   ` Ihor Radchenko
2022-06-13  2:16     ` Tim Cross
2022-06-13  5:30       ` [BUG] worg-setup.org is outdated (was: [accessibility] worg obscures text) Ihor Radchenko
2022-06-13  5:44         ` Tim Cross
2022-06-13  6:14           ` Timothy
2022-06-13 14:21           ` [BUG] worg-setup.org is outdated Bastien Guerry
2022-06-13 14:21         ` Bastien Guerry
2022-06-13 22:32           ` Tim Cross
2022-06-14  0:57             ` Ihor Radchenko
2022-06-14  1:08               ` Tim Cross
2022-06-14  1:37                 ` Ihor Radchenko
2022-06-14  1:51                   ` Tim Cross
2022-06-14  2:18                     ` Ihor Radchenko
2022-06-14  2:46                       ` Tim Cross
2022-06-14  2:59                         ` Ihor Radchenko
2023-01-02 10:40                 ` Ihor Radchenko
2023-01-02 20:03                   ` Tim Cross
2023-01-03 11:01                     ` Ihor Radchenko
2023-01-04 10:21                     ` [TASK] Enhance Worg HTML styling (was: [BUG] worg-setup.org is outdated) Bastien Guerry
2023-01-04 10:50                       ` Alain.Cochard
2023-01-04 22:43                         ` Tim Cross
2023-01-05 14:07                           ` Alain.Cochard
2023-01-05 15:41                             ` Tim Cross
2023-01-05 20:18                               ` [TASK] Enhance Worg HTML styling Leo Butler
2023-01-06  1:23                                 ` Tim Cross
2022-06-13  5:37       ` [accessibility] worg obscures text Max Nikulin
2022-06-16  3:22 ` Tim Cross
2022-06-16 23:30   ` Samuel Wales [this message]

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJcAo8vK=pZwCauD0ohrdsXSOUq9TNcKS54Z50e4ZsruB3k0Bw@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).