works great. thank you for even thinking about such things. if i were to create the tiniest little unnecessary nit for the sake of it, i would say that the toc has unexpected behavior as follows. i didn't notice the toc at first, but when looking for it, i found it, and i hovered and it popped up, and i scroll to see what is in it, and then if i scroll too much, it disappears. then i have to scroll up the page itself to find it again and hover and try not to scroll too much [without knowing where the end is precisely]. idk the fix, but i'd be ok with a plain text inline toc that you have to scroll past to get to the text, but then again i am a fan of simplicity and plain text, which is just me... oh, hmm, actually plain text is a key selling point of this whole active markup language thing :)
On Thu, May 29, 2025 at 1:44 AM Christian Moe <m...@christianmoe.com> wrote: > > Hi! > > I'm trying to fix an accessibility problem with the styling of the Worg > pages, originally reported by Samuel Wales and discussed in this thread: > https://list.orgmode.org/CAJcAo8uTOpEazLNCr0t1kFqPGTLz=G=adnklhuo1-ura8-m...@mail.gmail.com/ > > I would be grateful if a few people could try out a style change and > drop me a note here before I implement it next week. I'd like to know > that the accessibility problem is fixed, that I haven't inadvertently > created new ones, and any feedback on the layout. > > Problem: With narrow screens / large fonts, the text is obscured by > items on the right. An earlier partial fix hides the Table of Contents > on narrow screens, but that makes the TOC unavailable and still leaves > clashing items. > > Tested solution: Position the UP|HOME and LiberaPay links absolutely on > the top of the page to scroll away with the text. Keep the TOC fixed to > the right, but when the screen is narrow, position the TOC relatively > under the heading in the normal document flow. Keep the collapse/expand > behavior of the TOC unchanged. Shrink the unicorn logo on narrow screens > (consider hiding it instead). > > How to test: > > If your browser does not support alternate stylesheets, you > can see the fix in action on this one page: > > https://orgmode.org/worg/org-syntax.html > > In Firefox, you can open any Worg page with the current "Standard" > stylesheet and then switch to the proposed "Test" alternate stylesheet. > In the View menu (tip: press Alt to display the old-style menu if > hidden), select the "Test" stylesheet (View > Page Style > Test). > > Try narrowing the window, or increasing and decreasing the font, in > either style. How does it look? > > Yours, > Christian > -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com
