<ConanKudo[m]1>
it can be combined with waypipe to do remote wayland apps on macOS
<orowith2os[m]>
ConanKudo[m]1: but unmaintained, and macOS specific - I know owl exists, I was thinking of using their IOSurface protocols later down the line
<ConanKudo[m]1>
it's unmaintained because the upstreaming of the darwin patches for libwayland and others have stalled
<orowith2os[m]>
maybe it would be useful to strip it down and update it to work just for waypipe, to run Linux apps from a container on macOS
<orowith2os[m]>
kind of beside the point though. The main focus is Wayland on top of X11, with SDL3 abstracting most of it away.
<f_>
britney: want me to put a Reported-by: tag or not needed?
<f_>
:P
<f_>
oh, forgot -o, sec
<f_>
typo fixed
jvvv has joined #wayback
<f_>
and btw I made some changes to the website to make it more w3m-friendly and mobile-friendly
<f_>
I'm just a little bit concerned about the website a11y-wise
<axtlos>
first obvious thing to me is lacking alt text on the logo
<f_>
yep
<axtlos>
going from german accessibility standards, the headers also have to be in a semantic order
<axtlos>
the website currently uses h2 directly with no parent h1
<thomas_adam>
I'd also suggest increasing the spacing between the sections: "How does it work?", and "What's the current status?" -- as in, more vertical whitespace; the paragraphs are too close together, IMO.
<axtlos>
oh yeah thats true
<axtlos>
the "how does it work" and "whats the current status" bleed into each other on my end, it looks like it says "[...]needed for a rootfulbe done currently[...]"
<axtlos>
and the gray text in the motto and legal stuff has bad contrast
<f_>
Where does it not use h1?
<f_>
thomas_adam: there should be some padding but I'll add more
<thomas_adam>
f_: If there is padding, I don't see any. So yes, add more.
<axtlos>
f_: I dont see it use h1 anywhere
<axtlos>
its all h2
<f_>
in /docs it uses h1
<f_>
oh but the window thing is h2
<axtlos>
i didnt even know that /docs is a thing
<axtlos>
im just talking about the main page
<axtlos>
oh /docs is the manual link
<axtlos>
i mean using h2 isnt wrong, but there should be a higher level h1
<f_>
there's a h1 in the main page
<f_>
The "Enter Wayback" text is a h1
<axtlos>
yes but its not a toplevel to most other headers
<f_>
True.
<f_>
ok
<f_>
thomas_adam: How's the padding now?
<f_>
axtlos: I tried to make it so that there's a h1 before h2. In the main page everything's h1, but in docs page there's a h1 in the window thing and I consider that to be toplevel
arraybolt3 has joined #wayback
<thomas_adam>
f_: Much better!
<thomas_adam>
f_: Whether grey on white works... hmm... not for me. It's harder to read.
<thomas_adam>
I've also noticed that wayback segfaults when XDG_RUNTIME_DIR is not set -- if no one beats me to it, I'll submit a fix later.
<f_>
thomas_adam: I want the legalese and such to be a bit dim compared to the rest but still readable... if it doesn't look readable to you that's not good
<axtlos>
f_: yep headers look good now
<axtlos>
tohugh text contrast definetly is too low for the gray part, it only scores AA for large text, small text doesn't
<axtlos>
also the Close button should include `tabindex="-1"` if it also has `aria-hidden="true"` to make it unfocusable
<thomas_adam>
f_: Well, my opinion might not represent the minority, but that shade of grey against white is certainly less-readable to me.
<f_>
thomas_adam: I don't care all that much if it represents the minority or not
<f_>
If it's not readable do tell and I'll change it
<f_>
I want it to be readable, not to be readable only for 70% of people when I could do better :P
<thomas_adam>
f_: Try going slightly below true black... that would work.
<f_>
Done, just give it a minute to refresh
<f_>
btw when I said "if it doesn't look readable to you that's not good" .. I really mean it, it's not good
<f_>
and it should absolutely be fixed :p
<thomas_adam>
f_: LGTM!
<f_>
Awesome.
<axtlos>
f_: in case you missed it, the close button should have `tabindex="-1"` so that it cant be focused, otherwise it can trip up people using screenreaders since itll be a button with seemingly no content
<f_>
I didn't miss it
<f_>
will change it in a bit
<axtlos>
alright
<f_>
thanks ^^
<axtlos>
also thanks for caring so much about accessibility
<f_>
you're welcome
<f_>
I haven't yet setup a screen reader on this laptop but I'll need to do it sometime. I had it on my artix install but obviously that all got wiped a few days ago
<axtlos>
i never managed to properly set up a screen reader on my laptops, whenever i need to test it i do it on my phone
<f_>
there's an "Accessibility" tab in firefox-based browsers in the meantime I can use
<f_>
but also I know someone here on libera who's blind and realised how important a11y is
<f_>
also saw a number of blogposts about that
<f_>
Anyway firefox a11y thing now thinks the titlebar doesn't exist
<f_>
awesome
<axtlos>
uhh maybe because of the aria-hidden="true" on it?
<f_>
that wasn't sarcasm
<axtlos>
ohh
<f_>
sorry it wasn't obvious :P
<axtlos>
argh guests also cant approve merge requests on gitlab
<f_>
and btw also regarding !56 because of fossdd's MR I dropped the commit that changes spaces to tabs
<f_>
thanks fossdd :P
<thomas_adam>
Who was it that said fvwm worked under wayback -- that must have been s lie / misconception.
<axtlos>
that was most likely me, neither a lie or misconception, i tested it myself
<axtlos>
let me test with the latest changes
<f_>
It was also me
<f_>
are you having any issues with fvwm in wayback?
<axtlos>
thomas_adam: works for me, built from main
<thomas_adam>
Yeah, OK, that was opimistic.
<axtlos>
if you're having issues with it do tell though
<thomas_adam>
I'll do more than that, I'll submit fixes.
<axtlos>
ah even better, thanks!
<thomas_adam>
The thing about fvwm is it's a damn good reference for whst "good" should be -- and all I see if arrogance from some X replacement. So we need to be aware of this -- it'll take me a while to respond due to other projects.
<axtlos>
yeah no worries, take your time with it
<axtlos>
though theres a reason we dont say we're an X replacement yet, it's our goal for the future ;)
<axtlos>
though out of curiosity, does it just not launch or is it some usability thing?
<f_>
thomas_adam: if you don't have much time, bug reports are always welcome
<axtlos>
admittedly my testing is mostly just launching the de/wm, launching some apps and seeing if it crashes
<axtlos>
so some deeper features i dont know of may be broken
<thomas_adam>
It's a eons way.
<thomas_adam>
s/way/a&/
pinskia has quit [Read error: Connection reset by peer]