Hello everyone,

We had a discussion in our local UI/UX user group, I'd like to reduce
that discussion to a single question and put it to the css-d mailing
list in that modified form - to make it more on-topic. At root of the
issue: how to preserve the intent of the designer while keeping the
page accessible to everyone.

We experimented with some different font replacement technologies
for reproduction of column header text that the designer wanted
to use fancy fonts (images) for.

The CSSPlay, sIFR and FLIR methods of font replacement were tested.
I did my own testing with each of those methods and they yielded
less than satisfactory results, so I wanted to ask the list about
best practices with font-replacement technologies like those and see
where everyone else stood on them.

Not to start a religious war or feed the flames of one, but see
Allsopp(1) on the use of.

So if there is something else out there, something that does not
rely on sometimes blocked (javascript, Flash, etc.), sometimes
inaccessible (JAWS, etc.) technologies so that it defeats both
Allsopp's and my own arguments? I'd like to hear about it.

Reese

1- http://webstandardsgroup.org/features/john-allsopp.cfm#image-replacement

______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to