Zarobi

@Zarobi@aussie.zone · Joined ⁨Jun⁩ ⁨2026⁩

Replying to @⁨Deebster@infosec.pub⁩

I always used to quietly rebel against my boss when I did web development work. I’d spend the time making the pages actually accessible to screen readers and tab navigation and such. Even fixing my coworkers’ code to be compliant.

I always thought it was a fun minigame, and it didn’t even take that long. Little things like, icon buttons also need a text label, tabbing needs to follow a logical layout, shortcuts to jump to different parts of the page, actual tables and description lists.

I used to get in a lot of trouble for “wasting time” because “no blind people are using our software.” Years later an audit happens and my boss is shitting himself. We get a passing grade for accessibility. I never got any recognition for it, but he stopped yelling at me for wasting time after that and just let me do my thing.

Replying to @⁨cley_faye@lemmy.world⁩

In my experience, those laws aren’t followed much in reality. The biggest sites, sure, but most smaller sites are a mess under the hood. As long as something is “technically usable”, even if very awkward and annoying, it’s often hard to sue or anything like that. Maybe it’s different in other countries though, I live in Australia.

Next time you use a website, try only using your keyboard to navigate it and accomplish your task, and you’ll see what I mean. It’s a rough test of how much they value accessibility. For example, many websites disable the border around what you’re highlighting, so you have no idea what the tab button is about to click. Or popup windows don’t actually change your tab selection, so you have to tab through literally the entire page in the background to get to the popup window. Stuff like that; technically usable but annoying as hell.

Replying to @⁨RobotToaster@mander.xyz⁩

Yeah, if you care about screen reader users, functionally it’s just “Anubis but worse”. Unfortunately, most people don’t care, so for them and all visual users, it has the benefit of no additional “load time” computational check — the page appears instantly without the Anubis step. Though I’m not sure how long it takes the page to do the de-scrambling.

The primary purpose of this project is to mutilate your HTML so bots can’t scrape it, rather than preventing bot traffic in the first place. The screen reader stuff is a bolt-on.

Replying to @⁨ViatorOmnium@piefed.social⁩

Per the GitHub:

Accessibility layer<Shield> hides protected regions from assistive tech and ships an a11y prop that renders a real alternative beside them — mode: “text” puts your words in the page encrypted behind a time-lock puzzle the reader’s browser opens (no link for a scraper to follow, no artifact for you to host), or mode: “audio” points at a recording you make. What remains: NVDA and JAWS verification (VoiceOver is done by hand, Windows is not), the focus indicator a sighted keyboard user loses to an invisible control, and the non-React tiers shipping none of it.

In summary, they have two ways to get around this.

  • By default, blind people are fucked as usual. Most everything is unusable via screen reader just due to the way modern websites are designed.
  • Audio mode pre-records an audio file of your text, and plays that, bypassing the screen reader. This is extremely horrible UX for screen readers, for anything more complicated than a wall of text, but at least it’s something.
  • Text mode will do some sort of computational challenge, using CPU on the blind person’s machine for a few seconds, then revealing the original unmolested text. Assuming this works properly, because screen readers are extremely fragile beasts.

Replying to @⁨theherk@lemmy.world⁩

That’s a bit misleading.

A bunch of links in an unlisted share directory were indexed and crawled by Google. A Reddit user found them via Google Dorking, and discovered private conversations they shouldn’t have had access to. It’s not clear how Google discovered these links. To prevent this, Anthropic should have added a “no index” flag to this directory, which they have fixed now.

Replying to @⁨captainlezbian@lemmy.world⁩

It gets down to 4°C sometimes where I live, so not that harsh comparatively. I’ve experienced -5°C when traveling and it’s a whole different thing, my Australian ass was not equipped for that environment lol. Let alone -20, I’d probably just die. But above 0 it feels like good pants are probably good enough.

Honestly the bigger problem here is the opposite; on a 40°C day the seats and steering wheel become lava. I keep gloves in the car just to not burn myself in summer. I wouldn’t mind “cooled” seats and steering wheel instead of heated, but that sounds harder to pull off somehow.

It’s not the first tone deaf car feature sold in Australia, though. The worst are the holes in the ceiling to let the sun in. Free skin cancer for everyone!

Replying to @⁨sanitation@lemmy.today⁩

I think we found the service that’s responsible for astroturfing Reddit with thousands of memes / ads per day. The real question being asked is, is it breach of copyright to use an artist’s work for commercial uses? Probably yes. If it were a human doing it.

A.I. makes things complicated though, because it’s almost entirely created by plagiarised work in the first place, so that can of worms remains mostly sealed.