VERIFICATION PROCESS
Sources and methodology
Last reviewed September 6, 2026
Every character page combines a copyable Unicode value with source-checked technical data, conditional typing instructions, and language context.
Character identity and codes
Unicode is the primary source for code points, formal character names, decomposition information, and relationships between similar characters. We check the current Unicode character charts and names lists rather than inferring identity from a glyph’s appearance.
HTML decimal entities are calculated from the Unicode code point. Named HTML character references are included only when a recognized named form exists. We keep Unicode hexadecimal values, HTML decimal references, and Windows Alt sequences in separate columns because they are different systems.
Keyboard instructions
We prefer first-party instructions such as Apple’s accent-entry guidance and Microsoft’s Unicode and character-code guidance. Instructions state the applicable platform or app. When a shortcut assumes the US, ABC, or another input layout, the page says so.
Windows Alt codes receive extra care because behavior can vary with the application, keyboard hardware, active code page, and presence of a numeric keypad. A character without a dependable legacy sequence is labeled “Not standard” instead of being assigned an uncertain code.
Language and spelling information
Language usage is checked against official orthographies, language academies, Unicode annotations, and established dictionaries or institutional references. We distinguish the stable technical identity of a character from its linguistic function. For example, German ü and Spanish ü share one code point, although the dots have a different role in each language.
Examples are used to demonstrate a spelling or character distinction. Translations are kept short and are not intended to replace a dictionary or language course.
How the copy tools are tested
The tool must expose a real button with an accessible name for every character. Selecting a character should copy that exact Unicode string and provide a status message. Write mode should insert at the current cursor position, replace selected text, preserve surrounding text, and copy the complete result.
We test representative tools with a keyboard and pointer at desktop and mobile viewport sizes. Checks include focus visibility, button labels, clipboard success and fallback messaging, text insertion, horizontal table scrolling, responsive layout, and readable status announcements. The tools operate in the browser and do not intentionally send composed text to the website server or analytics.
Publishing and technical checks
Before deployment, the production build must complete and each intended URL must render core content in static HTML. We check titles, H1 headings, absolute canonicals, breadcrumbs, structured data, sitemap membership, internal links, Markdown mirrors, and the site’s llms.txt index. These checks help keep the website and its downloadable references consistent.
After release, search performance reports can help identify pages that are difficult to discover or need clearer explanations. Analytics can show which pages and tools readers use, but it does not replace accuracy review.
Updates and corrections
A review may be triggered by a reader report, a software change, a Unicode update, an official spelling change, a broken source, or observed search overlap. We correct the underlying page source, rebuild all derived formats, retest links and structured data, and then deploy the consistent result.
Send corrections to [email protected]. The editorial policy explains how reports are handled.