Accessible Web Design - PAGE 4

The current situation

"Computers can figure out all kinds of problems, except the things in the world that just don't add up."

Following is a list of accessibility issues that are common today:

• excessive download times of bulky code and poorly compressed images (see image slicing example on page 3).
• use of PDF downloads with no alternative access. A good idea here is to include a phone number so people can request a file type that is useful to them.
• no allowance for customized browser preferences (for example, using pixel sized text rather than relative sized text).
• tables used inappropriately to force layout
• incorrect code used for constructing forms
• italic text that is too small
• multiple pop-up boxes
• use of plugins and scripts whereby the user has no ulterior means of access
• unnecessary and poorly maintained text-only versions (most people who need them have learned to avoid them)
• image-based navigation with no text alternatives. See the example below:

While the text in this image may look fancier than html text, this email link would be completely innaccessible for someone with images turned off. Even with images enabled, this text cannot be copied or read by screen readers.

• poor coding (most browsers will compensate but assistive technology is not so forgiving)
• overall problems with usability and navigation (inconsistent and poorly designed architecture)
• html authoring software doesn't encourage compliance to guidelines and standards. Still requires extra work to conform. Many employers don't see this as important to their business principals.

The following link contains further information on working around limitations and selecting web authoring tools.

For authoring tool reviews, see Authoring Tool Conformance Evaluations.

TOP

Current developments in favour of web accessibility

The following languages and formats are having a positive impact on web accessibility:

• XHTML (Extensible HyperText Markup Language). Requires higher degree of coding rigor. This is an interface language.
• XML (Extensible Markup Language). Separates content from presentation.
• SVG (Scalable Vector Graphics). In Australia, CSIRO are the leaders in SVG development.
• SMIL (Synchronized Multimedia Language). Currently allows transitions for Quicktime and real media.
• Browsers are being developed with a higher awareness of accessiblity
• Authoring tools. Authoring tools are also being developed with accessibility issues in mind. An accessible content management system should address 3 core issues:

1. allow you to output accessible content (e.g. ALT tags)
2. encourage you to make content accessible (not just a 'hidden feature')
3. the tool itself must be accessible to use and be compatible with other tools

TOP

go to page 5 of 7