

There have been so many places in front end web dev that used the abbreviation “a11y” without defining it (or explaining the 11) that for years I assumed it was just the name of a particular library that had gotten Kleenexed.
(To be clear, I’m using “Kleenexed” as a verb here to mean “genericized explosively, as if a sneeze.”)
It didn’t help to look at the code, either. “Okay cool, so all this does is add a bunch of random extra tags to the DOM? Doesn’t seem super useful but okay, I guess there’s probably some tool out there that depends on them but we probably don’t use it.”
If the instance or community guidelines state “X isn’t allowed,” then it isn’t censorship to remove X. It becomes censorship when mods start removing things for reasons other than enforcing instance or community guidelines. Until that point, it’s just content moderation.
If the c/Androids community guidelines state that “This community is about human-like robots. Posts regarding the phone OS are unwelcome” and a mod removes such a post, that isn’t censorship. Likewise for spam, or reposts, or any number of other things.
On the other hand if the mods remove a post about a human-like robot built in China because they’re sinophobic, that is censorship. Likewise if the human-like robot was built by Tesla, if the lead engineer were a woman, or anything along those lines. Likewise if the post were instead critical of such a robot - still censorship (unless it’s a news only community and the post was free text or a meme).
Likewise if a community’s guidelines state that controversial statements without reputable sources backing them up, statements known to be false, or statements that have been flagged as false by a fact checker are prohibited, then removing such statements isn’t censorship. It’s moderation.