- Do not expect to find one solution that will provide accessibility
for all users. For example, as has been shown in relation to specific
disabilities, 'text-only' and 'accessible' are NOT synonymous.
- When designing pages use a fluid design which
allows the page to flow into the users screen device or window
size.
- When developing web applications, acknowledge
where aspects of your applications will present accessibility
barriers and make alternative provision where you can (e.g. by
using 'alt', 'longdesc', 'noframes' or 'noscript'). Accessibility
should not itself become a barrier to web development.
- When writing pages ensure that your code is
'valid' (complies with W3C standards that a range of browsers
recognise). You can use code validators provided by the W3C to
check this.
The approach outlined above focuses on design for all. This principle
also underlies the internationally recognised design and coding
standards developed by the W3C. Conformance with these standards,
embodied in the Web Accessibility Initiatives Web Content Accessibility
Guidelines, is currently considered the most reliable way to ensure
your site's accessibility.
< Previous - home - Next >
|
