invertedpanda
01-21-2006, 08:19 PM
Ok, I know of a few different ways to approach coding this layout (well, the header), but I'd like some opinions/arguments from others to help me settle.
The first, and easiest, would be to just create a div with the header image as a background, and use css to define image-map style hotspots using anchor tags and absolute positioning.
The problems with this is it isn't too TTS reader/text based browser friendly (no alt tags). I don't have many visitors using those, but I myself use Lynx on occasion (I'm a Linux/BSD user). I believe I could probably put the necessary text in the anchor tags and just specify font size=0, but I'm not sure how well that would work.
The second would be to chop the header image into two parts and take out the menu text, and write the menu text in the HTML.
This would be the best bet for TTS readers/lynx users, but the overall quality of the typography would suffer (due to a lack of anti-aliasing in web fonts rendering in Windows; a good Linux browser will render it beautifully, however :)).
Another option would be to do the above idea, but chop the menu options out as image links with alt tags. While it would work, you have to then consider bandwidth overhead (from image headers), unless more consideration was given to compression (.gifs would work for the menu buttons).
Anyway, I'd like to hear some other opinions.
The first, and easiest, would be to just create a div with the header image as a background, and use css to define image-map style hotspots using anchor tags and absolute positioning.
The problems with this is it isn't too TTS reader/text based browser friendly (no alt tags). I don't have many visitors using those, but I myself use Lynx on occasion (I'm a Linux/BSD user). I believe I could probably put the necessary text in the anchor tags and just specify font size=0, but I'm not sure how well that would work.
The second would be to chop the header image into two parts and take out the menu text, and write the menu text in the HTML.
This would be the best bet for TTS readers/lynx users, but the overall quality of the typography would suffer (due to a lack of anti-aliasing in web fonts rendering in Windows; a good Linux browser will render it beautifully, however :)).
Another option would be to do the above idea, but chop the menu options out as image links with alt tags. While it would work, you have to then consider bandwidth overhead (from image headers), unless more consideration was given to compression (.gifs would work for the menu buttons).
Anyway, I'd like to hear some other opinions.