areeveclg
commented
3 years ago As per the checklist (albeit abbreviated):
Spec contains any natural language? No. It does contain elements that will be augmented with natural language including both text and audio, but the spec itself does not.
Typographically appealing text? N/A
Point into text (aka creating fragments/selections) This is questionable. Once could create an alias for a text node and then what happens if the node's text is partially selected? We can't map that to the alias' text.
Searching/matching? Finding alt text? TTS reads something with an alias and then a search is done on heard content. Should we find the aliased, but not visible, content?
Sorts text? N/A
Captures user input? N/A
Deals with time? We do have attributes that use time oriented data and use things like an 's' suffix to indicate seconds and reading content as a date or a time.
Character encoding other than UTF-8? N/A
Names, address, time & date formats? Yes - date/time
Describes data needing localization? This spec augments the existing document with 'compatible' alternatives based on the existing text and its language. Discuss with i18n.
Cultural norms? We allow for a flexible choice of voices and languages. Discuss.
r12a
ruoxiran
Short i18n review checklist is here, we need to go through this checklist as the initial check of i18n.
Here is a good example for us to reference.