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

Re: What's the real-life meaning of an element?

From: Al Gilman <asgilman@iamdigex.net>
Date: Mon, 05 Mar 2001 22:59:45 -0500
Message-Id: <200103060340.WAA5150287@smtp2.mail.iamworld.net>
To: aaronl@netscape.com (Aaron Leventhal), w3c-wai-ua@w3.org
These are "the right questions" but the next document to try to answer them is
the XML Guidelines in work in the PF Working Group.

Even for HTML today, the answers to these questions are not that clear.  That
is partly why we don't have any more specific requirements in Checkpoints 7.6
(navigation) and 8.4 (orientation) than we do.


At 05:57 PM 2001-03-05 -0800, Aaron Leventhal wrote:
>When implementing an accessibility feature on a particular XML type, I
>(or a 3rd party) need some real down-to-earth information. I need to
>know what a tag is really "for".
>For example, to implement an outline view, I need to know what this
>document calls headings. Does it call them <h1>..<h6> or <hdg level="1">
>...<hdg level="6">.
>This might also be an issue for UI controls. The might be using Xforms,
>XUL, or another XML language for the widgets. How does the accessibility
>feature know what a "3dbutton" is, if it's  never seen one before.
>- Are we going to expect that the accessibility software will need to be
>upgraded for each new type of XML?
>- Perhaps will it pull a new module off the web for each kind,
>- Will there be an attribute bound on each element that tells what it's
>"role" and "state" are in generic terms
>- Can we relate new elements to old elements using RDF or Schemas, so
>that "xul:radiogroup" can be accessible by saying it inherits
>accessibility from "xform:multipleSelect" ?
>Don't need this tomorrow - just thought I'd get people's brains working
>way ahead of time.
Received on Monday, 5 March 2001 22:41:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:29 UTC