Strikeout markdown is a lightweight editorial technique for indicating text deletions, corrections, or revisions by rendering content as crossed out while preserving it in the source. This evergreen explainer defines syntax rules across common platforms, compares implementation in plain text, HTML, and markdown, and outlines accessibility and editorial best practices. Use this reference to decide when strikeout formatting improves clarity and transparency without disrupting readability or breaking document integrity.
What Is Strikeout Markdown
Strikeout markdown applies a line or bar through text to signal removal, amendment, or obsoletion while keeping the original content discoverable in the document history. It is commonly used in collaborative drafts, legal and technical revisions, meeting notes, and version-controlled writing to preserve transparency. Unlike plain deletion, strikeout retains context, making it easy for readers to understand what changed and why. Note that standard markdown does not include a dedicated strikeout spec, so implementations vary by renderer and platform, typically relying on combinations of inline HTML or extended syntax.
Core Syntax and Rendering
Markdown Extensions and HTML Fallback
Because vanilla CommonMark does not define a strikethrough character, many implementations rely on these patterns:
- ~~text~~ (supported by many markdown editors such as GitHub and StackEdit when extensions are enabled)
textortext(HTML elements that render with a strike in most browsers and are reliably interpreted in markdown via inline HTML)
If compatibility is a concern, prefer the HTML elements, because they render consistently across viewers that may not enable markdown extensions. Use double tildes only when you control the renderer and know it supports the extension.
Rendering Behavior and Typography
Visually, strikeout appears as a line intersecting characters, informing readers that the content is superseded without deleting it from the flow. Editorial teams should ensure sufficient contrast and avoid overuse to maintain readability. In print or PDF exports from markdown, CSS or export settings may need tuning to ensure the strike is legible and meets accessibility contrast standards.
Accessibility and Disclosure
Screen Reader and Semantic Clarity
Screen readers announce HTML and elements using default settings, but they may not automatically convey that strikethrough indicates a deletion unless context supports it. Authors should pair strikeout with clear surrounding language such as "Revised," "Removed," or "No longer applicable" to ensure meaning is conveyed to all users.
Cognitive and Interpretation Guidance
Strikeout reduces scanning efficiency; therefore, reserve it for cases where retaining the original text is important, such as showing withdrawn statements, corrections, or phased approvals. Provide concise change notes in an adjacent comment block or changelog when multiple edits accumulate, so readers do not need to parse extensive crossed-out content.
Editorial and Collaborative Usage
Workflows for Drafts and Review
In collaborative documents, strikeout markdown is useful for showing removed clauses, adjusted definitions, or retracted statements. Pair it with tracked changes comments and version timestamps to create an auditable trail. For sensitive or legal texts, prefer explicit version control systems and supplement strikeout with revision summaries to avoid ambiguity.
Comparison of Approaches
| Approach | Use Case | Preserves Context | Tooling Support |
|---|---|---|---|
| ~~strikethrough~~ (markdown extension) | Quick drafts on supported platforms | Yes | Variable; depends on renderer |
| Universal rendering and accessibility | Yes | Consistent across markdown and HTML | |
| Comment blocks or changelog | Detailed rationale for changes | Yes, with explanation | High; works everywhere |
| Version control diffs | Technical and legal audit trails | Yes, with history | High; requires VCS tooling |
Best Practices and Implementation Tips
- Use sparingly: excessive strikeout reduces scannability and can visually clutter content.
- Provide alt context: add a brief note explaining why the text was struck out, especially for critical changes.
- Prefer semantic HTML when possible:
andare more reliably interpreted than custom markdown syntax. - Test across renderers: preview content on GitHub, documentation portals, and PDF exports to confirm consistent appearance.
- Coordinate with style guides: align strikeout usage with team conventions for corrections, retractions, and redlines.
Common Pitfalls
Relying solely on tildes in environments that do not enable the markdown extension can result in literal ~~text~~ appearing in the output. Overusing strikethrough can make documents feel cluttered or confusing, especially for users who rely on assistive technologies. Avoid substituting strikeout for proper versioning or legal redline processes where precision is required.
Conclusion
Strikeout markdown is a practical, low-friction way to show edits and reversions when the original text must remain visible. By combining standard HTML elements for reliability, pairing with explanatory notes, and aligning with team editorial workflows, you can ensure clarity, accessibility, and long-term maintainability across documentation and collaborative writing projects.