|
 We have fine-tuned the content demonstration site to include suggestions received from faculty, staff, and students.
(Thanks to all who have provided guidance thus far on layout, design, and content. If you haven't participated in the past, please visit our committee Web site and join the public announcement mailing list. We'll be starting several new projects and always appreciate comments and feedback.)
Screen comparisons
Barbara Knauff has graciously gathered a list of Dartmouth Web Developers (DWebD) who have volunteered to capture screen shots with particular OS/browser combinations.
We're looking for screen shots of the following three pages:
Here's what we're looking for:
- ~ 800 x 600 (approx.) including full browser window
- (Optional: ~ 1000 x 800 (approx.) including full browser window)
- JPEG compression at about 60%
- Meaningful file name: <OS-browser-date.jpg> such as <w0-e52-20030715.jpg> (see below)
File naming conventions
Operating systems
- l (Linux)
- m8, m9, m92, mx1, mx2 (Mac OS 8, 9, 9.22, 10.1, 10.2)
- w5, w8, w0, wx (Windows 95, 98, 2000, xp)
Browsers
- c07 (Camino 0.7)
- i2 (Icab 2)
- e51, e52, e55, e6 (Internet Explorer 5.1, 5.2, 5,5, 6)
- m12, m14 (Mozilla 1.2, 1.4)
- n4, n47, n7, n702, n71 (Netscape 4, 4.7, 7, 7.02, 7.1)
- o6, o601, o711 (Opera 6, 6.01, 7.11)
- s1 (Safari 1)
- w42 (OmniWeb 4.2)
- Screen reader software (please send text evaluation)
You may send these files, as attachments, to <mailto:jay.collier@dartmouth.edu>. Those received by Monday, 7/21/03, will be included in the final round of adjustments.
Code Evaluation
We've made a number of strategic decisions about the page coding for the new top-level pages as well as the new department-level template that will be applied to the department sites managed by Web Publishing Services.
If you'd like to suggest code changes, please send a complete copy of the HTML text file with your recommended changes surrounded by comments starting with your initials. This will allow us to find your suggestions easily!
- Although all content and links are available on pre-version-5 browsers, limited presentation formatting is applied on those browsers. This allows us to focus on consistent application of CSS styles across standards-based browsers.
- We're using tables to define the general page layout. This allows users of older browsers such as Netscape 4.7 (still used across campus) to see the overall page layout. It also allows us to apply CSS to portions of the page and avoid cascading inconsistencies in various generations of recent browsers.
- The fluid design ranges from 580 pixels wide up. The design is optimized for 640-900 pixel widths.
- We are using HTML 4.01 transitional as the document type in order to activate the appropriate rendering engines in version 5 browsers and to validate to World Wide Web Consortium standards.
- Although our CSS sheets validate, we are using a number of tricks to move toward consistent viewing across browsers that trigger user checks. (The one remaining unsolved problem is Apple Safari's small default font size when using ems as the font unit. We have determined that ems are the best font unit to use, and Apple has acknowledged this problem in version 1 of their browser.)
- We are using additional tags and attributes -- such as access keys, skip to main content, link separators, table summaries and search box content -- to support accessibility guidelines. Although these tags (some of which are hidden by the style sheets) slightly increase file size, they get us close to satisfying World Wide Web consortium standards.
- We've defined four keyboard shortcuts (ACCESSKEY) based on Sarah Horton's work on the Access Dartmouth site. Please keep in mind, however, that access keys don't work in all browsers.
<http://www.dartmouth.edu/home/about-site/shortcuts.html>
- Opinions regarding a customized style sheet for printing (available with some browsers and some printers) is divided right down the middle. Some want to be able to print the complete page design; others are asking for a black-and-white version with no background colors and a serif font. What do you think? (Currently the print sheet matches the main sheet until we've determined preferences.)
- Many comment tags are currently formatted for our prototype workflow with Adobe GoLive; these comments will change when we move into production.
|
