W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2009

[Bug 6657] Comment 3 (of 4) from WAI-PF

From: <bugzilla@wiggum.w3.org>
Date: Fri, 06 Mar 2009 01:21:20 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1LfOka-0007Cq-93@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6657





--- Comment #1 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>  2009-03-06 01:21:19 ---
Created an attachment (id=656)
 --> (http://www.w3.org/Bugs/Public/attachment.cgi?id=656)
draft long description for Built-in Datatypes Hierarchy diagram

I attach a draft long description of the built-in datatypes hierarchy diagram,
for
examination and comment by those better versed in current practice than I am.

I have attempted to describe the diagram as I would if it occurred in a book I
was reading for Recording for the Blind and Dyslexic, but (a) it is some years
since I did any reading for RFB, so I'm out of practice, and (b) I do not know
if
this is considered the appropriate level of detail for long descriptions of
images
in HTML documents.  I also don't know the answers to several questions that
arose while drafting.  On any and all of them, I would welcome input from 
participants in WAI, or from potential users or readers of the description.

1 There are no headings in the longdesc document.  Should it have an HTML 
"h1" element at the beginning of the page?  Should there be "h2" heading
elements at the beginning of the overview and at the beginning of the 
detailed description?  (There are div elements, in the hopes that they 
may be useful for navigation.)

2 Every occurrence of a box label is hyperlinked to the corresponding section
of the spec.  This is simple and consistent and means I don't have to decide
which occurrence of a label is the 'main' occurrence.  If links are distracting
to readers, however, then I can imagine readers preferring that fewer phrases
in the description be hyperlinked.  What does good style in the formulation of
long descriptions prescribe here?

3 Should the longdesc document have a navbar of its own?

Any other suggestions which would improve the utility of this long
description for readers of the spec would be gratefully accepted.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 6 March 2009 01:21:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:09 UTC