Five Fixes, One Checklist — Your June Accessible Tech Closeout

This month we worked through five fixes for the digital surfaces you already touch — site, newsletter, social, onboarding, link-in-bio. One fix per week, fifteen minutes each, no full rebuild required.

New here? Here is the arc at a glance:

1. Readable contrast — text people can read at the end of a long day

2. Scannable structure — skim in ten seconds; headings and short blocks

3. Images that communicate — alt text workflow; text not trapped in images

4. Video and audio that include — captions reviewed; message without sound

5. Links and flows that do not trap — links say where they go; forms make sense

If you have been here all month: today we close with Fixes 4 and 5, then recap all five as one system.

Fix 4 and Fix 5 are where Neuroinclusive Design principles meet the platforms you already use — Flexible Interaction (different ways to complete a task) and Explicit Communication (clear language, no ambiguity). Captions and honest links are care made visible for the human on the other end of the screen.

This is also the week the Accessible Tech Checklist lands — your pin-up leave-with for June. The printable PDF is live: download it, print it, and pin it above where you publish. No live event this month; the checklist is the gathering point. Browse the full Accessible Tech Design series hub for all four issues and month context.

~4 min read

• This week: Fix 4 (captions and transcripts) + Fix 5 (descriptive links and form labels) + full recap of all five fixes.

• Do this today (30 minutes total, or split): Turn on captions on your last published video or add a 3-line text summary. Rewrite five "click here" links to say where they go. Fix one confusing form label.

• Primary resource: Download the Accessible Tech Checklist (PDF) — pin-up scan before you publish

• Series hub: Accessible Tech Design — all four June issues + month context

• Go deeper when ready: Neuroinclusive Design · Accessibility Legal Guide on resources · Accessible Social for social-post depth (captions, alt text, platform quirks)

• July preview: Tech Boundaries — auditing where tech drains you; free workbook ships early July.

• 🔥 Fire Horse principle (The Record Is the Guide): Pin the checklist where you publish — a quick scan beats a vague "be more accessible" intention.

Part 1: Fix 4 — Video & Audio That Include

The check: Can someone get the message without sound or with low attention?

Lens	Pick one surface this week	What to change
Small business	Sales video, tutorial, Zoom replay, podcast episode page	Captions on; transcript or summary linked nearby
Chronically online	Reel, TikTok, live replay, audio clip	Auto-captions reviewed (they are not perfect); critical info duplicated in caption or pinned comment

Your 15-minute action: On your last published video or audio piece: enable captions, skim for errors on names and jargon, and add a three-line text summary in the description or first comment if a full transcript is not realistic yet.

A transcript is the full text of everything said. A summary is the shortcut — three lines covering what someone needs to know if they cannot watch with sound. Start with the summary if a full transcript feels like too much this week.

Do it on the platform you already use: YouTube auto-captions + edit. Instagram/TikTok caption tools. Zoom cloud recording → transcript export. Descript, CapCut, or native editors — use what you already touch, not a new stack.

Part 2: Fix 5 — Links & Flows That Don't Trap

The check: Does every link say where it goes? Can forms be completed without guessing?

Lens	Pick one surface this week	What to change
Small business	"Book now," checkout, contact form, client portal	Replace "click here" with "Book a 20-minute session" / "Download the workbook." Visible labels on every field.
Chronically online	Link tree, newsletter signup, DM → calendar flow	Descriptive link text; thumb-tap targets; say what happens after submit

Bad → better

• "Click here" → "Register for the June workshop (Luma)"

• "Learn more" → "Read the Neuroinclusive Design guide"

• "Submit" alone on a long form → "Send my message to Amanda"

Your 15-minute action: Rewrite five "click here" or "learn more" links. Fix one form label that currently only makes sense if you already know your own business.

Do it on the platform you already use: Carrd, Linktree, Beacons, Squarespace buttons, ConvertKit forms, Cal.com embeds — all allow custom button text and field labels.

Part 3: Someone on the Other End — The Mystery Button

A client taps Book now on your link-in-bio. They land on a generic scheduling page with no context — no service name, no price range, no "what to prepare." They close the tab. They tell themselves they will come back. They do not.

You had a booking link. You did not have explicit communication — Fix 5's lane.

Pair that with a tutorial video that only makes sense with sound on (Fix 4), and you have hosted the tools, not the human.

Reflection prompt: Trace one path from social → booking → confirmation. Where is the first place you would get lost if you were tired?

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 read, skim, see, hear, and follow what you built? Five fixes. Fifteen minutes each. That is the whole month in one sentence.

Part 4: June Recap — All Five Fixes

#	Area	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	If images failed, would the message still land?
4	Video & audio	Can they get the message without sound?
5	Links & flows	Does every link say where it goes? Do form labels make sense?

You do not have to pass every row on every publish. The checklist is there so you remember what "accessible" actually covers — contrast, structure, images, sound, and paths — when you are moving fast.

Part 5: Month Close — Disarmed, Welcoming, Accessible

If you have been reading since mid-June, Pope Leo XIV's Magnifica Humanitas has been 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

One line I am carrying into July: accessible design accepts human limitation — tired eyes, slow connections, brains that skim, bodies that need captions. Captions 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.

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.

Part 6: Your Leave-With

Download: Download the Accessible Tech Checklist (PDF)

Print it. Pin it above where you publish. Scan any page, post, or send against the five areas — no scorecard required.

Browse the full June series: Accessible Tech Design hub

When your system needs a full redesign — navigation, forms, client journey, brand surface — that is what Deep Dive ($255) is for: pythonessprogrammer.com/services. Reflection sessions, not rescue.

Every hub, tool, and source from this month lives in June resources & sources at the end of this issue.

June resources & sources

You do not need everything here — pick what matches how you work.

Leave-withs (Pythoness + shop)

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 — hospitality before June
Accessibility Legal Guide	Legal framing + 90-day plan — resources hub
Accessible Social	Social posts — captions, alt text, copy, platform advisories

Tools from this month's fixes

Tool / setting	Best for
WebAIM Contrast Checker	Fix 1 — start here
Who Can Use	Choosing brand color pairs
TPGi Colour Contrast Analyser	Sampling colors from a live site, PDF, or screenshot
WCAG 2.2 — Contrast (Minimum)	Plain-language explanation of the 4.5:1 rule
WAVE Web Accessibility Evaluation Tool	Quick page scan (contrast is one of several checks)
Firefox Accessibility Inspector	Built-in contrast check on elements already on your page
The A11Y Project Checklist	Broader sanity check beyond contrast
Bluesky Require alt text before posting (Settings → Accessibility)	Fix 3 — habit without willpower
YouTube / native caption editors	Fix 4 — review auto-captions on names and jargon

Reading that shaped this arc

• Pope Leo XIV, Magnifica Humanitas: On Safeguarding the Human Person in the Time of Artificial Intelligence (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.

Your tech struggles, reflected back.

This week's prompt:

Which area on the checklist catches you most often — and on what kind of post or page? (Reply helps me see what lands.)

Hit reply. I read every one.

🔥 The Fire Horse's Callout: What to Charge Forward With

Pin the checklist where you publish. It is not bureaucracy — it is a memory aid for five kinds of complexity that are easy to forget when you are moving fast.

Accessible design is care made visible. June gave you five areas to keep in view without rebuilding your life.

🔥 Charge forward with: One post or page you will scan against the checklist before it goes live.

WHAT'S NEXT

July opens Tech Boundaries — where tech drains you, how to say no to tools and platforms, and protecting creative energy. The free Tech Boundaries Workbook ships with the first July issue. Details coming in the July arc.

Thank you for spending June on accessible tech design with me — practical, low-spoon, and oriented toward the people on the other end of your screen.

See you in July.

— Amanda

• 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 wants a checklist, not a lecture

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

Part of the Accessible Tech Design series — pythonessprogrammer.com/accessible-tech-design

Resource hub: Neuroinclusive Design