Around 2008 I worked with a nonprofit whose own board member could not use the organization's website. They relied on a screen reader, and the site gave it nothing to work with: no descriptions on the images, no logical order to the navigation, no way to reach the menu without a mouse. Nobody had locked him out on purpose. Nobody ever does, and that is the whole problem with accessibility: it fails quietly, to people the analytics never count, until one of them sits on your board.
Episode 7 of The Web Managers Podcast is built around that project and the claim it taught me: design, mobile, and accessibility are systems, not talents, and an accidental web manager can build all three. This post is the companion: the brand kit, the argument that the phone is the site, the eight accessibility fixes, an honest word about the widgets sold as shortcuts, and a quick win shorter than the episode.
Why this sits in Security Month
Accessibility belongs in a month about risk for two reasons. The Web Content Accessibility Guidelines (WCAG) at Level AA are the working legal standard, and demand letters under the Americans with Disabilities Act (ADA) reach small organizations because the scanners that find non-compliant sites do not check headcount first; a dated record of good-faith work changes that conversation. And the same clean structure that serves a screen reader, real headings, described images, meaningful links, is what the artificial intelligence (AI) systems deciding whether to cite you also read.
The brand kit that fits on a page
The episode's first system is a minimum viable brand kit: a folder holding the logo in the formats people actually request, including the original vector file, and a page recording two fonts from Google Fonts, four colors as hex codes, one sentence of photo guidance, and a few sentences on tone. Enforcement is where kits fail, because policing does not survive a busy week. Set the website's theme to the kit once, lock Canva templates to its palette, and the consistent path becomes the easy one.
The phone is the site
For years the phone version of a website was treated as an accommodation, checked after the real site was finished. The traffic settled that argument: mobile devices carry the majority of visits for most small-organization sites, and for local businesses found through search, the share runs higher. The phone version is the site, and the desktop view is the secondary one.
Responsive templates guarantee only that a site fits a phone, not that it works in a hand. Readability means no pinching to read the text. Touch targets must be large enough to hit with a thumb on the first try, roughly the size of a key on a physical keyboard. Thumb reach means the actions that matter, call, directions, donate, menu, belong in the lower half of the screen rather than huddled at the top. The first screenful is the most valuable property on the site, and most organizations spend it on a welcome banner while the hours and the phone number wait below.
The test is free: your own site, your own phone, on a cellular connection rather than office WiFi. Count the seconds, read without zooming, tap every button with a thumb, fill out the contact form, and confirm that tapping the phone number starts a call. Everything that made you squint, miss, or wait is your design to-do list.
The eight fixes
Most accessibility failures on small sites concentrate in eight items, and a careful non-designer can fix every one from ordinary editing screens. Alt text on every meaningful image, the most common failure on the web and the cheapest to repair. Color contrast that passes WCAG AA, which the free WebAIM Contrast Checker scores from your brand kit's hex codes in seconds. Real headings, nested in order, because screen readers and search engines both move through a page by structure. Link text that says where the link goes. Keyboard operability, so Tab and Enter reach every menu and form. Visible form labels. Captions on video. And never letting color alone carry meaning, as in "fields in red are required." The free WAVE scanner finds most violations of the first six automatically.
One reframe makes the list easier to sell to a board: almost every fix helps people who would never call themselves disabled. Captions serve the commuter on a loud train, contrast serves every phone in direct sunlight, and keyboard operability serves the visitor whose trackpad just died. Curb cuts were built for wheelchairs and promptly adopted by strollers; accessibility work behaves the same way.
Myth busted: the widget that promises compliance
Accessibility overlays are widgets that promise compliance through one pasted line of code. The promise does not hold. An overlay cannot repair the page structure assistive technology depends on, many screen-reader users report overlays interfering rather than helping, and organizations running them still appear in accessibility complaints. An overlay is a sticker over the lock; the eight fixes cost less and repair the door itself.
Also in this episode
The Question Line takes on a vendor quoting a zero-budget nonprofit board $490 a year for an overlay "for full ADA compliance," and the episode scripts the honest counter-proposal. The Tool Minute covers the WebAIM Contrast Checker, which turns two hex codes into a pass or fail in about sixty seconds.
Quick win: WAVE your homepage
Open wave.webaim.org and enter your homepage address.
Note every missing alt text the scan flags.
Add a one-sentence description to each image in your platform's normal image settings, describing what it shows and why it is there.
Date the scan and keep the report. It is the first entry in an accessibility record you may someday be glad to have.
Done looks like zero missing alt text on the homepage and a dated report saved where the next person can find it.
Get the worksheet. The M6.1 10-Point Accessibility and Mobile Self-Audit scores your site pass or fail on the eight fixes plus the phone test, ranks the fixes by priority, and includes the brand kit template. It is available free with a Web Managers account at https://webmanagers.com/register, and it arrives with the weekly Web Managers letter.