June Recap — Care Made Visible

Published: July 1, 2026 · Accessible Tech Design

---

THIS MONTH

We spent June on Accessible Tech Design — five fixes for the surfaces you already touch. One fix per Friday newsletter, fifteen minutes each, no full rebuild required.

If you were here all month, you already have the rhythm. If you are catching up, everything lives in one place: pythonessprogrammer.com/accessible-tech-design — all four issues, tools per fix, and the Accessible Tech Checklist PDF to pin above where you publish.

No live event in June. The checklist was the gathering point — and honestly, that matched the bandwidth I had.

This issue is the month closeout: the five fixes in one view, the encyclical frame that held the second half of June, a personal note on what changed when I protected my own energy, and the tarot mirror for the fortnights that tracked the same season.

Thank you for reading along.

---

TLDR

~4 min read

• The month in one line: Can the person on the other end of your screen read, skim, see, hear, and follow what you built?

• Leave-with: Download the Accessible Tech Checklist (PDF) — pin it where you publish.

• Hub: Accessible Tech Design — all four June issues + tools.

• Do this today: Run the checklist against one surface — email, homepage, or your last post. One row counts.

• Go deeper: Magnifica Humanitas · Jill Lepore on the encyclical · Karen Hao's Empire of AI · Accessible Social

• 🔥 Fire Horse principle (Lead with Independence): Protecting your own time and attention is how the work you choose stays honest.

---

MAIN FEATURE

The Five Fixes — All in One Place

#	Fix	Question to ask
1	Readable contrast	Can they read body text and CTAs without squinting?
2	Scannable structure	Can they skim in 10 seconds and know what this is for?
3	Images that communicate	If images failed, would the message still land?
4	Video & audio that include	Can they get the message without sound?
5	Links & flows that do not trap	Does every link say where it goes? Do form labels make sense?

You do not need to pass every row on every publish. The checklist is a memory aid for five kinds of complexity that are easy to forget when you are moving fast.

May's Mindful Automation hub gave us Y.O.U.R. — Reach asks who is on the other end. June added the layer underneath: when volume goes up, your obligation to preview goes up with it. Human eyes. Accessibility first. Then send.

Disarmed, Welcoming, Accessible

From mid-June on, Pope Leo XIV's encyclical Magnifica Humanitas was the wider frame — AI that must be "disarmed, welcoming and accessible," because merely regulating it is insufficient.

Here is how the five fixes map to that charge at your scale:

Leo's word	Your June fix	What it looks like in practice
Accessible	Fixes 1, 3, 4	Readable contrast; alt text; captions and transcripts
Welcoming	Fixes 2, 5	Scannable structure; links and forms that do not trap
Disarmed	All five, cumulatively	Refusing to let efficiency rhetoric outsource care to your audience

Leo writes that technology is never neutral — it takes on the characteristics of those who devise, finance, and use it. Communication works the same way. An image without description is a choice about who counts as your audience. A newsletter laid out by an agent nobody previewed on a phone is a choice too — Week 1 opened on exactly that failure mode.

Magnifica Humanitas landed in a complicated room. Jill Lepore reports that Anthropic co-founder Chris Olah appeared on the dais beside Leo at the release — unprecedented, and freighted with symbolism. Leo urges the public to push back against executives who resist restrictions. He also writes that a more moral AI is not enough if that morality is determined by a few. We do not have "ethical AI" in any finished sense — we have products, incentives, and pattern matchers.

Karen Hao's Empire of AI names the colonial shape of data extraction at scale. The encyclical names the moral failure. Your checklist names what you can hold in mind at your scale when you publish.

Accessible design accepts human limitation — tired eyes, slow connections, brains that skim, bodies that need captions. Alt text and honest links help people who cannot be in the room. They do not replace the room. Show up when you can. Include everyone when you publish.

I philosophize with other decolonizing neurodivergents about how our tech struggles reveal what we have internalized and what our brains actually need. June asked a simpler version of that question: can the person on the other end of your screen actually use what you built?

What I Did With the Extra Bandwidth

I spent June testing a theory: if I protect my own bandwidth, the work I choose to ship stays honest.

The bandwidth part came first. I am officially not on the job hunt right now. I canceled events I had planned but never announced — last-minute life stuff clarified priorities fast. The question that helped was what would I rather not worry about? One answer was a make-believe obligation I had invented for myself. Delete it. Move on.

What filled the room surprised me. I had fallen out of reading for so long that finishing one book felt like a stretch. In June I finished four. I kept starting something new on a weekend and finishing it before the week picked back up — which, for me, is the clearest sign I am not running on fumes.

When I tap into pure enjoyment, I come back to my work with more certainty. June reminded me that output can be a diamond dot painting or a silly little crochet thing — it does not have to be helpful to future-you every single time. It can just be cute and bring joy.

That is how a month ships at newsletter-and-checklist pace instead of sprint-video pace. The work stayed honest because the rest did too. I am logging reads on Fable if you want to follow along.

---

WHAT'S NEXT

Friday we turn the page to Tech Boundaries — auditing where tech drains you, saying no without guilt, and protecting creative energy.

Thank you for spending June on accessible tech design with me — practical, low-spoon, and oriented toward real humans.

See you Friday.

— Amanda

---

Your Accessible Tech hub

All five fixes, the checklist PDF, and fifteen-minute actions live on the Accessible Tech Design resource page — start there if you want the practical version without reading every issue.

The Friday newsletters go deeper on each fix:

• Jun 5: Accessible design is care made visible — start with readable contrast

• Jun 12: Scannable structure — Fix 2

• Jun 19: Alt text is a workflow — not a perfectionism trap

• Jun 26: Five Fixes, One Checklist — Your June Accessible Tech Closeout

Everything before June lives in the full newsletter archive.

---

June resources & sources

Pick what matches how you work.

Leave-withs (Pythoness)

Resource	Best for
Accessible Tech Checklist (free PDF)	Pin-up scan before you publish
Accessible Tech Design series hub	All four June issues + month context
Neuroinclusive Design	Principles + five-minute accessibility check
Mindful Automation	May Y.O.U.R. / Reach bridge
Accessibility Legal Guide	Legal framing — resources hub
Accessible Social	Social posts — captions, alt text, platform advisories

Tools from June's fixes

Tool / setting	Best for
WebAIM Contrast Checker	Fix 1 — start here
Who Can Use	Choosing brand color pairs
WCAG 2.2 — Contrast (Minimum)	Plain-language 4.5:1 rule
WAVE	Quick page scan
The A11Y Project Checklist	Broader sanity check
Bluesky Require alt text before posting (Settings → Accessibility)	Fix 3 — habit without willpower

Reading that shaped June's content

• Pope Leo XIV, Magnifica Humanitas (May 15, 2026).

• Jill Lepore, "What the Pope Said About A.I.", The New Yorker, May 27, 2026.

• Nathan Gardels, "Pope Leo: AI Wealth Must Be Universally Shared", Noema, May 27, 2026.

• Karen Hao, Empire of AI: Dreams and Nightmares in Sam Altman's OpenAI (Penguin Random House, 2025).

• Accessible Social — social media accessibility best practices.

---

SUPPORT THE PYTHONESS

The Pythoness Perspective is free, always. If it helps you, here are ways to support the work:

• Book a reflection session — 20min ($95), 60min ($255), or Async ($75) → pythonessprogrammer.com/services

• Browse free resources → pythonessprogrammer.com/resources

• Shop → stickyspells.etsy.com

• Support → pythonessprogrammer.com/support

• Forward this issue to someone who needs the checklist, not a lecture

Reflection sessions, not rescue. Tech That Works, for People Like Us.

June series hub: pythonessprogrammer.com/accessible-tech-design