REAL-WORLD INTERPRETIVE
UTF-8 is the baseline, not the finish line
The audit verifies byte-preserving storage and display of diacritics, combining marks, non-Latin scripts, emoji where legitimate, and mixed-script text. Examples include Türkiye, Guernésiais, 王明, محمد, and አበበ ተስፋዬ. Destructive ASCII normalization is prohibited outside a separate search index.
REAL-WORLD INTERPRETIVE
Text direction follows content
Dynamic human-language text uses direction-aware semantics such as dir="auto" so right-to-left and mixed-script names, quotations, and punctuation render intelligibly. Direction is attached to content fields when known and is not inferred from nationality.
REAL-WORLD INTERPRETIVE
Name integrity persists across views
Cards, headings, tables, search results, exports, citations, print views, and correction forms preserve preferred display name, original script, sequence, and transliteration labels. Truncation must not remove the only distinguishing component or silently reverse order.
REAL-WORLD INTERPRETIVE
Assistive access is structural
Headings follow a logical hierarchy; landmarks and skip links work; controls have names, states, and keyboard access; tables have headers and text equivalents; focus is visible; motion can be reduced; contrast is sufficient; and dynamic updates announce themselves appropriately.
REAL-WORLD INTERPRETIVE
Confidence and status use words and structure
Evidence labels, warnings, corrections, uncertainty, and game states include explicit text, icons with labels, and semantic markup. Color may reinforce meaning but cannot carry it alone.
REAL-WORLD INTERPRETIVE
Test with content that can break assumptions
Release tests include long compound names, mononyms, duplicate names, right-to-left text, mixed scripts, diacritics, narrow screens, zoom, keyboard-only use, screen readers, high contrast, reduced motion, printing, and data export. Failures block publication or receive a documented exception with owner and repair date.