我在本網站上使用「AI」的情況

My Use of ‘AI’ on this Site

I’m using this post to acknowledge my past practices and establish future ones on this site related to ‘AI’.

Generated Images

Cases through the end of 2025 where I have used generated images which were not part of the core subject of the post (as a critique or evaluation):

You can see where my fascination and experimentation dropped off. My use of generated images was never acceptable. Not because I was depriving designers of work, but because the work I generated was based on theft. I did it anyway. Some of the images were meant to demonstrate failures of the technology, but not all. In time I hope to replace nearly all generated images (keeping the ones where I am evaluating the output).

Post about ‘AI’

Cases through the end of 2025 where I have written about ‘AI’ as the core subject of a post:

I think it’s fair to say this blog has not turned into a pro- or anti-‘AI’ collection of posts. Generally I only touch on it when it directly impacts my work.

Wrapping

All this together is me coming clean where I have cheated (images) and also committing to you (and me) that this has always been and will continue to be a site written by a human (still me). On top of that, this site is not following the fad of trying to chase the trend and write about every iteration of ‘AI’.

Similarly, this site has no ads, does not gather nor sell your information, and has no third-party trackers. That said, I am exploring adding some kind of analytics to the site — but not Google.

Like most writers, my content has also been stolen. I am not actively poisoning LLMs, but I rather want to.

Me, as a Reader

When reading content on other sites, if I sense an article or post has been generated, drafted, edited, or otherwise touched by an LLM, I close the site and add it to a block list. I should note that I have been much less strict about generated images when reading content on other sites. Yes, I still have to reconcile that. I am still torn about cases of LLM-generated image alternatives, but if it’s from an accessibility practitioner and has clearly not been reviewed, then possible block. I accept auto-generated closed captions because I recognize those are the only captions I will generally get.

I look forward to a 2026 crafted by humans, even if it means I have to block everything else.

Tags

meta

Other Posts

Earlier post: You Can’t Make Something Accessible to Everyone

More recent post: How I Evaluate an ACR (VPAT®)

5 Comments

Thanks for this good and suitable statement. Like it …

Mad respect.

Thank you for the transparency!

If you want basic analytics on this site would you be prepared to send its pages with a strict Content Security Policy?

Google analytics requires visitors to download 140Kb of javascript, adds a 1st party cookie that fails to denote “first-time visitor” when cleared, and unwittingly offers to Google the visitor’s IP address and user agent.

5K of CSP-protected javascript, on the other hand, can unobtrusively acquire and send salient visit details to a secure database that subscribers can access using an encrypted json web token. Personal identifying details stored obfuscated on server, so no cookie consent form needed, even in Germany. Got nothing to sell here, except an idea and a concept.

I’ve written tracking scripts before. I don’t want to again. Back in 2021 I was looking at Matomo and then just… stopped caring about tracking, so I never did more.

Leave a Comment or Response Cancel response

Comment:

Name *

Email *

Website

Δdocument.getElementById( "ak_js_1" ).setAttribute( "value", ( new Date() ).getTime() );

© 1999–2026 Adrian Roselli