Standard markup - issues to resolve

I suggest the following:

Checkpoint x.1
The use of markup which does not conform to W3C standards must not
interfere with the user being able to access the form or function of a
document.

checkpoint x.2
Non-standard markup should not be used where it is possible t make use of
a W3C recommendation. In the absence of a recommendation, or in the
absence of widespread implementations, non-standard markup may enhance the
use of a page by certain groups. In such situations, alternatives must be
generated (see the first statement

techniques:
An example is the use of a form which includes scripted validation after
each entry to optimise the form for server-side processing. Where the
script may not be executed, there must be some alternative, such as a
server-side validation, or tolerant processing of errors.

Another example is the use of an applet to generate a series of links
which replace each other. This could either be done by providing the same
links as alternative content to the applet object, or by using SMIL to
allow the production of an accessible version, or by providing a text-only
version.

Charles McCN
--Charles McCathieNevile            mailto:charles@w3.org
phone: +1 617 258 0992   http://purl.oclc.org/net/charles
W3C Web Accessibility Initiative    http://www.w3.org/WAI
MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA

Received on Monday, 22 February 1999 17:34:46 UTC