W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 2005

ATAG 2.0 Comments on Glossary

From: Harvey Bingham <hbingham@acm.org>
Date: Fri, 14 Jan 2005 09:54:57 -0500
Message-Id: <6.2.0.14.2.20050114015102.02824490@pop.rcn.com>
To: w3c-wai-eo@w3.org w3c-wai-au@w3.org
Cc: public-wai-eo-lexicon@w3.org

Reference: W3C Working Draft 22 November 2004

These comments are more detailed than the discussion in the eo group.


Glossary (Normative):

Normative implies these terms must be interpreted as given; often in
conflict with their definitions in other WAI documents.

Accessibility Problem, Authoring Interface -- reference to ISO-TS-16071  may
be a problem, as it is not generally available, I suspect few (including 
me) are
willing to pay for it, and so may be trapped into failing to meet some obscure
requirement therein. Is there anything in its content that cannot be subsumed
in ATAG?

Display: presentation to the author; should be extended to consider the 
equivalent alternatives that the reader may be using -- as some of these
make different demands on how the author prepares content for the
alternative presentations to different end-users, in different environments.

Element  ?why diverge from the more technical definition used in markup
language descriptions?  For some readers who are familiar with these other
uses, the more general use will be confusing. [You do indicate therein that
XML does have the more technical meaning.]

Further: it is not clear that the "pair of tags and their content" includes
attributes as well as whatever comes between the pair of tags.

Possible alternatives to your use of Element include chunk, item, or object.

Equivalent Alternative is missing any scene description. [The Audio Description
does indicate this capability -- I think it may apply to the other uses of 
equivalent
alternatives.]

Editing Method: speaks of editable property -- as if some properties need
not be editable -- such as attribute-value pairs, preparation of metadata,
matching tag pairing and proper nesting, etc.

Markup language
should include XML (or applications of XML.) It certainly is more common 
than MATHML!

What about inaccessible pdf, which Adobe would claim is a markup language.  
Received on Friday, 14 January 2005 14:55:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:52 UTC