HTML Entity for Black Circle with Two White Dots (⚉)
What You'll Learn
How to display Black Circle with Two White Dots (⚉) in HTML and CSS. This character is U+2689 in the Miscellaneous Symbols block (U+2600–U+26FF), added in Unicode 3.2, in the Go markers subrange (U+2686–U+2689). It shows a black circle with two white dots, used in Go to mark board positions.
There is no named HTML entity for U+2689. Use ⚉ or ⚉ in markup, or \2689 in stylesheet content. The symbol also suits UI bullets, dual-state indicators, diagrams, and paired emphasis markers. Pair decorative glyphs with visible text or aria-label when the symbol conveys state.
⚡ Quick Reference — Black Circle Two Dots
U+2689Miscellaneous Symbols
⚉Hexadecimal reference
⚉Decimal reference
—None (use numeric refs)
Name Value
──────────── ──────────
Unicode U+2689
Hex code ⚉
HTML code ⚉
Named entity —
CSS code \2689Complete HTML Example
This example shows U+2689 using hexadecimal and decimal character references, plus a CSS content escape on a pseudo-element:
<!DOCTYPE html>
<html>
<head>
<style>
#point:after{
content: "\2689";
}
</style>
</head>
<body>
<p>Black Circle with Two White Dots using Hexa Decimal: ⚉</p>
<p>Black Circle with Two White Dots using HTML Code: ⚉</p>
<p id="point">Black Circle with Two White Dots using CSS Entity: </p>
</body>
</html>🌐 Browser Support
U+2689 is widely supported; piece artwork varies by typeface:
👀 Live Preview
See the glyph at different sizes and beside related circle-dot symbols (font-dependent):
🧠 How It Works
Hexadecimal Code
⚉ references code point U+2689 using hex digits 2689 after the #x prefix.
Decimal HTML Code
⚉ is the decimal equivalent (9865) for the same Black Circle with Two White Dots character.
CSS Entity
\2689 is the CSS escape for U+2689, used in the content property of ::before or ::after.
Same visual result
Hex, decimal, and CSS escapes all produce ⚉. There is no named HTML entity for U+2689.
Use Cases
The Black Circle with Two White Dots (⚉) is commonly used for:
Mark board positions in Go diagrams and analysis (Go markers subblock).
Custom bullets, dual-state indicators, and paired emphasis in interfaces.
Step indicators, paired elements, and visual markers in flowcharts.
Checklists, progress steps, and status markers with dual emphasis.
Feature callouts, ratings, and paired-item indicators.
Printable guides and handouts from HTML without image assets.
Pair ⚉ with text or ARIA (e.g. “Current step”) when it conveys state.
💡 Best Practices
Do
- Use hex or decimal consistently—there is no named entity for U+2689
- Use hex or decimal consistently—there is no named entity for U+2689
- Pair ⚉ with clear text when it marks a step or status
- Scale with
font-sizeso the glyph fits your layout - Use
\2689only inside CSScontent, not inside HTML text nodes - Add
aria-labelortitle(e.g. “Selected”) for screen readers
Don’t
- Confuse U+2689 with sibling circle-dot code points U+2686–U+2689
- Rely on ⚉ alone to communicate meaning in critical UI
- Assume every font renders Miscellaneous Symbols crisply at small sizes
- Ship stateful UI using only dingbats without accessible fallbacks
- Mix CSS escapes into HTML text nodes (use numeric refs in markup)
Key Takeaways
Two numeric references render the same glyph
⚉ ⚉CSS content escape
\2689U+2689 has two white dots; U+2688 is dot-on-right in the same series
Go markers U+2686–U+2689 sit in Miscellaneous Symbols (U+2600–U+26FF)
Pair glyphs with text or ARIA when the symbol conveys interactive state
❓ Frequently Asked Questions
⚉ (hex), ⚉ (decimal), or \2689 in CSS content. There is no named entity; all valid methods render ⚉.U+2689 (hex 2689, decimal 9865). Miscellaneous Symbols, Go markers subblock. Unicode name BLACK CIRCLE WITH TWO WHITE DOTS.\2689 escape belongs in stylesheets (for example on pseudo-elements). Do not paste CSS escapes into HTML text nodes.⚉, ⚉, or \2689 in CSS depending on whether you are authoring markup or styles.Explore More HTML Entities!
Discover 1500+ HTML character references — currency symbols, arrows, math operators, emojis, and more.
About the author
8 people found this page helpful