

You think only aria-attributes are accessibility? Most accessible is, what you not need additional tools and interpreters for.
You think only aria-attributes are accessibility? Most accessible is, what you not need additional tools and interpreters for.
https://lemmy.zip/comment/19872383
Usability by third-parties. A webpage is not a pdf.
Now it is remembering tags for property instead.
Why Tailwind if you have CSS variables?
Oh wow, a framework that needs a framework.
Would be fine if it used a custom parameter for their tags. Using class names makes for bad accessibility.
As one who creates usercss to fit pages to my needs, Tailwind is second worst.
scrolling
Wasn’t there a community gor nonsensical error messages?
Human needs more water and less energy, yes.
Dynamically loading pages suck too.
And if not they have sed or ed or echo and cat.
I think i’ve read something about (pseudo-)RISC architectures not allowing universal drivers for whole families, each must exactly match to the hardware.
That’s a miniature sofa.
You absolutely can regex (some) html if you sanitize and maybe convert it beforehand.
Btw, why are parsers always built to support the whole thing and maybe throw an error on or just consume unsupported shenanigans? That’s how you get security vulnerabilities in picture formats. Instead of just picking the things you support and ignoring the rest.
Btw, pylance is proprietary. There’s Kylin for jedi as alternative.
For the how: https://xkcd.com/2044/
Look, if it hinders me in my workarounds for my ADHD while every other framework does less so, then accessibility is worse. Shut up with your trademark gatekeeping bullshit.
Also,