W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2001

RE: Split UAAG 1.0 and Techniques into smaller documents?

From: Denis Anson <danson@miseri.edu>
Date: Tue, 10 Apr 2001 09:53:45 -0400
To: "'Charles McCathieNevile'" <charles@w3.org>
Message-ID: <000501c0c1c5$a98dbb50$17dcc241@deniscomputer>
I agree.  Long load times are a bummer, and well linked sections would
improve things for web readers.

Denis Anson, MS, OTR/L
Assistant Professor
College Misericordia
301 Lake St.
Dallas, PA 18612
 


-----Original Message-----
From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org] On
Behalf Of Charles McCathieNevile
Sent: Tuesday, April 10, 2001 7:24 AM
To: Ian Jacobs
Cc: w3c-wai-ua@w3.org
Subject: Re: Split UAAG 1.0 and Techniques into smaller documents?


Actually I think it is a fine idea.

I agree that it isn't a high priority, but I suspect itonly takes a few
minutes to do.

Chaals

On Mon, 9 Apr 2001, Ian Jacobs wrote:

  Hi folks,

  I probably shouldn't do this, but I am curious to know whether
  people think we should break UAAG 1.0 and the Techniques
  documents into smaller chunks. UAAG 1.0 (not including
  the appendixes) is 322k. The Techniques Document is 533k.
  These are both on the long side.

  It would be possible (though I haven't tried it yet to see
  what kind of effort is required) to split the document(s)
  into smaller pieces. We would also provide a link at
  the top to a single source HTML version (essentially,
  what people get today).

  The W3C Process Document [1] has been organized this way.
  Essentially, you only get the table of contents on the first
  page (in the Process Document case, that's only 18k).

  In the UAAG 1.0 case, it makes sense to split the
  document into the following pieces:

   a) Front page
   b) Introduction
   c) Guidelines
   d) Conformance
   e) Glossary
   f) References
   g) Acknowledgments

  For instance, the Guidelines section (the longest) would only
  be approximately 162k. The appendixes (checklists and summary)
  would still have their own URIs (but are considered part of
  the document package).

  The navigation mechanisms of the Process Document are pretty
  straightforward: you have next/previous/contents links
  at the top of each section.

  Obviously, this doesn't change the substance of the document,
  but it may be worth exploring. Your comments welcome,

   - Ian

  [1] http://www.w3.org/Consortium/Process-20010208/


-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61
409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1
617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex,
France)
Received on Tuesday, 10 April 2001 09:56:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:49 GMT