[WEB4LIB] Re: Fonts & CSS

[Keith Higgs]

I have a very simplistic approach to this.  Knowing that non-CSS-capable
browsers will simply ignore the style information I allow the browser to
apply it's default font settings.  To do this I avoid use of the FONT
tag wherever possible.  Additionally, I make certain that all of the
tags I use, with all of their various classes, pseudo-classes, and IDs
are accounted for in the style sheet.

D. Keith Higgs <mailto:dkh2 at po.cwru.edu>
 Case Western Reserve University, Webmaster - University Library
 Additional Information at http://www.cwru.edu/UL/
"Follow the white rabbit."


-----Original Message-----
From: web4lib at webjunction.org [mailto:web4lib at webjunction.org]
On Behalf Of Russell Voigt
Sent: Wednesday, August 07, 2002 11:06 AM
To: Multiple recipients of list
Subject: [WEB4LIB] Re: Fonts & CSS


Hi All,

I have been directed to keep our pages accessible to as many browser
types as possible; we still have patrons using IE 2.0 and text browsers
that are not CSS compliant. To keep older and less-popular browsers
accessible I've stayed away from using CSS all together and still use
the font tag through HTML Styles in Dreamweaver MX. I'm also
implementing Active Server Pages because it does it's calculations on
the server then returns pure HTML to the browser.

I thought his solution was a good one because I'm using the lowest
common denominator - pure HTML. Has other library systems given up
completely on these browsers/patrons or is there another solution that
I'm not aware of?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Russell Voigt
Systems Analyst
Anne Arundel County Public Library 
www.aacpl.net
5 Harry S. Truman Parkway 
Annapolis, MD 21401 
V: 410-222-7371 
F: 410-222-7069

-----Original Message-----
From: 	Jeremy Foster [mailto:agjf1 at nsh.library.ns.ca] 
Sent:	Wednesday, August 07, 2002 10:29 AM
To:	Multiple recipients of list
Subject:	[WEB4LIB] Re: Fonts & CSS

Thank-you to everyone for their views on this.
Possibly I was reading this line wrong when I was going over guidelines:
"Note that conformance to this checkpoint is important even though
Priority 2 Checkpoints 3.1 and 3.3 suggest implementing a stylesheet.
Note that conformance to this checkpoint also may require you to violate
the Priority 2 Checkpoint 11.2 which advises avoiding old features such
as FONT." I am not trying to force fonts on anyone :-) just want to be
able to define a base font , that will work with most of our users and
still be accessable friendly. I had planned on using the H1 - H6 tags to
headline the sections but the problem with this is not all formatted
text needs to stand out so much if CSS is not supported. Once again
thank you for your input, I have the information I required.

Jeremy Foster
HRL Webmaster
-----------------------------------  
agjf1 at nsh.library.ns.ca
Tel: (902)490-5670
http://www.halifax.library.ns.ca
----------------------------------- 
Alderney Gate Library
60 Alderney Drive
Dartmouth, NS, B2Y 4P8          
-----------------------------------