WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Bridge page wording

for

From: Christian Heilmann
Date: Jun 23, 2005 9:54AM

> > We have a client that has a Flash version and an HTML version of the
> > same site. The Flash version will be by its very nature not accessible
> > to all (marketing speak, games, loads of moving sliding and bouncing
> > bits) and is not meant to be. Both versions have the same data, and
> > get generated from one source. As it stands now, they automatically
> > send Flash users to the singing and dancing version, which is clearly
> > a bad idea. I proposed a bridge page to let the visitor choose.
>
> How about just a discrete "View non-flash version" (or something a bit sexier
> and less techie sounding) and matching "View flash version" on those pages.

Well, the problem is that the client will not spend any money on flash
accessibility, therefore they wanted to ensure that the HTML version
is advertised to the user as the "accessible" one.
As you rightfully answered beforehand, it is not a matter of being
lazy, crap or bad Flash developers, it is a matter of budget and
buy-in from the client. The flash is created dynamically via Turbine,
too, so there are not as many options to make the flash acccessible as
you have with hand-developed fFash.

> Also, you could possibly pipe those links through an additional bit of
> script that sets a cookie, so if the user chose to click through to the
> non-flash version, the browser remembers it next time (similar to what
> you obviously want to implement, but without necessarily asking the user,
> but simply taking a cue from their choice).

That was a part of the text, there will be a "remember my choice"
checkbox, so that next time the same visitor arrives there is no
bridge page any longer.

Cheers

Chris (btw, where is the picture you shot of me at the @media
pissup^H^H^H^H^H^H^H networking party?)

--
Chris Heilmann
Blog: http://www.wait-till-i.com
Writing: http://icant.co.uk/
Binaries: http://www.onlinetools.org/