Keep the glossary simple
The glossary defines words. Tools such as Quick Help, Wording Checker, Situation Guide, and Print Cards stay on separate pages.
Public language quality rules
Review Standards
This page explains how ANCHOR glossary and language entries should be reviewed before public use.
Purpose: keep definitions clear, respectful, non-diagnostic, public-facing, Spanish-ready, and useful for real support.
Write for the person using the service
Start with plain meaning. Add professional meaning only after the everyday explanation is clear.
Separate behavior from interpretation
Describe what happened before guessing intent. Use access, sensory, communication, trauma, health, and system-barrier checks.
Name what helps and what harms
Each major term should give practical support actions and warn against common escalation patterns.
Respect individual language preference
Use autistic person, person with autism, disabled person, or person with a disability according to individual preference and context.
Avoid public developer language
Do not publish build notes, internal version notes, placeholder explanations, or language that talks to the creator instead of the public.
Keep Spanish access human-reviewed
Spanish entries should use plain explanations, not only direct word-for-word translation. Interpreter notes should be added where a term is culturally or clinically difficult.
Do not turn language into diagnosis
Definitions can explain concepts and support needs, but they do not diagnose, determine eligibility, or replace legal or medical advice.
Community reviewed
Useful for lived-experience accuracy, clarity, and harm reduction.
Professional reviewed
Useful for education, healthcare, legal, policy, and agency language.
Spanish reviewed
Useful for bilingual access, interpreter wording, and family-facing materials.