NEXT: Introduction | BACK: Code for accessibility
You need to factor in sufficient time for testing and retesting your web site. This process involves:
As a general rule, people will only comment on features of a site that they find hard to use. Your design can be usable (in the broader context) but not accessible. However, in my experience, a site that is accessible is also usable.
If the main site is accessible it means less work maintaining alternative versions. In addition separating structure and content means that any changes to the appearance of the site can be changed once in the style sheet/s and this will then apply to the entire site. Accessible HTML code is very lean and clean, whereas deprecated code can be bulky making changes more time consuming.
I believe two things are important in maintaining a high level of accessibility on a web site once the initial development project is handed over.
Having an "accessibility champion" within the organisation, someone who will advocate for accessibility and usability, is an asset.
In addition, developing guidelines, checklists and policy for editing, updating and adding new content is an important part of managing accessibility and usability longer term.
Sandra Vassallo is the Managing Director of e-bility Pty Ltd. She provides consultancy services to organisations and Government agencies, including web site accessibility / usability evaluations, training and web site design.
Google links
End of Google links
NEXT: Introduction | BACK: Code for accessibility