You've got an interesting point, Steve. Transitioning from non-accessible websites to accessible websites seems like it would require some sacrifice in look and feel. In fact, I was prone to thinking the same thing, but check out http://www.zeldman.com. You see that he's using images in the navigation, but when you disabled the styles these turn into text links. I haven't ever used this technique, but doesn't that achieve what you're talking about?
Even if this whole text link with CSS images is too complex, it seems like the web is going away from graphical representations of text in general. What you lose in graphics, you gain back in SEO and accessibility - that's an easy way to pitch it to a client. Besides, CSS can do some stunning things with text. A good example is http://www.particletree.com - the only images on that page are with a specific purpose, and not to replace text. Also, I'd question you in saying that continuous movement, audio that loads automatically, and "whizzy stuff" is enhancing to the user experience. Honestly, I'm more prone to turn off a site with these features, especially the audio that plays automatically - when you reload the site, it reloads the audio, and that's just annoying :) Have you gotten feedback that this is positive, or is it just what the client wants? -Tim www.timpalac.com On 8/14/07, Steve Green <[EMAIL PROTECTED]> wrote: > > I would like to agree with you Joe but I currently have a battle with > several design agencies who work for a multinational client of ours. > Historically they have produced websites that are predominantly > Flash-based > or sliced and diced from PhotoShop. Our client wants to achieve WCAG AA > and > the agencies are saying it will affect the visuals, which I can't disagree > with. > > Graphical representations of text are used throughout because virtually > all > the text is in fonts that browsers don't support and has visual effects > that > cannot be achieved using CSS (sIFR is not an option for this quantity of > text). The colour contrast is subtle (i.e. low). There is continuous > movement, audio that plays immediately on page loading and all kinds of > whizzy stuff. > > The overall effect is fantastic for most users but it simply isn't > possible > to achieve the level of accessibility the client wants without making > compromises. I so wish it was otherwise because this is a battle I don't > want to have. > > Steve > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Joseph Taylor > Sent: 14 August 2007 15:33 > To: wsg@webstandardsgroup.org > Subject: Re: [WSG] Usability & Accessibility Over Design? > > There's no reason to have to sacrifice on either end of the scale. > > Every document should start as a plain, accessible HTML document. If the > information on the document is well organized and logical, its already > usable. > > At this point, progressive enhancements on all ends can be used to > integrate > higher level interaction. Your first level of enhancements come in the > way > of the visual design, color choices, basic styles. > > The second level is where CSS is taken a step further and used to perform > image replacement, hide things, etc. > > The third level is where javascript manipulates objects in the document, > or > adds things in that are not part of the original HTML document, like flash > movies, etc... > > You can keep adding in this direction....making a page as rich and > interactive as you want. > > Usability...thats not guaranteed anymore than a good visual design, but it > is certainly a result of all things coming together with the same goal in > mind. > > Joseph R. B. Taylor > > Sites by Joe, LLC > http://sitesbyjoe.com > [EMAIL PROTECTED] > > > John Faulds wrote: > >> Web Standards, Accessibility and Usability needs to be put right at > >> the top of the list, way before design. > > > > I won't argue with that but all of those things are generally a harder > > sell to a client than the more superficial aspects of a project like > > the graphic design. > > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
