- From: Jason White <jasonw@ariel.ucs.unimelb.edu.au>
- Date: Fri, 20 Oct 2000 14:02:37 +1100 (EST)
- To: Web Content Accessibility Guidelines <w3c-wai-gl@w3.org>
Yet another alternative, distinct from those mentioned by Charles at the teleconference, would be to allow content developers to decide which technologies to support, on the basis of whatever considerations they think relevant, but subject to the condition that they may not use features or implementation strategies which are completely unsupported by adaptive technologies, user agents or access-related tools. Specifically, only what is completely unimplemented and has no support whatsoever in user agents, assistive technologies and access tools would be excluded by this criterion. The WCAG Techniques would document (1) which standard or specification, including the version number, each technique relies on; and (2) whether there is known to be an implementation of the relevant feature or features that would enable the technique to be applied in practice. Details of what software packages implement a given feature could also be supplied. Content designers would then be free to choose the extent of their support for backward compatibility, and when to adopt newer standards and technologies. Note: I am not necessarily supporting this position but merely explaining it for the purpose of having a range of alternative proposals available for consideration.
Received on Thursday, 19 October 2000 23:02:45 UTC