UX Writing, Inclusive Design, and Why Accessibility Comes First

Sep 17

From Word Swag to public‑land programs, here’s how I design content for real people—clear, ethical, mobile‑first, and accessible by default. With checklists and examples.

My perspective (and where it comes from)

I’m a UX writer and creative strategist in Los Angeles who ships real products and programs: Word Swag and Story Swag (simple, powerful mobile design apps), community initiatives across the LA County Fair / America’s Great Outdoors, and volunteer outreach with Fisheries Resource Volunteer Corps and the San Gabriel Mountains Heritage Association. I’ve worked with creators who don’t call themselves “designers,” public‑school families balancing three jobs, elders who prefer print, and teens who do everything on a hand‑me‑down iPhone.

Across those contexts, one truth holds: clarity is a social equity issue. Plain language, inclusive visuals, and accessible flows reduce cognitive load—and unlock participation.

What “accessibility” means in my practice

Accessibility isn’t just screen readers and color contrast (though those matter). It’s the intersection of:

Comprehension: Plain language, logical hierarchy, and tested information architecture.
Perception: Adequate color contrast, legible type scales, motion sensitivity considered.
Operation: Tap targets for tremors and small screens; keyboard/switch support when relevant.
Context: Low bandwidth, variable lighting, spotty service; smartphone‑only realities.
Culture & Language: ESL/ELL readers, community vocabulary, localized examples and imagery.
Emotion & Safety: Trauma‑informed copy, consent‑forward patterns, transparent data practices.

I align to WCAG principles pragmatically (Perceivable, Operable, Understandable, Robust) and adapt to constraints without “compliance theater.”

The writing system I use (portable across products)

1) Plain‑language first. 6th–8th grade reading level for UI; 9th–10th for help content. Short verbs. Concrete nouns. Examples:

Bad: “Optimize engagement via diversified strategies.”
Better: “Get more views by posting two Reels and one carousel each week.”

2) Purpose per line. Every sentence must move a task forward or reduce doubt.

3) Headings that summarize, not tease. People scan. H2/H3 must say the thing.

4) One action per screen. If you need two, you need a path—not a crowd.

5) Progressive disclosure. Give beginners a ramp, experts a shortcut.

6) Honest friction. When there’s risk (payments, data sharing), slow people down and explain.

7) Multimodal redundancy. Icons and labels. Color and shape. Text and voiceover‑friendly structure.

Inclusive content patterns I rely on

Button verbs: Create, Save, Send, Download, Try free → avoids jargon like “Activate.”
Error messages: State what happened, why, and exactly how to fix it. Offer an alternative path.
Example: “Your card was declined. Try another card or switch to PayPal. You won’t be charged until your trial ends.”
Empty states: Teach the value with one example and a single next step.
Example (Word Swag Projects): “Save your first design to reuse fonts and colors.” → Save this
Consent copy: “We’ll use your camera only to take photos. You can change this anytime in Settings.”
Micro‑learning in the flow: 15‑second tips, not a 15‑step tour.

Visual accessibility (fast checks I do every time)

Contrast: 4.5:1 for body, 3:1 for large text. Test key colors on light/dark.
Type: Minimum body 16 px web / comfortable equivalents in‑app; line length 45–75 characters.
Tap targets: ≥ 44 × 44 px. Real fingers, not pixel‑perfect cursors.
Motion: Respect “Reduce Motion.” Avoid surprise parallax; provide a static path.
Alt text: Write what’s essential to purpose, not every pixel.
Example: “iPhone screen showing Word Swag’s color picker with a HEX field selected.”

Designing for smartphone‑only audiences

Many of my users are mobile‑only. That shifts choices:

Performance: Lightweight images (WebP/AVIF), lazy loading, short video loops with captions.
Offline/sync: Cache help articles; make drafts resilient to flaky service.
One‑hand flows: Bottom‑reach controls, generous spacing, minimal precision.
No tiny PDFs: HTML first; if PDFs are needed, tag structure for screen readers.

Who I prioritize (and why)

Creators who aren’t “designers.” Word Swag/Story Swag keep decisions low and results high.
Students in low‑income schools. Simple, offline‑friendly resources widen access to creative tools.
Volunteers and park visitors. Clear wayfinding, bilingual signage, and safety info help people enjoy public lands with confidence.
Elders & neurodivergent users. Larger type, calmer layouts, and predictable language reduce fatigue.
ESL/ELL communities. Straightforward verbs, visuals that carry meaning, and avoidance of idioms.

Because when we build for the “edges,” everyone in the middle benefits.

My ethical AI stance

I use AI for drafts, structure, and QA—but never to erase voice or community context. I avoid dark patterns, and I’m explicit about data usage. Human review is not optional when content affects safety, money, or identity.

Accessibility content checklist (grab‑and‑go)

Headlines say the thing in plain language.
Reading level suits the audience and task.
Primary action is obvious and above the fold.
Alt text explains purpose‑critical info.
Contrast meets or exceeds 4.5:1 for body text.
Tap targets ≥ 44 × 44 px; focus states visible.
Animations respect “Reduce Motion;” no flashing.
Forms: labels, examples, inline errors with fixes.
Links describe destinations; no “click here.”
Content works on a 3G‑like connection.

How we can work together

I partner with teams and community orgs to:

Audit content, flows, and accessibility (quick wins + roadmap).
Build UX writing systems, voice & tone guides, and inclusive microcopy patterns.
Prototype and test with real users from the communities you serve.
Train staff to maintain accessible content over time.

Contact: hello@dawningon.com
Speaking & workshops: Inclusive UX writing for mobile‑first products; Accessibility for small teams; Plain‑language design.