Here’s a complete, practical outline (with key takeaways and actionable advice) you can use as the backbone for the book Content For Everyone: A Practical Guide for Creative Entrepreneurs to Produce Accessible and Usable Web Content. It’s written specifically for designers, writers, photographers, illustrators, makers, and other creative business owners who may not have a technical background but want their websites to work for every visitor—including people with disabilities.Suggested Book Structure & Core ContentIntroduction – Why Accessibility Isn’t Optional Anymore
- The moral case (inclusion) + the business case (15–20 % of the population has some form of disability; Google rewards accessible sites; legal risk under ADA/Section 508/WCAG conformance)
- “Accessibility is good design that got left out of art school”
- Quick win: One small change (proper heading structure) can improve both accessibility AND SEO at the same time
- Empathy is your superpower as a creative
- Accessibility is creativity with constraints (just like designing for mobile or brand guidelines)
- Reframe “I’m not a developer” → “I’m the one who decides what goes out into the world”
- Why 4.5:1 contrast ratio isn’t “killing your aesthetic”
- Tools: Stark plugin (Figma/Sketch/Adobe XD), Contrast (macOS), WebAIM Contrast Checker
- Real portfolio fixes: before/after examples of moody photography sites that still pass AA
- Bonus: High-contrast versions don’t have to be ugly—think Duotone or dark-mode elegance
- Minimum body text: 16 px (or 1 rem)
- Line height 1.5+, letter-spacing slightly increased for dyslexic readers
- Left-aligned text for Latin languages
- Free accessible-friendly font pairs (Inter, Libre Franklin, Work Sans, Atkinson Hyperlegible, Lexend)
- Decorative vs meaningful images
- The one-sentence rule for alt text
- How to describe your own artwork accessibly without sounding robotic
- SVG accessibility tricks (title, aria-label, role="img")
- Image carousels/sliders are accessibility nightmares—here are better alternatives
- Plain language (Hemingway app, Flesch-Kincaid < grade 8)
- Heading hierarchy (never skip levels just because it looks wrong in your design)
- Link text: “Click here” is evil; use descriptive links
- Writing good focus indicators for keyboard users
- Logical heading order = automatic SEO + screen-reader win
- Skip-to-content links (and how to style them beautifully)
- Mobile hamburger menus done right (focusable, clear labels)
- Labels explicitly associated (not just placeholder text)
- Clear error messages and success states
- reCAPTCHA alternatives (Friendly Captcha, hCaptcha)
- Captions + transcripts (creative caption styling ideas)
- Audio description for cinematic brand films
- How to keep your beautiful scroll animations from causing vestibular issues (prefers-reduced-motion)
- Quick scorecard for Squarespace, Shopify, Showit, WordPress, Webflow, Framer, Carrd, etc.
- Best themes/plugins (2025 edition)
- When to fire your current platform
- Free/quick tests you can do in 10 minutes:
- Tab through your site with keyboard only
- Turn images off
- Use VoiceOver (Mac) / TalkBack (Android) / NVDA (Windows)
- WAVE, axe DevTools browser extension
- Hire real testers: platforms like Fable, AccessWorks, or even Be My Eyes volunteers
- Current state of ADA web lawsuits (2025)
- Having a basic accessibility statement reduces risk
- Overlay widgets (accessiBe, UserWay, etc.)—why most experts hate them
- Build accessibility into your quarterly site refresh
- Keep a living access checklist with every new page or product launch
- Alt-text decision tree (flowchart)
- Accessible color palette generator (Figma file)
- Copy-and-paste accessibility statement template
- 7-day accessibility sprint for existing websites
- Warm, encouraging, slightly irreverent (think “your cool friend who actually knows this stuff”)
- Lots of before/after visuals
- Zero shame—focus on “here’s how to fix it in 5 minutes”
- Humor: “Yes, your 12-step illustrated cursor trail is very 1998 Geocities, but it’s also giving screen-reader users a panic attack.”

0 Comments