Stimpunks Foundation

Mutual Aid and Human-Centered Learning for Neurodivergent and Disabled People

Yellow poster titled “Stimpunks Style Guide” with the Stimpunks logo in the top right. Six framed images are arranged in two rows. Top row: the word “Autistic” in colourful letters labelled “Why We Capitalise Autistic,” a person holding a white mask labelled “Identity First Language,” and a laptop and notebook labelled “Scanning & Skimming.” Bottom row: a person standing before a glowing keyhole labelled “Access Needs,” a sign reading “Diversity, Equality, Inclusion” labelled “Intersectionality,” and a chess piece being moved labelled “Framing and Ethics.” At the bottom is the website “www.stimpunks.org.”

Stimpunks.org House Style Guide

🗺️

Home » Field Guide » Editorial » Stimpunks.org House Style Guide

A shared language for making Stimpunks readable, humane, and usable.

We, Stimpunks

This is the writing and design playbook for Stimpunks.org. It exists so that the ideas we share — about access, neurodivergence, disability justice, and lived experience — come through clearly, honestly, and without harm. We don’t write to fit norms that erase people. We write to make room for complexity, nervous systems of all kinds, and real lives.

The guide covers how we use language, structure content, and design experiences that are usable for people with diverse attention patterns, sensory needs, and ways of making meaning. It’s practical, not perfect, and designed to help anyone contribute work that feels like Stimpunks: direct, care-centered, and grounded in real experience.

This isn’t about policing tone.
It’s about making our work readable, accessible, and humane, for readers and for the people who create it.

Table of Contents

This is a concise house style guide for Stimpunks.org. It’s written to be usable by contributors, editors, and collaborators, and to protect the voice from drift, dilution, or institutional smoothing.

Purpose

Stimpunks writing exists to surface hidden labor, challenge harmful systems, and center neurodivergent and disabled lived experience. The goal is clarity, access, and truth—not approval.

Voice & Authority

Write from lived experience

  • Speak as “we” when naming shared realities.
  • Authority comes from being affected, not from credentials.
  • Cite research when useful, but never let it override lived truth.
  • Lived experience is not monolithic; avoid flattening differences.

Center those most impacted

  • Prioritize perspectives of people with intersecting marginalizations.
  • Do not default to the most privileged version of disability or neurodivergence.

Take a position

  • Stimpunks writing is values-forward.
  • Neutrality is not required and is often harmful.
  • Name injustice directly, including ableism, racism, sexism, transphobia, classism, colonialism, and capitalism where relevant.

Unapologetic, not aggressive

  • Be firm and clear without attacking individuals.
  • Critique systems, norms, and structures—not people struggling inside them.

Tone

Plainspoken

  • Prefer simple, direct language.
  • Avoid jargon unless it’s necessary—and explain it when used.

Anti-respectability

  • Do not soften language to sound “professional.”
  • Do not adopt nonprofit, academic, or corporate tones.

Care-centered

  • Write with care for readers’ nervous systems.
  • Avoid shock for its own sake.

Punk in philosophy

  • Challenge power.
  • Reject compliance culture.
  • Prioritize survival, dignity, and access over polish.

Structure & Rhythm

One idea at a time

  • Short paragraphs.
  • One main idea per sentence or line whenever possible.

Scannable by design

  • Use lists, line breaks, and white space.
  • Assume readers may need to pause and return.

Declarative sentences

  • Favor statements over hedging.
  • Avoid unnecessary qualifiers (“just,” “maybe,” “kind of”).

Framing & Content Rules

Center systems, not individuals

  • Frame harm as a design failure, not a personal flaw.
  • Avoid language that blames people for unmet needs.

Human needs, not special needs

  • Never frame access as exceptional, optional, or charitable.
  • Care and access are infrastructure.

Foreground complexity

  • Do not oversimplify lived reality.
  • Reject binary thinking and reductionism.

Intersectionality is foundational

  • Neurodivergence and disability never exist in isolation.
  • Write as if multiple identities and risks are present—because they are.

Center those most impacted

  • Prioritize perspectives of people facing multiple, overlapping forms of marginalization.
  • When examples are used, avoid defaulting to the most privileged version of disability or neurodivergence.

Design from the edges

  • Ask: Who is most excluded by this system?
  • If it doesn’t work for them, it doesn’t work.
  • Edge cases are stress tests, not inconveniences.

Avoid flattening experience

  • Do not treat “the neurodivergent experience” or “the disabled experience” as singular.
  • Frame patterns as patterns, not rules.

Name power explicitly

  • Identify how racism, ableism, sexism, transphobia, colonialism, capitalism, and classism shape access and harm.
  • Avoid language that individualizes or psychologizes structural violence.

Do not trade one group’s access for another’s

  • Avoid framing that pits access needs against each other.
  • Conflicts are design failures, not competing bodies.

Representation is not enough

  • Inclusion without safety is harm.
  • Visibility without power is extraction.
  • Writing should reflect this distinction clearly.

Honor lived knowledge

  • Do not paraphrase or sanitize marginalized voices to sound “cleaner.”
  • Preserve meaning, anger, grief, and complexity.

Avoid savior framing

  • Stimpunks does not “give voice” to marginalized people—we amplify voices that already exist.
  • Write with people, not about them.

Assume uneven risk

  • What is inconvenient for some is dangerous for others.
  • Write with awareness that consequences are not distributed equally.

Access is relational

  • Treat accessibility as ongoing, contextual, and collective.
  • Avoid checklist or compliance framing.

Identity-First Language

Stimpunks uses identity-first language (e.g., Autistic person, not person with autism) as a default. This reflects how many Autistic and disabled people understand themselves: not as people carrying a condition, but as people whose identities, perceptions, and ways of being are inseparable from who they are.

Identity-first language affirms that neurodivergence and disability are not defects to be distanced from or softened with euphemism. They are real, meaningful aspects of identity shaped by both biology and social context. Saying Autistic is not reducing someone—it is naming a reality that deserves respect.

Why This Matters

Person-first language was designed to counter dehumanization, but in practice it often reinforces the idea that disability is something shameful, burdensome, or detachable. Identity-first language resists that framing. It recognizes that harm usually comes not from our neurology or bodies, but from systems that refuse to accommodate them.

Language shapes power. We choose words that center dignity, agency, and self-definition.

Our Practice

  • We default to identity-first language throughout the site.
  • We follow community-preferred terms, especially when writing about lived experience.
  • We respect individual preferences when explicitly stated.
  • We avoid deficit-based, medicalized, or pity-framed language unless critiquing it directly.
  • We explain our choices openly rather than treating them as neutral or apolitical.

When We Name Differences

We name identities plainly and without apology. No scare quotes. No softening. No euphemisms meant to make non-disabled readers more comfortable. Comfort is not the goal—clarity and respect are.

Why We Say Autistic (In Brief)

We use Autistic because autism isn’t something we carry—it’s part of who we are. Identity-first language reflects lived experience and rejects the idea that disability is shameful or detachable. The harm isn’t autism; it’s systems built without us in mind. Naming identity plainly is an act of respect.

Capitalization: Why We Write Autistic

Stimpunks capitalizes Autistic.

We treat Autistic as an identity and culture, not a diagnosis or pathology. Capitalizing the A places Autistic people alongside other named identities and communities, rather than framing autism as a deficit or condition to be managed.

Capitalization is a small but meaningful act of resistance to medicalization and neuronormativity. Language shapes power. Lowercasing often reflects clinical distance; capitalization reflects dignity, agency, and self-determination.

Editorial guidance:

  • Use Autistic (capital A) as the default.
  • Prefer identity-first language (“Autistic person”) unless an individual explicitly requests otherwise.
  • Respect personal preferences when quoting or referring to individuals.
  • Preserve original capitalization when quoting external sources, even if it differs from Stimpunks style.

In short: Capital A for Autistic—because people are not symptoms.

Language to Prefer

  • “Human needs” (not “special needs”)
  • “Access” as a process, not a feature
  • “Bodyminds” when relevant
  • “Care,” “interdependence,” “mutual aid”
  • “Systems,” “structures,” “design failures”
  • “Most impacted” instead of “vulnerable”

Language to Avoid

  • “Normal” as a standard
  • “High-functioning / low-functioning”
  • “Behavior problems”
  • “Fixing” or “curing” people
  • Euphemisms that hide harm
  • Savior language (“giving voice,” “helping the less fortunate”)

We love hyperlinks and use them extensively. We consider them a kindness to the reader and a potent weapon in the fight against disinformation. Many of our links lead to our expansive glossary.

Semantic links rather than commercial advertisements are the life blood of the internet – the Autistic online habitat.

Jorn Bettin, author of “The Beauty of Collaboration at Human Scale: Timeless patterns of human limitations“

Block Quotes

We use block quotations (blockquote) heavily. We quote our favorite passages and sources with hyperlinks signposting back to the original work.

A block quotation (also known as a long quotation or extract) is a quotation in a written document that is set off from the main text as a paragraph, or block of text, and typically distinguished visually using indentation and a different typeface or smaller size font. This is in contrast to setting it off with quotation marks in a run-in quote. Block quotations are used for long quotations.

Block quotation – Wikipedia

Sections, Hierarchy, Semantics, and Tables of Contents

We provide content hierarchy, visual hierarchy, and tables of contents to improve skimmability and wayfinding.

Readers on the web scan for information, rather than reading everything line-by-line. Chunking your content into smaller sections, called out by larger headings, helps them find the information they’re searching for.

When I’m trying to find something quickly, there’s nothing more intimidating than jumping onto a site with a giant wall of unbroken content. 

Show, Don’t Tell | CSS-Tricks – CSS-Tricks

People want to know where they’re at in the story. This doesn’t have to be fancy, you don’t need a full timeline bar like a YouTube video. But a quick outline of progress (and, if you’ve got a particularly long document, recapping your position in that outline as you go) can help ensure people that they understand their place in the overall conversation.

Make better documents. – Anil Dash

Headings are semantic and hierarchical and should be used semantically, not just for styling.

Semantic HTML is the use of HTML markup to reinforce the semantics, or meaning, of the information in web pages and web applications rather than merely to define its presentation or look.

Semantic HTML – Wikipedia

We encounter documents all the time with incoherent heading hierarchy because folks used them according to their displayed size instead of their meaning.

Hierarchical headings are important to accessibility.

A common navigation technique for users of screen reading software is to quickly jump from heading to heading in order to determine the content of the page. Because of this, it is important to not skip one or more heading levels. Doing so may create confusion, as the person navigating this way may be left wondering where the missing heading is.

The HTML Section Heading elements – HTML: HyperText Markup Language | MDN

Most screen readers can also generate an ordered list of all the headings on a page, which can help a person quickly determine the hierarchy of the content:

The HTML Section Heading elements – HTML: HyperText Markup Language | MDN

One of the best things we can do for accessibility is use headings, actual html 1-6 headings, not just text that’s been bolded and made bigger. It needs to be marked as a heading.

Accessible Typography

Typography isn’t decoration — it’s a core accessibility practice. How text looks, how it’s spaced, how clearly letters are formed, and how large it appears all affect whether people can read, understand, and stay present with what you write. When typography is inaccessible, it creates real visual and cognitive barriers that make content harder to parse, harder to focus on, and harder to complete — especially for people with low vision, dyslexia, cognitive differences, or sensory processing needs.

There is no one “magic font” that works for everyone, and designers often disagree about what’s best. But there are real design choices that reduce barriers for most readers: typefaces with clear, distinguishable characters, generous spacing, left-aligned text, sufficient size and line height, and high contrast between text and background. These choices benefit everyone — not just people with specific access needs — and are part of our commitment to inclusive, humane publishing.

Above all, the accessible typography principle at Stimpunks is this: make text that people can see, stay with, and understand without unnecessary strain. That means listening first to disabled people’s experiences, testing with real users, and making thoughtful choices about type, sizing, spacing, and contrast — not following aesthetic trends that privilege style over legibility.

Font

This article surveyed dyslexic people for their preferences and they found a list of things to look for in an accessible typeface:

  • Is there a difference between capital I, lowercase l, and the number 1?
  • Compare letters b and d, p and q — are they mirror images or distinguished?
  • Compare letters g, a, and o — are they distinguished?
  • Do the letters rn look like the letter m?
The controversy of accessible type | by Alex Chen | Queer Design Club | Medium

Font Size

Use large font sizes instead of tiny text. It’s best practice for body text to be at least 16px for web. I personally prefer 18–20px.

People should also be able to zoom in up to 200% without losing information or structure.

The controversy of accessible type | by Alex Chen | Queer Design Club | Medium

Weights and Styles

Use different weights and styles sparingly to make text simple and clean.

  • Use sentence case, not all caps
  • Don’t combine bold and italics
  • Don’t create blocks of text with italics
The controversy of accessible type | by Alex Chen | Queer Design Club | Medium

Spacing

Use accessible spacing to differentiate lines of text and make reading easier. Best practices are:

  • 1.5x font size for line spacing
  • 2x font size for paragraph spacing
The controversy of accessible type | by Alex Chen | Queer Design Club | Medium

Contrast

Use high contrast to make text stand out. The text on the left is easy to read because:

  • It uses regular instead of light weight
  • It’s at 100% instead of 30% opacity
  • It’s at 21:1 contrast (aim for at least 7:1)
The controversy of accessible type | by Alex Chen | Queer Design Club | Medium

Accessibility Commitments

  • Write for multiple reading speeds and cognitive styles.
  • Avoid dense blocks of text.
  • Explain concepts without condescension.
  • Respect sensory and emotional load.

Form Accessibility

Forms are not neutral. They can invite participation — or quietly exclude. At Stimpunks, all forms must be designed to minimize friction, respect neurodivergent and disabled realities, and serve people rather than screen them out.

This checklist defines the minimum standard for any form used by Stimpunks (intake, applications, surveys, internal ops, fundraising, or research).

Purpose & Transparency

  • Every form must begin with a plain-language purpose statement.

Forms must explain:

  • how information will be used
  • who will have access
  • what happens after submission
  • Required fields must be clearly labeled; optional is the default.

Cognitive Load

  • Forms must be as short as possible.
  • Questions must be grouped into clearly labeled sections (use headings or lily pads).
  • Avoid compound, trick, or multi-part questions.
  • Remove “nice-to-have” data.

Language & Framing

  • Use plain, direct language.
  • Avoid institutional, legalistic, or deficit-framed wording.
  • Do not assume capacity, resources, time, or executive function.
  • Do not require performative professionalism.

Response Flexibility

When feasible, offer multiple ways to respond:

  • text
  • file upload
  • audio or video
  • follow-up conversation
  • Avoid long narrative requirements.
  • Do not impose minimum word counts unless essential.

Visual & Sensory Design

  • High contrast text and backgrounds are required.
  • No flashing elements, animations, or time limits.
  • Long forms must be broken into sections or pages.
  • Field labels must be visible (do not rely on placeholders).

Neurodiversity & Disability Inclusion

  • No timers, countdowns, or urgency cues.
  • Allow saving progress and returning later when possible.
  • Accept varied answer styles and levels of detail.
  • Design for fluctuating energy, memory, and attention.

Technical Accessibility

All forms must be:

  • keyboard navigable
  • screen-reader friendly
  • mobile usable without loss of function
  • Avoid CAPTCHAs that block disabled users; provide alternatives if unavoidable.

Error Handling

  • Error messages must explain what went wrong and how to fix it.
  • Entered data must not be erased on error.
  • Errors should be phrased neutrally and respectfully.

Power & Safety

  • Collect only information that is truly necessary.
  • Do not require disclosure of diagnosis, trauma, or identity unless essential.
  • When forms relate to selection, funding, or review, name the system of power involved.
  • Provide a contact for questions, corrections, or accommodations.

What We Are Not

  • Not neutral
  • Not polite to harmful systems
  • Not assimilationist
  • Not charity-focused
  • Not productivity-obsessed

Intersectionality Final Check

Before publishing, ask:

  • Who is centered here—and who is missing?
  • Whose risk is acknowledged, and whose is ignored?
  • Does this treat complexity as real, or as an inconvenience?
  • Does this reinforce power, or challenge it?

If it flattens, revise.
If it erases, stop.

Final Check

Before publishing, ask:

  • Does this center lived experience?
  • Does it name systems, not blame individuals?
  • Does it protect access and dignity?
  • Does it sound like Stimpunks—or like an institution?

If the answer isn’t yes, revise.

Companion Guides

These companion guides live as subpages of the House Style Guide. Each stands on its own and can be linked directly.

How the Style Guide Serves Accessibility

The Style Guide is more than a set of writing rules — it’s a tool for inclusion. It ensures that the language, layout, tone, and presentation of Stimpunks content are usable by people with a range of sensory, cognitive, attentional, and physical needs. Accessibility isn’t an add-on; it’s baked into how we communicate.

1. Language That Meets Real Brains

The Guide promotes:

  • Plain language over jargon
  • Short sentences and clear structure
  • Explanations of terms where they appear
    These choices reduce cognitive load and help readers who process information non-linearly, have language differences, or struggle with dense text.

2. Visual Structure That Supports Reading

The guide encourages:

  • Lily pads (colored blocks/groups)
    These act as visual anchors, letting readers pause, regroup, and navigate at their own pace.
  • Headings and signposts
    So readers can orient themselves without reading every word.
  • Whitespace and breaks
    Reducing visual clutter and providing space for processing.

These elements help readers with ADHD, dyslexia, visual processing differences, and sensory sensitivities by making meaning easier to find and sustain.

3. Rhythms and Pacing That Respect Attention

The guide steers contributors to use:

  • Scrollytelling patterns
    Which pace information with intent.
  • Lists, bullets, and modular chunks
    So attention can land, rest, and move again without overload.

This makes reading less exhausting and helps people engaging in bursts or fragmented sessions.

4. Inclusive Tone and Permission

The Guide asks writers to:

  • Explicitly permit skimming, stopping, and skipping
  • Avoid shaming language
  • Respect that readers arrive with different capacities and contexts

This supports emotional accessibility as much as cognitive — no one is made wrong for engaging differently.

5. Punctuation and Visual Cues

By standardizing things like:

  • Em-dash usage for meaningful pauses
  • Oxford commas for clarity
  • Accessible typography choices (clear letterforms, contrast, spacing)

the Guide ensures that text structure itself doesn’t become a barrier. These conventions aid comprehension for screen readers, scanning readers, and people with sensory needs.

6. Multiple Expression Paths

The Guide encourages:

  • Alternative response formats (audio, visual, text)
  • Expandable sections (“In other words…”, “Go deeper…”)
  • Recognition of different reading patterns
    This supports people who read non-linearly, use assistive tech, or have fluctuating capacity.

7. Continuous Reflection

The Style Guide isn’t a fixed rulebook. It’s written to:

  • evolve with lived experience
  • be transparent about why choices are made
  • invite feedback and adaptation

This embodies accessibility as an ongoing practice, not a checklist.

In Sum

The Style Guide serves accessibility by shaping how meaning is offered, structured, and experienced. It doesn’t ask people to adapt to the content. Instead, it designs content to adapt to people — especially those whose brains and bodies have been left out of dominant design norms.

Accessibility at Stimpunks isn’t about compliance.
It’s about respect, care, and real usability.

Further Reading