this post was submitted on 01 Aug 2026
343 points (95.5% liked)

Technology

86783 readers
3670 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
 

Most mass scrapers, on the other hand, simply grab the raw HTML underneath. ShieldFont exploits this difference through an automated process called OpenType glyph substitution.

That said, because the whole defense rests on scrapers reading code rather than screens, taking a screenshot of a shielded page and running OCR on the image can still recover the real words.

Screen readers used by blind readers also work from the code, so they read the decoys aloud. ShieldFont ships with a beta feature that provides those readers with the real text instead.

you are viewing a single comment's thread
view the rest of the comments
[–] sun_is_ra@sh.itjust.works 110 points 1 day ago (4 children)

does this also block blind people who depend on an e-reader?

[–] FTonsilStones@lemmy.ca 72 points 1 day ago (1 children)

Per the article, yes:

Screen readers used by blind readers also work from the code, so they read the decoys aloud.

But:

ShieldFont ships with a beta feature that provides those readers with the real text instead.

[–] ViatorOmnium@piefed.social 74 points 1 day ago (2 children)

ShieldFont ships with a beta feature that provides those readers with the real text instead.

AI scrappers will just pretend to be screen readers then.

And if the approach becomes popular they will just OCR the text instead.

[–] Zarobi@aussie.zone 18 points 1 day ago* (last edited 1 day ago) (1 children)

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.
[–] RobotToaster@mander.xyz 17 points 1 day ago (1 children)

Sounds like an overly convoluted way to do exactly what Anubis does...

[–] Zarobi@aussie.zone 1 points 1 day ago (1 children)

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.

[–] cley_faye@lemmy.world 7 points 1 day ago (1 children)

Unfortunately, most people don’t care

There are laws about accessibility, at least for public websites, and probably for larger websites as they have such a large audience that disability can't be ignored (as much).

[–] Zarobi@aussie.zone 4 points 1 day ago (1 children)

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.

[–] Cricket@lemmy.zip 4 points 20 hours ago* (last edited 20 hours ago) (1 children)

In the US, the Americans with Disabilities Act (ADA) facilitates tons of lawsuits against websites that are not accessible: https://www.rjo.com/publications/website-accessibility-lawsuits-continue-to-inundate-california-courts-despite-covid-19/

Typically, in website accessibility lawsuits, a visually impaired Plaintiff will allege that a company’s website is inaccessible and incompatible with screen-reading software such that the individual is denied full and equal access to the company’s website in violation of the ADA and the Unruh Act. In these cases, a Plaintiff will seek statutory damages, injunctive relief, and attorney’s fees both individually and on behalf of a class of persons similarly situated. Plaintiffs have been testing this theory of ADA liability in courts across the country for years, with New York, Florida and California being the most active.

Edit: here's another good link showing a graph of the number of ADA website accessibility lawsuits from 2016 to 2025: https://www.ecomback.com/annual-2025-ada-website-accessibility-lawsuit-report

[–] Zarobi@aussie.zone 1 points 16 hours ago (1 children)

That sounds nice. Wish we had an ADA, wouldn't even need to change the acronym lol

[–] Deebster@infosec.pub 4 points 11 hours ago (1 children)

You do! It's the DDA (Disability Discrimination Act). A famous case is Maguire v SOCOG 2000 over the Olympic website. Also Coles got sued in 2014.

[–] Zarobi@aussie.zone 0 points 5 hours ago

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.

[–] cley_faye@lemmy.world 7 points 1 day ago

AI scrappers will just pretend to be screen readers then

There's a fair chance they're already doing that. It provides better insight on the content, less formatting to handle, and even visual stuff gets text alternatives.

[–] cley_faye@lemmy.world 16 points 1 day ago

screen reader, SEO, indexation, in page search, etc.

Basically, it breaks everything except people… unless they block/substitute fonts for accessibility reasons, in which case fuck people too.

This is a terrible idea, and it won't even achieve it's original "purpose" as it is trivially detectable. Only negatives in this.

[–] eager_eagle@lemmy.world 15 points 1 day ago (1 children)

it does, unless the reader has an OCR mode of sorts

[–] T156@lemmy.world 9 points 1 day ago (1 children)

Presumably the AI scraper would also have OCR, and would sidestep things like this?

[–] sudo@programming.dev 12 points 1 day ago

A scraper has many more ways around something like sheildfont than just OCR. The question will be if it was actually programmed to check for such measures.

[–] gex@lemmy.world 11 points 1 day ago

Yes, the decoy text is marked aria-hidden, so it won't be read out loud. The real text is sent to the browser encrypted, and the decryption process takes ~20 seconds, roughly the same as running ocr.