WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Code Validation (was RE: spacing -  versus clear images)

for

From: ben morrison
Date: Mar 8, 2006 9:20AM

On 3/8/06, John Foliot - WATS.ca < <EMAIL REMOVED> > wrote:
> >
> > We're talking about accessibility first and foremost. Standards
> > based development is a complementary topic, but doesn't fully overlap
> > with accessibility.
>
> True, but we are also, in a very broad term, talking about technology as
> well. How can you justify "hacks" or equivalent that "work" now, but
> may not work later? This is a bad development position at any time, in
> any technology, especially as it scales out to larger and larger
> initiatives. Developing to Standards ensures that your content "works"
> now and into the future, as it is based upon published Standards. By
> their nature, Standards remain in effect, even if they fall from favor
> or are superceded by newer technologies in the future. Non-Standard
> constructs, on the other hand, may simply cease to be supported. This
> can create a very real access problem for all users, not just those with
> special needs.

Im in agreement with both of you, firstly I think standards are very
important and its the only way the web can improve from its awkard
beginnings - think browser wars/hacks and work forwards into the
future.

Although, as we know we need to be pragmatic about it - as the
longstanding accesskey/tabindex issues have shown.

I suppose the difference here is that we follow best practices and no
we should not be using <spacer>.

Ben