- From: Charles McCathieNevile <charles@w3.org>
- Date: Mon, 22 Mar 1999 08:31:12 -0500 (EST)
- To: jon gunderson <jongund@ux1.cso.uiuc.edu>
- cc: w3c-wai-ua@w3.org
These things can be done, but I am not sure that tagging them is the best
way to go about it - it is a repair strategy for poor design. What should
be done is:
Collections of anchors:
use MAP
TABLE:
there should not be layout tables
events:
Events can change the DOM - either at the level of a content node or (in
DOM2) changing style properties (which is the well-designed way to do
rollover highlights etc so they can be reproduceed across different
devices). These changes can be tested, and can probably be tested in
advance as a repair strategy.
Verification events are pretty meaningless unless they have some effect.
If that effect is to make a specialised call to the server (eg saying what
is wrong) then there is not much that can be done to track them. If they
actually change the DOM (eg making a note for an input that was not
well-formed) then they would look like transformation events, and teh
heuristic for finding them would be based on the fact that they are
attached to particular types of elements (INPUT, SUBMIT, etc)
Charles McCN
On Fri, 19 Mar 1999, jon gunderson wrote:
Is there a way we could add a general section on tagging the
purpose of certain elements. For example the following types of elements
could indicate their purpose:
Anchors: navigation link
Table: layout or table
Event: decorative, used for visual affects
verify, checks the user input, but no visual affects
functional, is used to change content of the document
--Charles McCathieNevile mailto:charles@w3.org
phone: +1 617 258 0992 http://www.w3.org/People/Charles
W3C Web Accessibility Initiative http://www.w3.org/WAI
MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA
Received on Monday, 22 March 1999 08:31:15 UTC