| ZVON > References > WCAG 1.0 |
| Intro / Search / ZVON |
| Previous | Next | Guidelines | Priorities |
Use W3C technologies (according to specification) and follow accessibility guidelines. Where it is not possible to use a W3C technology, or doing so results in material that does not transform gracefully, provide an alternative version of the content that is accessible.
The current guidelines recommend W3C technologies (e.g., HTML, CSS, etc.) for several reasons:
Many non-W3C formats (e.g., PDF, Shockwave, etc.) require viewing with either plug-ins or stand-alone applications. Often, these formats cannot be viewed or navigated with standard user agents (including assistive technologies). Avoiding non-W3C and non-standard features (proprietary elements, attributes, properties, and extensions) will tend to make pages more accessible to more people using a wider variety of hardware and software. When inaccessible technologies (proprietary or not) must be used, equivalent accessible pages must be provided.
Even when W3C technologies are used, they must be used in accordance with accessibility guidelines. When using new technologies, ensure that they transform gracefully (Refer also to guideline 6.).
| 11.1 | Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [Priority: 2] |
|---|---|
| 11.2 | Avoid deprecated features of W3C technologies. [Priority: 2]
|
| 11.3 | Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) [Priority: 3] |
| 11.4 | If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. [Priority: 1] |