Working with legacy websites

This is a task which comes up over and over again for many developers. There are a lot of jobs in maintaining web sites. Our work doesn’t always come with the dream experience of a brand-new web site. Even if a new web site is a major goal, there will inevitably be large quantities of legacy content which will need to be worked into the new accessible design. Working on legacy websites can pose a number of subtle challenges. If […]

Continue reading “Working with legacy websites” »

Why not tables? Is CSS really better?

At Cre8asite Forums this week, a lengthy discussion on the ultimate value of pure CSS (Cascading Style Sheets) based layout over the use of tables has been taking place. Sometimes, living in the sheltered world of accessible and standards-based design, I can lose touch with the fact that many people out there simply don’t accept some of the same guidelines I work with every day — and that this does not, in any way, mean that they haven’t given the […]

Continue reading “Why not tables? Is CSS really better?” »

The Pains of Physical Accessibility

Thursday night last week, I attended a musical theater production. It was a production which was being provided with audio description, American Sign Language interpretation, and captioning. Obviously, the goals were to provide an all around accessible experience of this production. And these things were all well done: the audio description was clear and simple. It neither interfered with the production nor gave any kind of bias to the actions of the characters. Although I don’t personally know ASL, the […]

Continue reading “The Pains of Physical Accessibility” »

Pseudo-Accessibility: Reinventing the Wheel

In my last post, Accessibility and Client Expectations, a major point was on the practice of implementing accessibility as a site “add-on,” rather than developing a web site from the ground up with accessibility in mind. Some of the features which are implemented in this manner fall into a gross category I’m inclined to describe as “pseudo-accessibility.” In general, pseudo-accessible features are those which: Solve the symptom, not the problem. Create additional accessibility problems in their implementation Reinvent the wheel […]

Continue reading “Pseudo-Accessibility: Reinventing the Wheel” »

Accessibility and Client Expectations: Selling Accessibility

One routine challenge in being an accessible web developer is convincing clients of the necessity of certain features you’ve implemented. I don’t sell my services specifically on the grounds of accessibility; accessibility is simply a feature of my web sites. As a result, not every client is even aware when the project starts that they’re going to end up with an accessible web site. I don’t make an issue of it. I just make it happen. However, this does frequently […]

Continue reading “Accessibility and Client Expectations: Selling Accessibility” »