Example checklist

Language

Language basics

1. It should be possible to associate a language with any piece of natural language text that will be read by a user. more

NA

1. Where possible, there should be a way to label natural language changes in inline text. more

NA

1. Consider whether it is useful to express the intended linguistic audience of a resource, in addition to specifying the language used for text processing. more
2. A language declaration that indicates the text-processing language for a range of text must associate a single language value with a specific range of text. more
3. Use the HTML lang and XML xml:lang language attributes where appropriate, rather than creating a new attribute or mechanism. more
4. A metadata-type language declaration that indicates the intended use of the resource, rather than the language of a specific range of text, may be associated with multiple language values. more

Defining language values

1. Values for language declarations must use BCP 47. more
2. Refer to BCP 47, not to RFC 5646. more
3. Be specific about what level of conformance you expect for language tags. The word "valid" has special meaning in BCP 47. Generally "well-formed" is a better choice.
4. Reference BCP47 for language tag matching.

Declaring language at the resource level

1. The specification should indicate how to define the default text-processing language for the resource as a whole. more

4.20.13

1. Content within the resource should inherit the language of the text-processing declared at the resource level, unless it is specifically overridden.
2. Consider whether it is necessary to have separate declarations to indicate the text-processing language versus metadata about the expected use of the resource. more
3. If there is only one language declaration for a resource, and it has more than one language tag as a value, it must be possible to identify the default text-processing language for the resource. more

Establishing the language of a content block

1. By default, blocks of content should inherit any text-processing language set for the resource as a whole. more
2. It should be possible to indicate a change in language for blocks of content where the language changes. more

Establishing the language of inline runs

1. It should be possible to indicate language for spans of inline text where the language changes. more

NA

Text direction

Basic requirements

1. It must be possible to indicate base direction for each individual paragraph-level item of natural language text that will be read by someone. more

NA

1. It must be possible to indicate base direction changes for embedded runs of inline bidirectional text for all natural language text that will be read by someone. more

NA

1. Annotating right-to-left text must require the minimum amount of effort for people who work natively with right-to-left scripts. more

NA

Background information

1. Do not assume that direction can be determined from language information. more

NA

Handling direction in markup

1. The spec should indicate how to define a default base direction for the resource as a whole, ie. set the overall base direction. more

NA

1. The default base direction, in the absence of other information, should be LTR. more
2. Values for the default base direction should include left-to-right, right-to-left, and auto. more
3. The content author must be able to indicate parts of the text where the base direction changes. At the block level, this should be achieved using attributes or metadata, and should not rely on Unicode control characters.
4. It must be possible to also set the direction for content fragments to auto. This means that the base direction will be determined by examining the content itself.
5. If the overall base direction is set to auto for plain text, the direction of content paragraphs should be determined on a paragraph by paragraph basis.
6. To indicate the sides of a block of text where relative to the start and end of its contained lines, you should use 'before' and 'after' (maybe block-start/block-end – the terminology is changing), rather than 'top' and 'bottom'.
7. To indicate the start/end of a line you should use 'start' and 'end' rather than 'left' and 'right'.
8. Provide dedicated attributes for control of base direction and bidirectional overrides; do not rely on the user applying style properties to arbitrary markup to achieve bidi control.
9. It must be possible to indicate spans of inline text where the base direction changes. If markup is available, this is the preferred method. Otherwise your specification must require that Unicode control characters are recognized by the receiving application, and correctly implemented.
10. It must be possible to also set the direction for a span to auto. This means that the base direction will be determined by examining the content itself. A typical approach here would be to set the direction based on the first strong directional character outside of any markup. more
11. If users use Unicode bidirectional control characters, the RLI/LRI/FSI with PDI characters must be supported by the application and recommended (rather than RLE/LRE with PDF) by the spec.
12. Use of RLM/LRM should be appropriate, and expectations of what those controls can and cannot do should be clear in the spec. more
13. Provide dedicated attributes for control of base direction and bidirectional overrides; do not rely on the user applying style properties to arbitrary markup to achieve bidi control.
14. Allow bidi attributes on all inline elements in markup that contain text.
15. Provide attributes that allow the user to (a) create an embedded base direction or (b) override the bidirectional algorithm altogether; the attribute should allow the user to set the direction to LTR or RTL in either of these two scenarios.

Characters

Choosing a definition of 'character'

1. Specifications, software and content MUST NOT require or depend on a one-to-one correspondence between characters and the sounds of a language. more
2. Specifications, software and content MUST NOT require or depend on a one-to-one mapping between characters and units of displayed text. more
3. Protocols, data formats and APIs MUST store, interchange or process text data in logical order. more
4. Independent of whether some implementation uses logical selection or visual selection, characters selected MUST be kept in logical order in storage. more
5. Specifications of protocols and APIs that involve selection of ranges SHOULD provide for discontiguous logical selections, at least to the extent necessary to support implementation of visual selection on screen on top of those protocols and APIs. more
6. Specifications and software MUST NOT require nor depend on a single keystroke resulting in a single character, nor that a single character be input with a single keystroke (even with modifiers), nor that keyboards are the same all over the world. more
7. Specifications, software and content MUST NOT require or depend on a one-to-one relationship between characters and units of physical storage. more
8. When specifications use the term 'character' the specifications MUST define which meaning they intend. more
9. Specifications SHOULD use specific terms, when available, instead of the general term 'character'. more

Defining a Reference Processing Model

1. Textual data objects defined by protocol or format specifications MUST be in a single character encoding. more
2. All specifications that involve processing of text MUST specify the processing of text according to the Reference Processing Model described by the rest of the recommendations in this list. more
3. Specifications MUST define text in terms of Unicode characters, not bytes or glyphs. more
4. For their textual data objects specifications MAY allow use of any character encoding which can be transcoded to a Unicode encoding form. more
5. Specifications MAY choose to disallow or deprecate some character encodings and to make others mandatory. Independent of the actual character encoding, the specified behavior MUST be the same as if the processing happened as follows: (a) The character encoding of any textual data object received by the application implementing the specification MUST be determined and the data object MUST be interpreted as a sequence of Unicode characters - this MUST be equivalent to transcoding the data object to some Unicode encoding form, adjusting any character encoding label if necessary, and receiving it in that Unicode encoding form, (b) All processing MUST take place on this sequence of Unicode characters, (c) If text is output by the application, the sequence of Unicode characters MUST be encoded using a character encoding chosen among those allowed by the specification. more
6. If a specification is such that multiple textual data objects are involved (such as an XML document referring to external parsed entities), it MAY choose to allow these data objects to be in different character encodings. In all cases, the Reference Processing Model MUST be applied to all textual data objects. more

Including and excluding character ranges

1. Specifications SHOULD NOT arbitrarily exclude code points from the full range of Unicode code points from U+0000 to U+10FFFF inclusive. more
2. Specifications MUST NOT allow code points above U+10FFFF. more
3. Specifications SHOULD NOT allow the use of codepoints reserved by Unicode for internal use. more
4. Specifications MUST NOT allow the use of surrogate code points. more
5. Specifications SHOULD exclude compatibility characters in the syntactic elements (markup, delimiters, identifiers) of the formats they define. more

Using the Private Use Area

1. Specifications MUST NOT require the use of private use area characters with particular assignments. more
2. Specifications MUST NOT require the use of mechanisms for defining agreements of private use code points. more
3. Specifications and implementations SHOULD NOT disallow the use of private use code points by private agreement. more
4. Specifications MAY define markup to allow the transmission of symbols not in Unicode or to identify specific variants of Unicode characters. more
5. Specifications SHOULD allow the inclusion of or reference to pictures and graphics where appropriate, to eliminate the need to (mis)use character-oriented mechanisms for pictures or graphics. more

Choosing character encodings

1. Specifications MUST either specify a unique character encoding, or provide character encoding identification mechanisms such that the encoding of text can be reliably identified. more
2. When designing a new protocol, format or API, specifications SHOULD require a unique character encoding. more
3. When basing a protocol, format, or API on a protocol, format, or API that already has rules for character encoding, specifications SHOULD use rather than change these rules. more
4. When a unique character encoding is required, the character encoding MUST be UTF-8, UTF-16 or UTF-32. more
5. Specifications SHOULD avoid using the terms 'character set' and 'charset' to refer to a character encoding, except when the latter is used to refer to the MIME charset parameter or its IANA-registered values. The term 'character encoding', or in specific cases the terms 'character encoding form' or 'character encoding scheme', are RECOMMENDED. more
6. If the unique encoding approach is not taken, specifications SHOULD require the use of the IANA charset registry names, and in particular the names identified in the registry as 'MIME preferred names', to designate character encodings in protocols, data formats and APIs. more
7. Character encodings that are not in the IANA registry SHOULD NOT be used, except by private agreement. more
8. If an unregistered character encoding is used, the convention of using 'x-' at the beginning of the name MUST be followed. more
9. If the unique encoding approach is not chosen, specifications MUST designate at least one of the UTF-8 and UTF-16 encoding forms of Unicode as admissible character encodings and SHOULD choose at least one of UTF-8 or UTF-16 as required encoding forms (encoding forms that MUST be supported by implementations of the specification). more
10. Specifications that require a default encoding MUST define either UTF-8 or UTF-16 as the default, or both if they define suitable means of distinguishing them. more

Identifying character encodings

1. Specifications MUST NOT propose the use of heuristics to determine the encoding of data. more
2. Specifications MUST define conflict-resolution mechanisms (e.g. priorities) for cases where there is multiple or conflicting information about character encoding. more

Designing character escapes

1. Specifications should provide a mechanism for escaping characters, particularly those which are invisible or ambiguous. more
2. Specifications SHOULD NOT invent a new escaping mechanism if an appropriate one already exists. more
3. The number of different ways to escape a character SHOULD be minimized (ideally to one). more
4. Escape syntax SHOULD require either explicit end delimiters or a fixed number of characters in each character escape. Escape syntaxes where the end is determined by any character outside the set of characters admissible in the character escape itself SHOULD be avoided. more
5. Whenever specifications define character escapes that allow the representation of characters using a number, the number MUST represent the Unicode code point of the character and SHOULD be in hexadecimal notation. more
6. Escaped characters SHOULD be acceptable wherever their unescaped forms are; this does not preclude that syntax-significant characters, when escaped, lose their significance in the syntax. In particular, if a character is acceptable in identifiers and comments, then its escaped form should also be acceptable. more

Storing text

1. Protocols, data formats and APIs MUST store, interchange or process text data in logical order. more
2. Specifications of protocols and APIs that involve selection of ranges SHOULD provide for discontiguous logical selections, at least to the extent necessary to support implementation of visual selection on screen on top of those protocols and APIs. more

Specifying sort and search functionality

1. Software that sorts or searches text for users SHOULD do so on the basis of appropriate collation units and ordering rules for the relevant language and/or application. more
2. Where searching or sorting is done dynamically, particularly in a multilingual environment, the 'relevant language' SHOULD be determined to be that of the current user, and may thus differ from user to user. more
3. Software that allows users to sort or search text SHOULD allow the user to select alternative rules for collation units and ordering. more
4. Specifications and implementations of sorting and searching algorithms SHOULD accommodate text that contains any character in Unicode. more

Converting to a Common Unicode Form

1. Specifications of text-based formats and protocols MAY specify that all or part of the textual content of that format or protocol is normalized using Unicode Normalization Form C (NFC). more
2. Specifications that do not normalize MUST document or provide a health-warning if canonically equivalent but disjoint Unicode character sequences represent a security issue. more
3. Specifications and implementations MUST NOT assume that content is in any particular normalization form. more
4. Specifications MUST specify that string matching takes the form of "code point-by-code point" comparison of the Unicode character sequence, or, if a specific Unicode character encoding is specified, code unit-by-code unit comparison of the sequences. more
5. Specifications that define a regular expression syntax MUST provide at least Basic Unicode Level 1 support per Unicode Technical Standard #18: Unicode Regular Expressions and SHOULD provide Extended or Tailored (Levels 2 and 3) support. more
6. Specifications of text-based formats and protocols that, as part of their syntax definition, require that the text be in normalized form MUST define string matching in terms of normalized string comparison and MUST define the normalized form to be NFC. more
7. A normalizing text-processing component which receives suspect text MUST NOT perform any normalization-sensitive operations unless it has first either confirmed through inspection that the text is in normalized form or it has re-normalized the text itself. Private agreements MAY, however, be created within private systems which are not subject to these rules, but any externally observable results MUST be the same as if the rules had been obeyed. more
8. Specifications of text-based languages and protocols SHOULD define precisely the construct boundaries necessary to obtain a complete definition of full-normalization. These definitions SHOULD include at least the boundaries between markup and character data as well as entity boundaries (if the language has any include mechanism) , SHOULD include any other boundary that may create denormalization when instances of the language are processed, but SHOULD NOT include character escapes designed to express arbitrary characters. more
9. Where operations can produce denormalized output from normalized text input, specifications of API components (functions/methods) that implement these operations MUST define whether normalization is the responsibility of the caller or the callee. Specifications MAY state that performing normalization is optional for some API components; in this case the default SHOULD be that normalization is performed, and an explicit option SHOULD be used to switch normalization off. Specifications SHOULD NOT make the implementation of normalization optional. more
10. Specifications that define a mechanism (for example an API or a defining language) for producing textual data object SHOULD require that the final output of this mechanism be normalized. more

Handling Case Folding

1. Case sensitive matching is RECOMMENDED as the default for new protocols and formats. more
2. Because the "simple" case-fold mapping removes information that can be important to forming an identity match, the "Common plus Full" (or "Unicode C+F") case fold mapping is RECOMMENDED for Unicode case-insensitive matching. more
3. ASCII case-insensitive matching MUST only be applied to vocabularies that are restricted to ASCII. Unicode case-insensitivity MUST be used for all other vocabularies. more
4. If the vocabulary is not restricted to ASCII or permits user-defined values that use a broader range of Unicode, ASCII case-insensitive matching MUST NOT be required. more
5. The Unicode C+F case-fold form is RECOMMENDED as the case-insensitive matching for vocabularies. The Unicode C+S form MUST NOT be used for string identity matching on the Web. more
6. Specifications and implementations that define string matching as part of the definition of a format, protocol, or formal language (which might include operations such as parsing, matching, tokenizing, etc.) MUST define the criteria and matching forms used. These MUST be one of: (a) Case-sensitive (b) Unicode case-insensitive using Unicode case-folding C+F (c) ASCII case-insensitive. more
7. Specifications SHOULD NOT specify case-insensitive comparison of strings. more
8. Specifications that specify case-insensitive comparison for non-ASCII vocabularies SHOULD specify Unicode case-folding C+F. more
9. Specifications MAY specify ASCII case-insensitive comparison for portions of a format or protocol that are restricted to an ASCII-only vocabulary. more
10. Specifications and implementations MUST NOT specify ASCII-only case-insensitive matching for values or constructs that permit non-ASCII characters. more

Defining 'string'

1. Specifications SHOULD NOT define a string as a 'byte string'. more
2. The 'character string' definition SHOULD be used by most specifications. more

Indexing strings

1. The character string is RECOMMENDED as a basis for string indexing. more
2. A code unit string MAY be used as a basis for string indexing if this results in a significant improvement in the efficiency of internal operations when compared to the use of character string. more
3. Grapheme clusters MAY be used as a basis for string indexing in applications where user interaction is the primary concern. more
4. Specifications that define indexing in terms of grapheme clusters MUST either: (a) define grapheme clusters in terms of default grapheme clusters as defined in Unicode Standard Annex #29, Text Boundaries [UTR #29], or (b) define specifically how tailoring is applied to the indexing operation. more
5. The use of byte strings for indexing is NOT RECOMMENDED. more
6. Specifications that need a way to identify substrings or point within a string SHOULD provide ways other than string indexing to perform this operation. more
7. Specifications SHOULD understand and process single characters as substrings, and treat indices as boundary positions between counting units, regardless of the choice of counting units. more
8. Specifications of APIs SHOULD NOT specify single characters or single 'units of encoding' as argument or return types. more
9. When the positions between the units are counted for string indexing, starting with an index of 0 for the position at the start of the string is the RECOMMENDED solution, with the last index then being equal to the number of counting units in the string. more

Referring to Unicode characters

1. Use U+XXXX syntax to represent Unicode code points in the specification. more

Referencing the Unicode Standard

1. Since specifications in general need both a definition for their characters and the semantics associated with these characters, specifications SHOULD include a reference to the Unicode Standard, whether or not they include a reference to ISO/IEC 10646. more
2. A generic reference to the Unicode Standard MUST be made if it is desired that characters allocated after a specification is published are usable with that specification. A specific reference to the Unicode Standard MAY be included to ensure that functionality depending on a particular version is available and will not change over time. more
3. All generic references to the Unicode Standard MUST refer to the latest version of the Unicode Standard available at the date of publication of the containing specification. more
4. All generic references to ISO/IEC 10646 MUST refer to the latest version of ISO/IEC 10646 available at the date of publication of the containing specification. more

Resource identifiers

Basics

1. ​Resource identifiers must permit the use of characters outside those of plain ASCII. discussion
2. Specifications MUST define when the conversion from IRI references to URI references (or subsets thereof) takes place, in accordance with Internationalized Resource Identifiers (IRIs). more

Markup & syntax

Defining elements and attributes

1. Do not define attribute values that will contain user readable content. Use elements for such content. more
2. If you do define attribute values containing user readable content, provide a means to indicate directional and language information for that text separately from the text contained in the element.
3. Provide a way for authors to annotate arbitrary inline content using a span-like element or construct. more

Defining identifiers

1. Identifiers should be case-sensitive.

Working with plain text

1. Avoid natural language text in elements that only allow for plain text and in attribute values.
2. Provide a span-like element that can be used for any text content to apply information needed for internationalization. more

Typographic support

Text decoration

1. Text decoration such as underline and overline should allow lines to skip ink.
2. It should be possible to specify the distance of overlines and underlines from the text. more

Vertical text

1. It should be possible to render text vertically for languages such as Japanese, Chinese, Korean, Mongolian, etc.
2. Vertical text must support line progression from LTR (eg. Mongolian) and RTL (eg. Japanese)
3. By default, text decoration, ruby, and the like in vertical text where lines are stacked from left to right (eg. Mongolian) should appear on the same side as for CJK vertical text. Placement should not rely on the before and after line locations.
4. Vertical writing modes that are equivalent to the vertical- values in CSS (only) should use UTR50 to apply default text orientation of characters. (This does not apply to writing modes that are equivalent to sideways- in CSS.)
5. By default, glyphs of scripts that are normally horizontal should run along a line in vertical text such that the top of the character is toward the right side of the vertical line, but there should also be a mechanism to allow them to progress down the line in upright orientation. Such a mechanism should use grapheme clusters as a minimum text unit, but where necessary allow syllabic clusters to be treated as a unit when they involve more than one grapheme cluster.
6. Upright Arabic text in vertical lines should use isolated letter forms and the order of text should read top to bottom.
7. It should be possible for some sequences of characters (particularly digits) to run horizontally within vertical lines (tate chu yoko).
8. Writing modes should provide values like sideways-lr and sideways-rl in CSS to allow for vertical rotation of lines of horizontal script text. UTR50 is not applicable for these cases.

Setting box positioning coordinates when text direction varies

1. Box positioning coordinates must take into account whether the text is horizontal or vertical. more

Ruby text annotations

1. 'Ruby' style annotations alongside base text should be supported for Chinese, Japanese, Korean and Mongolian text, in both horizontal and vertical writing modes.
2. Ruby implementations should support zhuyin fuhao (bopomofo) ruby for Traditional Chinese.
3. Ruby implementations should support a tabular content model (such that ruby contents can be arranged in a sequence approximating to rb rb rt rt).
4. Ruby implementations should make it possible to use an explicit rb tag for ruby bases.
5. Ruby implementations should allow annotations to appear on either or both sides of the base text.

Miscellaneous

1. Line heights must allow for characters that are taller than English.
2. Box sizes must allow for text expansion in translation.
3. Line wrapping should take into account the special rules needed for non-Latin scripts. more
4. Avoid specifying presentational tags, such as b for bold, and i for italic. more

Local dates, times and formats

Working with time

1. When defining calendar and date systems, be sure to allow for dates prior to the common era, or at least define handling of dates outside the most common range.
2. When defining time or date data types, ensure that the time zone or relationship to UTC is always defined.
3. Provide a health warning for conversion of time or date data types that are "floating" to/from incremental types, referring as necessary to the Time Zones WG Note. more
4. Allow for leap seconds in date and time data types. more
5. Use consistent terminology when discussing date and time values. Use 'floating' time for time zone independent values.
6. Keep separate the definition of time zone from time zone offset.
7. Use IANA time zone IDs to identify time zones. Do not use offsets or LTO as a proxy for time zone.
8. Use a separate field to identify time zone.
9. When defining rules for a "week", allow for culturally specific rules to be applied. more
10. When defining rules for week number of year, allow for culturally specific rules to be applied.
11. When non-Gregorian calendars are permitted, note that the "month" field can go to 13 (undecimber).

Designing forms

1. When defining email field validation, allow for EAI (smtputf8) names.

Working with numbers

1. When parsing user input of numeric values, allow for digit shaping (non-ASCII digits).
2. When formatting numeric values for display, allow for culturally sensitive display, including the use of non-ASCII digits (digit shaping).

Navigation

Providing for content negotiation based on language

1. In a multilingual environment it must be possible for the user to receive text in the language they prefer. This may depend on implicit user preferences based on the user's system or browser setup, or on user settings explicitly negotiated with the user.