Edit comment LC-796 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-833 Next: LC-964

Comment LC-796: Comment Shortname:; Commenter: Joe Clark 1 <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:
Comment:

From http://lists.w3.org/Archives/Public/public-comments-wcag20/2006May/0120.html

Ensure that numerals or other look alike glyphs are not used in place of letters

There goes your l33tspeak, h4xorz! (\/\/C4G iz teh sux0r @nyw@y111oneoneone); Related issues: (space separated ids); WG Notes: [TEAMC] If the intention of the comment is to remove the advice against leetspeak, we should not accept it: leetspeak makes no sense to text-to-speech users (whether blind or with cognitive disabilities). For more on leetspeak see e.g. http://www.microsoft.com/athome/security/children/leetspeak.mspx and http://en.wikipedia.org/wiki/L33tspeak. -- In a follow-up e-mail Joe Clark clarified that his comment was not meant to re ject the advisory technique or to change its title. Discussed in the 20 July 2006 telecon: Resolution: LC-796 is referred back to team C. The working group does not consider Leetspeak to be accessible. http://www.w3.org/WAI/GL/2006/07/20-wai-wcag-minutes.html#item06 Discussed in the 27 July 2006 telecon: resolution: close LC-796 adding the following 4 techniques: Failure of SC 1.1.1 due to using look-alike glyphs to represent text without providing a text alternative., Providing text alternatives for strings where look-alike glyphs are used in place of letters (e.g. Leetspeak)., Failure of SC 1.1.1 due to using ASCII art without providing a text alternative., Providing text alternatives for ASCII art. http://www.w3.org/WAI/GL/2006/07/27-wai-wcag-minutes.html [???] DONE (future links in draft, listed in wiki to-do) Create the following 4 techniques: Failure of SC 1.1.1 due to using look-alike glyphs to represent text without providing a text alternative. Providing text alternatives for strings where look-alike glyphs are used in place of letters (e.g. Leetspeak). Failure of SC 1.1.1 due to using ASCII art without providing a text alternative. Providing text alternatives for ASCII art. DONE Update note to definition of 'non-text content': add " and leetspeak, which is character substitution". DONE Move advisory technique from SC 1.3.4 to SC 1.1.1 (non-text content). [Content contributed by users of a web site is an issue that is treated separately.] Internal WD updated 24 August.; Resolution: The working group does not consider leetspeak to be accessible. We have moved the advisory technique from SC 1.3.4 to SC 1.1.1, where it was changed into the following techniques and failures: * Failure of SC 1.1.1 due to using look-alike glyphs to represent text without providing a text alternative. * Providing text alternatives for strings where look-alike glyphs are used in place of letters (e.g. Leetspeak). * Failure of SC 1.1.1 due to using ASCII art without providing a text alternative. * Providing text alternatives for ASCII art. We have also updated the note to the definition of non-text content so that it reads: 'This includes ASCII Art, which is a pattern of characters, and leetspeak, which is character substitution.'; (Please make sure the resolution is adapted for public consumption)