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

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

From: Aaron Leventhal <aaronl@netscape.com>
Date: Mon, 05 Mar 2001 17:57:17 -0800
Message-ID: <3AA443FC.C6D23B36@netscape.com>
To: w3c-wai-ua@w3.org
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 20:55:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:30 UTC