Accessibility and Inclusion

Accessibility is not a decorative compliance layer. It is part of the Archive’s truthfulness. If the institution only records people who can tolerate long forms, loud rooms, small text, fast speech, inaccessible video, English-only materials, or high-bandwidth tools, the Archive will misrepresent the age it is trying to preserve.

The Rule

Access is designed before invitation, not repaired after exclusion.

Every public Spiralist activity should ask four questions before it is announced:

1. Can a disabled person participate without asking for special permission?
2. Can a neurodivergent person understand the structure before arriving?
3. Can a low-bandwidth or low-income participant access the core material?
4. Can a person who does not use fluent institutional English still find the basic promise, risk, and consent terms?

If the answer is no, the institution has not finished designing the activity.

Access Commitments

Spiralism should make these commitments public:

• The public website follows WCAG 2.2 AA as the working baseline.
• Public videos include captions.
• Public audio receives transcripts.
• Long documents receive summaries, tables of contents, and stable headings.
• Testimony intake is available in more than one format.
• Chapter gatherings publish access information before attendance is requested.
• Accessibility requests are treated as ordinary operations, not favors.
• No participant is required to disclose a diagnosis in order to request access.
• AI-generated accessibility support is reviewed by humans before publication.

WCAG 2.2 frames accessibility across visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. Spiralism should use that breadth as a design minimum, while remembering that standards do not replace lived testing.

Website Baseline

The public site should meet these operational rules:

• semantic HTML before custom interaction;
• visible keyboard focus;
• keyboard access to all interactive controls;
• meaningful link text;
• lang declared on every page;
• sufficient color contrast;
• no text baked into images when HTML text would work;
• alt text for informative images;
• empty alt text for decorative images;
• headings in logical order;
• tables only for data;

• responsive layouts that do not require horizontal scrolling for ordinary reading;

• no auto-playing sound;

• reduced-motion support if animation is added;
• forms with explicit labels, clear errors, and no mouse-only controls.

The site is currently static and text-first, which is a strength. The danger is not technical complexity but institutional drift: adding cinematic effects, newsletter widgets, embedded media, or donation flows without checking whether they can be used by keyboard, screen reader, magnification, voice control, and low-bandwidth users.

Plain Language Layer

Spiralism needs poetic language, but access requires a second layer of plain language.

Every major doctrine or protocol should have:

• a one-paragraph summary;
• a short “what this asks of you” section;
• a short “what this does not ask of you” section;
• definitions for inside terms;
• explicit money, consent, privacy, and authority language;
• a contact path for clarification.

Plain language does not mean flattening the institution’s aesthetic. It means never using mystery to hide obligations.

Cognitive Accessibility

The AI transition will bring anxious, overloaded, grieving, curious, skeptical, and exhausted people into contact with the institution. Cognitive access is therefore central.

Use these defaults:

• predictable page structures;
• short paragraphs;
• stable navigation;
• clear next steps;
• summaries before long arguments;
• no pressure countdowns;
• no manipulative scarcity;
• no surprise public sharing;
• no required rapid decisions after emotionally intense testimony;
• quiet rooms or pause options at in-person gatherings;
• breaks in long workshops;
• written agendas before meetings;
• post-meeting notes after meetings.

WebAIM’s cognitive accessibility guidance emphasizes clear language, relevant content, understandable instructions, readable text, descriptive labels, and summaries for complex material. Spiralism should treat these as spiritual discipline: a community that cannot be understood by tired people is not yet humane.

Testimony Intake Access

The testimony protocol should support multiple intake paths:

• recorded audio;
• recorded video;
• written testimony;
• interview with an Archivist;
• asynchronous question packet;
• supported testimony with a trusted companion present;
• short-form testimony for people who cannot complete the full protocol.

No one should be told that their testimony is less real because it arrives in a different format. The Archive can distinguish media quality, consent status, and metadata completeness without ranking human worth.

Testimony forms should:

• use plain labels;
• separate required and optional fields;
• avoid large unbroken text blocks;
• allow saving or pausing where practical;
• explain publication options before collection;
• explain withdrawal and revision limits;
• avoid diagnosis requests unless legally or ethically necessary;
• provide an accessibility contact.

Captions, Transcripts, and Descriptions

Public media should use this ladder:

1. Captions for public video.
2. Transcript for public audio and video.
3. Speaker identification where useful.
4. Description of important non-speech sounds.
5. Visual description for visuals that carry meaning.
6. Plain-text source notes for research-heavy pieces.

Captions generated by AI can be a draft, not the finished record. Names, technical terms, quoted language, and emotionally important phrases must be reviewed by a human before publication. A bad transcript can misrepresent the speaker as surely as a bad edit.

Gatherings and Chapters

Every public chapter listing should include:

• physical access notes for the venue;
• transit and parking notes where known;
• whether masks are expected, optional, or unavailable;
• food and allergen information if food is served;
• whether there will be amplified sound;
• whether there will be captions or notes for virtual participation;
• expected meeting length;
• agenda shape;
• contact path for access requests;
• whether the event is recorded;
• whether testimony will be solicited.

Accessible events are not only about ramps. They are about predictability, sensory load, participation modes, remote access, and the ability to leave without social penalty.

For hybrid gatherings:

• test audio before the meeting;
• use microphones for all speakers;
• repeat audience questions before answering;
• make slides available before or after the event;
• designate a remote host if remote participation is offered;
• do not treat remote participants as passive viewers unless the event is explicitly a broadcast.

Language and Translation

English can be the founding language without becoming a spiritual gate.

The first language-access layer should include:

• plain-English summaries for all major pages;
• translated summaries before full translated manuals;

• glossary support for terms such as Spiral, Mirror, Archive, Testimony, Patron, Chapter, and Signal Convergence;

• clear labeling of machine translation;

• human review for consent language, safety language, and donation language;
• refusal to use translation to imply legal status that does not exist.

Machine translation may help people approach the work. It should not be the only version of legally or emotionally consequential text.

Economic Access

Participation must not quietly become pay-to-belong.

Default rules:

• core doctrine remains free to read;
• testimony submission is not paywalled;
• chapter attendance should have a free path;
• paid retreats or intensives require scholarship planning;
• volunteer labor cannot be treated as proof of devotion;
• patron recognition cannot become social rank inside chapters;
• access needs are budget items, not optional extras.

The development budget should include captions, transcripts, venue access, childcare experiments where appropriate, transport support, translation review, and accessibility audits.

Neurodivergence and Spiritual Intensity

Spiralism uses mythic, symbolic, and future-religious language. That language can help people name reality, but it can also intensify pattern-seeking, grandiosity, paranoia, or dependency in some contexts.

Chapter hosts should therefore:

• state that Signal Convergence is a prompt to document and test, not a command;
• avoid telling people what their experiences “really mean”;
• keep ritual optional;
• preserve ordinary language beside symbolic language;
• avoid sleep deprivation, fasting pressure, isolation, or confession pressure;
• refer distress to qualified support when needed;
• document concerns through the incident protocol rather than improvising spiritual authority.

Accessibility includes the right not to be swept into the room’s intensity.

Access Review

Each quarter, the institution should review:

• pages missing summaries;
• videos missing captions or transcripts;
• events held in inaccessible venues;
• forms with abandonment problems;
• unresolved access requests;
• chapters without access notes;
• donation pages or intake flows with inaccessible controls;
• complaints involving disability, language access, or sensory exclusion.

The annual report should include access metrics without turning disabled people into proof of virtue.

Public Access Promise

Use this plain public language:

Accessibility:
Spiralism is building an archive and community for people living through the AI
transition. We want disabled, neurodivergent, low-bandwidth, and language-diverse
participants to be able to take part without unnecessary friction. Public videos
should have captions, public audio should have transcripts, gatherings should
publish access notes, and major documents should include plain summaries. If an
access barrier prevents participation, tell us and we will treat it as an
operations issue, not a special favor.

Anti-Patterns

Avoid:

• “Contact us for accommodations” as the only access plan;
• tiny gray text for legal, consent, or donation language;
• image-only flyers;
• auto-playing background audio;
• livestreams with unusable room audio;
• captions posted weeks after publication;
• machine translation without labeling;
• asking for diagnoses instead of access needs;
• treating accessibility as a compliance chore;
• using mystery, ritual, or urgency to bypass comprehension.

Sources Checked

• W3C, Web Content Accessibility Guidelines 2.2, accessed May 2026.
• W3C WAI, Accessibility Principles, accessed May 2026.
• WebAIM, Evaluating Cognitive Web Accessibility, accessed May 2026.
• WebAIM, Creating Accessible Forms, accessed May 2026.
• WebAIM, Writing Clearly and Simply, accessed May 2026.
• Mass.gov, Tips for hosting accessible events and meetings, accessed May 2026.
• MDN Web Docs, Cognitive accessibility, accessed May 2026.