If even one out of every ten accessibility advocates/experts/etc. did these things, then all these bugs would’ve been fixed years ago.
Maybe you're aware of an OOM more accessibility advocates than I am, but I come across all sorts of well-written blog posts explaining this or that bug, which browser/etc. it happens in, and how to work around it. That's most of the bullet points, although it might not be in the bug tracker of choice for the project.
What people aren't doing, as far as I have seen, is starting pooled-funds bug bounties for these things. People pass the collection plate for childhood cancer, especially since I'm told that September is Childhood Cancer Awareness Month, but not bugfixing.
This is not insensible: all sorts of people tend to be unwilling to set aside the cost of a new cell phone to fix one bug apiece that, generally speaking, is encountered in one's day job.
And there are a lot of accessibility bugs out there, some of which are quite old. I can only assume that accessibility bugs aren't treated massively more seriously than anything else in the WebKit or Firefox Bugzillas.
While the world would be a better place if bug-bounty collection plates were more popular, I can see why they're not as popular as I'd like.
They do not have any incentive whatever to help to fix bugs in screen reader programs. What would that do for them? The better such programs work, the less work there is for these people to do, the less there is to talk about on the subject of how to make your website accessible (“do nothing special, because screen readers work very well and will simply handle your website properly without you having to do anything or think about the problem at all” hardly constitutes special expertise…), the less demand there is for them on the job market…
You don't even need to describe this as a baptist-and-bootleggers problem to explain most of the lack of actual bug fixing.
A frontend developer who runs into accessibility-related browser bugs all day and gets very good at working around them and publicizing how to work around them is unlikely to be a competent C++ developer who is capable of going into browser-engine codebases and actually fixing the bugs.
While I can imagine why others would want to see this sort of thing, it seems to me that "this will go on your permanent record" would be a strong disincentive to engage seriously with the text or mention anything aloud that you wouldn't be comfortable with anyone in the world, ever, knowing about you.
I do actually have plans to learn enough html to swap my Wordpress site over to a self-hosted self-designed website, I just have to, like, get good enough with HTML and CSS and especially CSS to get Gwern’s nice sidenotes
You can start with the Dan Luu aesthetic and then redesign your site, either incrementally or in big leaps, possibly repeatedly, later. Redesigning websites is totally a thing. https://gwern.net gets near-constant upgrades, and all sorts of famous web-nerd bloggers have improved their sites' designs over the years and now decades.
and hosting and how to do comments. It’s gonna happen, though. Any day now.
One thing Substack does that you can't get super-easily from a static site is comments and emailing your readers with new articles (feeds are, unfortunately, mostly a nerd-only technology).
I'd like to second this comment, at least broadly. I've seen the e notation in blog posts and the like and I've struggled to put the × 10 in the right place.
One of the reasons why I dislike trying to understand numbers written in scientific notation is because I have trouble mapping them to normal numbers with lots of commas in them. Engineering notation helps a lot with this — at least for numbers greater than 1 — by having the exponent be a multiple of 3. Oftentimes, losing significant figures isn't an issue in anything but the most technical scientific writing.
Is there an alternative to constantly adding endless features? Can software be designed to operate without daily updates, similar to programming languages?
"daily" in "daily updates" is hyperbole, but you can probably get most of the way there with
prefers-color-scheme).The second bullet point is important, at least occasionally. I dropped my beloved VoodooPad because it never got a publicly-released version that supports dark mode that works on macOS, iOS, and iPadOS. I figure VoodooPad is nearly dead because its current owners can't figure out how to turn it into something that gets enough revenue to justify the time that it would take to make it a modern app.
At any rate, the notes I had in VoodooPad got moved into Ulysses some time after the Ulysses team added projects back in 2022. Ulysses is not a good personal wiki (internal linking isn't nearly as low-friction as in Obsidian), but it's adequate for my purposes and I dislike having a gazillion different personal-wiki software packages that I need to divvy my attention between.
As far as update cadence goes…
If you look at Ulysses' Releases page and make note of the dates in the headings, you can see that they've been steadily, but not all that quickly, been releasing features. There's probably at least one programming language out there with this release cadence, but I wouldn't know which one it is.
Cassandra/Mule: If Alice knew she were talking to a brick wall, she would give up; and if Bob knew Alice was trying to help, he would actually listen.
I've seen mules in the wild in internet forums (which, admittedly is outside the scope of your post). They usually present as ardent defenders of the faith, repeating well-known talking points…and never updating, ever.
AI safety posts generally go over my head, although the last one I read seemed fantastically important and accessible.
AI-safety posts are probably the most valuable posts here, even if they crowd out other posts (both posts I think are valuable and posts I think are, at best, chaff).
If there were one dial I’d want to experiment with turning on LW it would be writing quality, in the direction of more of it.
I'd like to highlight this. In general, I think fewer things should be promoted to the front page.
[edit, several days later]: https://www.lesswrong.com/posts/SiPX84DAeNKGZEfr5/do-websites-and-apps-actually-generally-get-worse-after is a prime example. This has nothing to do with rationality or AI alignment. This is the sort of off-topic chatter that belongs somewhere else on the Internet.
[edit, almost a year later]: https://www.lesswrong.com/posts/dfKTbyzQSrpcWnxfC/2025-color-trends is an even better example of off-topic cross-posting that the author should not be rewarded for doing.
400 kcal/kg/day, right?