Operation Arlene

Accessibility

Last updated May 20, 2026

How this site is built for older eyes, slower fingers, and screen readers.

Our audience includes people whose vision is not what it once was, whose hands are less steady than they used to be, and who use the web with screen readers, switches, or voice. The site is built with those readers as the default audience, not as an afterthought. This page describes what we have done, what is still in progress, and how to tell us when we have fallen short.

What we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level. That is the standard most public websites in the United States are expected to meet.

What is in place

  • Real headings, in order. A screen reader user can move through the page by headings.
  • Keyboard navigation across the whole site. A “Skip to content” link appears when you start tabbing.
  • Text contrast meets the AA threshold against every background color we use.
  • Form fields have visible labels and a clear focus ring when you tab to them.
  • Photographs of the founder, of scam letters, and of placeholder elements include text descriptions for screen readers.
  • Nothing on the site auto-plays sound, flashes, or traps your keyboard inside an element.

What is in progress

  • A full WCAG 2.1 AA audit by an outside reviewer is on the schedule but has not happened yet.
  • We are testing with VoiceOver on macOS and NVDA on Windows. JAWS testing is next.
  • A few of the older third-party plugins we rely on (LearnDash, Gravity Forms) ship markup we do not fully control. We have reported the gaps we have found and we work around them where we can.
  • Live captions on course videos are coming. Until then, every course video has a written transcript on the same page.

How to tell us something does not work

If something on the site is hard or impossible for you to use, write to us at michael@operationarlene.com. Tell us what you were trying to do, what happened, and (if you can) what device and software you were using. We respond within five business days.

If sending the email is itself a barrier, ask anyone to write on your behalf. We will not insist on hearing from the affected person directly.

Other ways to get the same information

If a specific page is giving you trouble, we will send you the same content as a plain-text email, a printed copy by post, or read through it with you on the phone. Ask.