- From: Gregg Vanderheiden <gv@wiscmail.wisc.edu>
- Date: Wed, 09 Jul 2003 12:16:47 -0500
- To: w3c-wai-gl@w3.org
Oops 2.4 should be Facilitate O & Nav. Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison -----Original Message----- From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Gregg Vanderheiden Sent: Wednesday, July 09, 2003 10:12 AM To: 'Katie Haritos-Shea'; w3c-wai-gl@w3.org Subject: RE: WCAG 2.0 Checkpoint "Handles" or Short Names I like this list Couple suggested changes. 1.3 change to "Separable from Presentation" or "Separable". -Rationale. We don't want to separate presentation. In fact you can't. 1.4 change to "Decodeable". - Rationale. Unicode only addresses the required success criteria -- not any of the rest of the checkpoint Then just shorten the others -- since they only have to be long enough to jog our memory. That would make them: 1. PERCEIVABLE 1.1. [c] Text Equivalents 1.2. [c] Synchronized Equivalents 1.3. [c] Separable from Presentation (or just Separable) 1.4. [c] Decodable 1.5. Emphasize Structure 1.6. Fore/Background 2. OPERABLE 2.1. [c] Keyboard 2.2. [c] Time-Limits 2.3. [c] Flicker 2.4. Orientation 2.5. Errors 3. UNDERSTANDABLE 3.1. [c] Language ID 3.2. [c] Abbvs. Etc. 3.3. Complexity 3.4. Predictable Layout 4. ROBUST 4.1. [c] Specs & Stds 4.2. Legacy 4.3. Accessible or Alternative Thanks Katie. Anyone want to take another pass? We need to look at how we would use these -- and then can see if these are good enough or need to be longer to catch all. Remember - if they are long enough to make sense in and of themselves, they will be used INSTEAD of the guidelines in short listings and this is not good. Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison Easily Scannable List to Quickly Identify Topic................ 1. PERCEIVABLE 1.1. [core] Text Equivalents 1.2. [core] Synch (Synchronize) Media 1.3. [core] Separate Presentation 1.4. [core] Unicode 1.5. Emphasize Structure 1.6. Fore and Background Info Clarity 2. OPERABLE 2.1. [core] Keyboard Operable 2.2. [core] Time-Limit Control (s) 2.3. [core] Flicker 2.4. User Orientation 2.5. Error Recovery 3. UNDERSTANDABLE 3.1. [core] Language ID 3.2. [core] Abbreviations & Acronyms 3.3. Complexity Control 3.4. Predictable Layout 4. ROBUST 4.1. [core] Adhere to Technical Specifications OR Follow Standards 4.2. Site HELP and Legacy Support OR Site Documentation and Backwards Compatibility 4.3. Support Accessibility APIs & Alternate Formats NOTE: New Contact Phone Numbers for Katie (Below) Katie Haritos-Shea Section 508 Technical Policy Analyst CESSI Accessible Solutions 6858 Old Dominion Drive Suite #250 McLean, Virginia, USA 22101 mailto:kshea@cessi.net mailto:ryladog@earthlink.net Voice: 703-448-6155 Fax: 703-442-9015 Mobile: 703-371-5545 "The best and most beautiful things in the world cannot be seen or even touched. They must be felt with the heart." - Helen Keller
Received on Wednesday, 9 July 2003 13:17:22 UTC