Re: Goals of accessible templates

If it passes WCAG AAA then it doesn't need to pass Bobby...

I presume you are not talking about producing PDF templates. I would suggest
for print good that it comes out as well as common sites around (pick a few
from your bookmarks list). There is a printCSS implementation in Amaya, if
anyone wants to test it out.

cheers

Charles McCN

On Wed, 1 Mar 2000 pjenkins@us.ibm.com wrote:

  
  
  Please comment on my new prioritized goals for templates:
  
  1. Must pass WCAG AAA
  2. Must look good, sound good, Braille good, and print good:
       "Look good" means it looks good on Nav4, IE4, IE5, and Opera
       "Sound good" on IBM Home Page Reader and PW WebSpeak
       "Braille good" on latest screen readers w/Braille display
       "print good" means ? [dare I say pdf]
  3. Should pass BOBBY.
  4. Should be valid code
  
  
  Jutta wrote:
  >... My sense of the priorities is:
  >should pass WCAG AAA which can be further verified by the tests you
  listed.
  
  pjenkins@us.ibm.com wrote:
  >
  >
  >Some things I wanted to discuss is the scope of the template:
  >In priority order:
  >1. Must look good, sound good, Braille good, and print good:
  >     "Look good" means it looks good on Nav4, IE4, IE5, and Opera
  >     "Sound good" on IBM Home Page Reader and PW WebSpeak
  >     "Braille good" on JFW 3.5? on Windows w/Braille display
  >     "print good" means ?
  >2. Should pass BOBBY.
  >3. Should be valid code.
  
  
  

--
Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
W3C Web Accessibility Initiative                      http://www.w3.org/WAI
Location: I-cubed, 110 Victoria Street, Carlton VIC 3053
Postal: GPO Box 2476V, Melbourne 3001,  Australia

Received on Wednesday, 1 March 2000 17:24:46 UTC