Enthusiastically Ambiverted Hopepunk
Whatever I’m geeking out about at the time.
Book 51 of 2025: ⭐️⭐️⭐️
The third in Titan Books’s series of Star Trek films “behind the scenes” coffee-table art books, and the second from the team of John and Maria Jose Tenuto. It’s always fun to see all the production art, photos of models and setups, and all the skill that goes into the films. As with the prior books, much of the information I knew, but there are always some gems and stories that I hadn’t come across yet.
📷 I did post an album of photos of the day’s adventures, before, during, and after the protest. I had fun playing a bit with these; the only lens I brought was a Pocket Dispo, a disposable camera lens mounted in a 3-D printed fitting. It gives the images a fun bit of distortion. Definitely not an everyday lens, but fun to have in my kit for when it feels right.
The rest of the week was a pretty standard week, with no particular stories of note.
Read one Star Trek novel, Gene DeWeese’s Into the Nebula.
We finished our rewatch of Scrubs; our first time watching all the way to the end, including the Scrubs: Med School ninth season/spinoff. The first few seasons of Scrubs are definitely the best; much of the latter seasons are very hit-and-miss, but generally still at least amusing.
We also watched Murderbot, which was a really good adaptation of the first book in the series, and even got my wife, not as much of a sci-fi fan as I am, invested and enjoying (most of) the show. The one disappointment was a section in the final episode that fills in a period of time that’s skipped in the book, and which was tonally very different from the rest of the show, enough so that we skipped forward through a chunk of it. Still, overall, really good, and I’m looking forward to the second season when it shows up.
Micah Lee: Unfortunately, the ICEBlock app is activism theater: “Joshua makes strong claims about the security and privacy of his app without backing any of them up with technical details. Many of his claims are false. He also chose to target only iOS, and not Android, because of a misunderstanding about how Android push notifications work. And even worse, during the Q&A, he made it clear that he didn’t understand terms like ‘warrant canary,’ ‘reverse engineering,’ or ‘security through obscurity,’ which doesn’t inspire confidence.”
Jason Aten at Inc.: After 18 Years, This Is Still the Most Useful macOS Feature You Probably Forgot Existed: “…one of the most underrated features in macOS is also one of the oldest: the Guest User account. It’s been around for more than 18 years, first appearing in Mac OS X Leopard in 2007. Yet most Mac users barely remember it exists.” It’s a very clickbait-y headline, but honestly, I’d not thought about the Guest User account in years, and it’s worth keeping in mind.
Book 50 of 2025: ⭐️⭐️⭐️
As is common for this era of Trek lit, a serviceable entry. I figured out the mystery early enough that the rest was just waiting for the characters to catch up.
Book 49 of 2025: ⭐️⭐️⭐️
Anthology of dark, noir-ish fiction inspired by the music (and memories) of the ’90s alternative scene. My favorites were Veronica Schanoes’s “Wendy, Growing Up”, Alex Jennings’s “We’ve Been Had”, Brian Francis Slattery’s “Never Let Me Down”, Silvia Moreno-Garcia’s “Superstition”, and Cyan Katz’s “The Show Must Go On”.
Two additional notes: This is the debut publication for Cyan, whom I’ve known since we were both running around in the 90’s alternative scene in Anchorage, Alaska, and I’m thrilled for them; and I’m sorely tempted to make a playlist/”mixtape” of the inspirational tracks for all the stories in this anthology.
I don’t know exactly when this happened (my best guess is maybe sometime in April, based on this YouTube video; if you watch it, be aware that the output seems to have improved since it was made), but at some point in the not-too-distant past, Google Docs has started including accessibility tags in downloaded PDFs. And while not perfect, they don’t suck!
update: Looks like this started rolling out in December 2024, earlier than I realized. Thanks to Curtis Wilcox for pointing out the announcement link.
For PDFs to be compatible with assistive technology and readable by people with various disabilities, including but not at all limited to visually disabled people who use screen readers like VoiceOver, JAWS, NVDA, and ORCA, PDFs must include accessibility tags. These are not visible to most users, but are embedded in the “behind the scenes” document information, and define the various parts of the document. Assistive technology, rather than having to try to interpret the visual presentation of a PDF, is able to read the accessibility tags and use those to voice the document, assist with navigation, and other features.
However, until recently, Google Docs has not included this information when exporting a PDF using the File > Download > PDF Document (.pdf) option. PDFs downloaded from Google Docs, even if designed with accessibility features such as headings, alt text on images, and so on, were exported in an inaccessible format (as if they had been created with a “print to PDF” function). The only way around this was to either use other software to tag the PDF or to export the document as a Microsoft Word .docx file and export to PDF from Word.
But that’s no longer the case! I first realized this a couple months ago when I was sent a PDF generated from Google Docs and was surprised to see tags already there. I’ve recently had the chance to dig into this a little bit more, and I’m rather pleasantly surprised by what I’m seeing. It’s not perfect, but it doesn’t suck.
I’m not a PDF expert! I’ve been working in the digital accessibility space for a bit over three years now, but I’m learning more stuff all the time, and I’m sure there’s still a lot I don’t know. There are likely other people in this space who could dig into this a lot more comprehensively than I can, and I invite them to do so (heck, that’s part of why I’m making this post). But I’m also not a total neophyte, and given how little information on this change I could find out there, I figured I’d put what knowledge I do have to some use.
Very simple, quick-and-dirty: I created a test Google Doc from scratch, making sure to include the basics (headings, descriptive links, images with alt text) and some more advanced bits (horizontal rules, a table, a multi-column section, an equation, a drawing, and a chart). I then downloaded that document as a PDF and dug into the accessibility tags to see what I found. As I reviewed the tags, I updated the document with my findings, and downloaded a new version of the PDF with my findings included (338 KB .pdf).
More details are in the PDF, but in brief:
<P>.<H1> (or whatever level is appropriate).<Link> with a <Link - OBJR> tag. Link text is wrapped in a <Span>, and the link underline ends up as a non-artifacted <Path>.<Figure> with alt text included. However, images on their own lines end up wrapped inside a <P> tag and are followed by a <Span> containing an empty object (likely the carriage return).<LI> list item includes a subsidiary list, that list is outside of the <LBody> tag, and I’m not sure if that’s correct, incorrect, or indifferent. Additionally, list markers such as bullets or ordinals are not wrapped in <LBL> tags but are included as part of the <LBody> text object. However, this isn’t unusual (I believe Microsoft Word also does this), and doesn’t seem to cause difficulties.<TH> if the header row is pinned (which is the only way I could find to define a header row within Google Docs). However, the column scope is not defined (row scope is moot, as there doesn’t seem to be a way to define row header cells within Google Docs; the table options are fairly limited).<P> containing an empty object (presumably the carriage return, just as with images).So, not perfect…but an impressive change from just a few months ago, and really, the output doesn’t suck! For your basic, everyday document, if you need to distribute it as a PDF instead of some other more accessible native format, PDFs downloaded from Google Does now seem to be a not-horrible option. (My base recommendation is still to distribute native documents whenever possible, as they give the user agency over the presentation, such as being able to adjust font face, size, and color based on their needs. However, since PDFs are so ubiquitous, it’s heartening to see Google improving things.)
If you’ve ever struggled with writing alt text for images, especially for photos that seem difficult to describe, here are six excellent tips from a visually impaired person, posted to Mastodon by @hello@makary.online:
Tell me about the colours, because of all the people who need an alt text, some of us see a little bit, or we used to, so we know what colours are. Even those of us who were born blind, we know intellectually what green is and that it’s the colour of grass, and leaves, and people usually bring it up in the context of life, and hope, and so on. Just because you haven’t seen an atom doesn’t mean that the concept is unthinkable for you, right?
I know what shapes and textures are, if you tell me that something is smooth, I know what smooth is, if you tell me that something is made of cloth, I know how that feels, if you tell me it has sharp edges, I know how sharp edges feel and how they are different from soft, rounded corners.
Give me the context. If it is a character from a book or a series, tell me their name and the title, maybe I know them! I listen to audiobooks and series all the time! If it’s a comic and the people interacting are a couple, it is important, and means something else than if they are siblings, or a parent with a child, or an owner and their dog. If someone on the photo makes an awkward or unhappy face, or grins like crazy, that’s information that helps me get it.
Give me vibes. Describe it to me the way you see it. If you think the drawing of a doll is creepy, say ‘it seems creepy to me’. If the picture of a sunrise makes you feel at peace, tell me ‘It looks really peaceful to me’. Tell me how it makes you feel, be evocative, because that’s what experiencing stuff is, you know, experiencing. If you don’t feel sure about it, also tell me. ‘It feels off and eerie for some reason, but I can’t put my finger on it’ is a very interesting description.
Be a person. AI image descriptions not only sometimes get stuff wrong, but also miss all the context. A robot will not know which part of the picture is important. I am not a robot, neither are you. Just think about ‘how would I describe it to a friend who cannot see it for whatever reason’ and do that. You are not my external eyes, because that’s not possible, you are a person describing stuff to me.
Do as much or as little as you can. You don’t have to write an essay about every meme. Write as much or as little as you can, have time and feel comfortable with. If you give a short or a bad description, I can see that, and that’s what happens in life lol. But if you don’t put ANY description. the whole thing that you thought was important enough for you to share, doesn’t exist at all for me and people like me, and that’s just low-key sad.
Book 48 of 2025: ⭐️⭐️⭐️
Fun short little ‘zine I got at the Seattle Worldcon. Very enjoyably anti-Elon.
Book 47 of 2025: ⭐️⭐️⭐️⭐️
Ordered this just after it won the Best Graphic Novel Hugo award this year. The combination of choose-your-own-adventure plotting and Lower Decks humor works really well. Lots of humor and various Trek callbacks, but with some surprisingly dark moments as well, all leading to a fittingly Trek-ish end. Much fun!
Book 45 of 2025: ⭐️⭐️⭐️
My favorites this month were “Missing Helen” by Tia Tashiro, “The Walled Garden” by Fiona Moore (another of her excellent Morag stories), “Welcome to Kearney” by Gary Kloster, and “Hunter Harvester” by Bam Bruin.
