RE: Goals of accessible templates

A template that did this would be great. But for the moment we will also need
plain boring HTML templates, since ther are a lot of authors who aren't going
to accept cutting out people who don't have XSLT, and don't have sufficient
control over their servers to do it server-side. (And a lot of developers who
won't credit their customers with the intellect to do that anyway. Presumably
because there are a lot of customers who will say it is too complex and they
just want something they can cut and paste text into and "publish".)

Charles

On Thu, 2 Mar 2000, Pawson, David 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
  
  Suggestion.
  Markup in XML.
  XSLT to HTML, strict 4 dtd. 
  (optional) to HTML targetted at HPR and Webspeak,
  though I know they are good with good html.
  XSLT to plain ASCII for braille displays, with good para and line breaks.
  XSL to pdf for good print.
  Validate with whatever in the DTD of choice.
  
  First time I've heard a statement of intent for
  multi media output on WAI. We are getting there.
  
  
  Regards, DaveP
  

--
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 Thursday, 2 March 2000 04:07:08 UTC