CJK Compatibility Forms

• Provide robust font fallbacks that include CJK Compatibility Forms glyphs to avoid missing characters.
• Use explicit font-family stacks and test rendering across Windows, macOS, Android, and iOS.
• Normalize user input to prevent unexpected mappings or duplicates caused by legacy code points.
• Avoid hard-coding UI semantics around these code points; prefer clear text or images when possible.
• Document compatibility limitations and accessibility considerations for screen readers.

The CJK Compatibility Forms block contains characters kept for compatibility with older encodings rather than for modern text flow. It often appears in legacy documents or systems that relied on specific glyph shapes for forms and punctuation. For UI work, treat these code points as historical artifacts rather than primary content, and prefer more stable characters when possible.

In practice, design teams should anticipate inconsistent rendering and provide clear guidance to developers and content authors. When needed, link to related blocks such as Geometric Shapes Block, Arrows Block, Currency Symbols, and Box Drawing Block to show how compatibility forms interact with other symbol families. The historical role of this block is to preserve round-trip data compatibility across platforms rather than to convey new meaning in modern text workflows.