Edit comment LC-849 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-808 Next: LC-1500

Comment LC-849: Comment Shortname:; Commenter: Joe Clark 2 <joeclark@joeclark.org>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
From http://lists.w3.org/Archives/Public/public-comments-wcag20/2006May/0119.html

text
sequence of characters[INS: [.] :INS] Note: Characters are those included in the Unicode/ISO/IEC 106464 repertoire.

One may use only characters in Unicode. Given that several scripts are [8]unencoded in Unicode, this may present a problem. Some East Asian languages are more robustly published with legacy encodings even if that is ""improper."" I repeatedly tried to explain to the Working Group that all that matters is a defined and understandable character encoding.; Related issues: (space separated ids); WG Notes: [EDITORZ] originally proposed: add "or characters that can be mapped into this repertoire." to the end of the definition of "text" respond with: We have added "or characters that can be mapped into this repertoire." to the end of the definition of text. -- Discussed in the 20 July 2006 telecon: Resolution: refer LC-849 back to the editors to explore baseline approach http://www.w3.org/WAI/GL/2006/07/20-wai-wcag-minutes.html BBC: Not sure what "baseline approach" refers to above. Survey comments are http://www.w3.org/2002/09/wbs/35422/20060720editorz/results#x849 I have included a slightly modified version of Michael's proposal below. Christophe also had a good suggestion here, but since the definition we have is already based on extended discussion with I18N and all currently-used Web encodings already map to unicode, then the revised note should cover it. Discussed in the 17 August 2006 telecon: resolution: unanimous consent to accept the following proposals from the Editorz: LC-847, LC-849, LC-850, LC-1006, LC-987, LC-936, LC-890, LC-852 resolution: unanimous consent to accept the following proposals from Team C: LC-1047, LC-1082, LC-1089, LC-1116, LC-1117, LC-1196, LC-1326 resolution: unanimous consent to accept the following proposals from Team B: LC-1127 http://www.w3.org/WAI/GL/2006/08/17-wai-wcag-minutes.htm DONE Add a note to the definition of "text": Note 1: DONE add a an entry to references as follows: [I18N-CHAR-ENC] "Tutorial: Character sets & encodings in XHTML, HTML and CSS," R. Ishida, ed., This tutorial is available at http://www.w3.org/International/tutorials/tutorial-char-enc/. DONE Modify note 1 in the definition of unicode to read, For more information, refer to [UNICODE] or [I18N-CHAR-ENC]. Internal WD updated 24 August. Discussed in the 10 May 2007 telecon: Accepted by Unanimous Consent http://www.w3.org/WAI/GL/2007/05/10-wai-wcag-minutes.html; Resolution: We have changed the definition of text and non-text so that it is clear that we don't preclude the use of non-Unicode encodings as long as AT can handle them (i.e. they can be 'programmatically determined'). text: http://www.w3.org/TR/2007/WD-WCAG20-20070517/#textdef non-text content: http://www.w3.org/TR/2007/WD-WCAG20-20070517/#non-text-contentdef; (Please make sure the resolution is adapted for public consumption)