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

Re: Evaluation results: Priorities

From: Chetz Colwell <c.g.colwell@herts.ac.uk>
Date: Tue, 16 Mar 1999 10:26:39 +0000
Message-Id: <v01540b05b313301678af@[]>
To: Charles McCathieNevile <charles@w3.org>, w3c-wai-gl@w3.org
CMN:: = Charles McCathieNevile's comments, my comments = CC::

>This is a tricky problem. If we remove P1 from things which are not
>supported by browsers x,y and z (where x,y, and z are an ever-changing and
>personal set, then we are compromising what is supposed to happen.

I don't think I was suggesting that the P1 be removed, but that authors be
informed that what the Guidelines said they 'must' do may not be supported
yet.  I think there may be no harm in the Guidelines being more explicit
about the fact that some elements / attributes are not yet supported and it
is not possible to predict if or when user agents will support them.

>One of the challenges we face is getting people to understand that the
>purpose of following these guidelines is that things they cannot see (or
>otherwise perceive...) with their browser may be crucial for people who
>are using a different browser.

Could the Guidelines state this more clearly in the introduction where
browser support is mentioned?

From the Guidelines: "The current document and the Techniques Document
refer to some technologies (e.g., features of >HTML, CSS, or SMIL) that may
not be supported yet in some browsers, multimedia tools, etc." ...

[insert here]
Authors should also note that some of these technologies may not be
supported by all browsers.  However, browsers that do not support such
technologies will not be adversly affected by their use.  [or words to this
... "Browser support for language features is discussed in the Techniques

Received on Tuesday, 16 March 1999 05:25:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:29 UTC