Accessiforum & XHTML Mime Types
At the moment, most people just offer larger fonts, which is underuse. But different colour combinations, different fonts, and different levels of contrast all affect readability.
Okay, I am using the XHTML 1.0 Strict DTD now, so do I need to include the XML directive for the CSS, or do I just use the LINK element? Or both? (Right now I'm using both and serving it as text/html MIME type, so I think I'm supposed to use LINK exclusively, correct?)
I've updated it, by the way. I know the "new" logo sucks eggs, but other than that tell me what you guys think about what I've done to it, lol. I did the navigation menu in EM's as TOOLman suggested, but in IE with a larger text size it overlaps the content division, although it does keep the text inside of the division block. Should I do the same for the content division to prevent this?
|Did you see Minz Meyer's demonstration of style-switching with the PI?|
I did now.
Actually, I'm using that principle myself in my eventually-to-be-launched redesign. There's a common, persistent style sheet; one preferred (set in PHP, based on cookies); and at least one alternate layout. Then there's an alternate style sheet for printing, of course (media="print").
I'm going to use the alternate style sheet for a completely different layout -- not just fonts. The initially preferred style is a kind-of 3-column thing with dark-on-light text. The alternate style will use tabs and a kind-of 2-column layout, with another color scheme altogether. The alternate laout will probably work better on small displays, since the navigation won't occupy an entire column.
Of course, I'll use <link/> when serving documents as text/html (to inferior browsers). I'll even put the IE hacks in a separate style sheet and use a conditional comment for it.
|Okay, I am using the XHTML 1.0 Strict DTD now, so do I need to include the XML directive for the CSS, or do I just use the LINK element? Or both?|
If you're serving the documents as text/html, use <link/>. If you're doing content negotiation in PHP, use PIs (only) when serving as application/xhtml+xml.
Tommy has left the building
|Okay, I am using the XHTML 1.0 Strict DTD now, so do I need to include the XML directive for the CSS, or do I just use the LINK element? Or both? (Right now I'm using both and serving it as text/html MIME type, so I think I'm supposed to use LINK exclusively, correct?)
Personally, I'd stick with using <link>.
Later, if you do decide to serve pages as application/xhtml+xml, you could associate the stylesheet with the XML PI for pages served like that. I haven't done it, but I'm told another line or two changed in the header should be simple enough.
If you have a look in the comments for that link I gave earlier, you'll see that Ben de Groot gives a link to show how he does it.
Okay thanks, guys, that made a world of difference. Wow, I never knew there was so much to learn about headers! Anyway, can you guys tell me what you think of the new design, please? I really am going to chang the logo, I just need something more catchy for portability...
All times are GMT