Email conversation
| From | Roland Hentschel |
|---|
| To | Me |
|---|
| Subject | a menu-script |
|---|
| Date | 13 November 2007 16:10 |
|---|
| Attachment | zip file containing images, fonts, PHP, and JavaScript |
|---|
hi,
since your site was one of those helping me the most
in several cases, here is a little something in return :-)
my menu is special in so far, as it's using php to create
images from text with true-type-fonts dynamically,
and as for functionality it offers more than most of the
other scripts, that i found during my (extensive) researches.
plus: it's not using large libraries, but a pretty slim code.
it's certainly optimizable, but for now i'm really happy
with it; may be you could trun it into a list-based menu?
( -: roland :- )
| From | Me |
|---|
| To | Roland Hentschel |
|---|
| Subject | Re: a menu-script |
|---|
| Date | 18 November 2007 08:48 |
|---|
Roland,
Thanks for the gesture.
> my menu is special in so far, as it's using php to create
> images from text
I am interested to know about the accessibility aspects of this script. It
seems to rely very heavily on images and JavaScript. What happens if the
user has images disabled (say for example that they use a screen reader, or
a slow connection)? What happens if the user has JavaScript disabled? Can
they still select the text (required for a lot of screen reader software)?
Basically, I find that images used to replace text is almost never a good
idea. I understand some designers demand precise fonts and font stylings,
and I assume that is what this script is for. However, from an accessibility
standpoint, I feel it is better to ignore the designer, and make the page
properly with regular text in semantic HTML, and style it with CSS to make
it pleasing (this can, in most cases, be done in a way the designer can be
made to appreciate). That way it also falls back better, and remains
accessible.
Mark 'Tarquin' Wilton-Jones - author of http://www.howtocreate.co.uk/