|
|
Standards Manual Template Jan Willard Page last revised: 08/10/01
|
Level 3 Page
Required Topics for Initial Submission of Standards Manual:
On LEVEL (3) the links are internal such as thumbnail to full-size images.
Full-size images viewed by clicking on the ALT description to the thumbnail still appear in the
confines of the frameset, keeping the user on the site. This is the advantage
of using frames for navigation.
By continued use of frames, navigation and consistency are maintained.
All images, regardless of size shall have a header and a footer included with the image.
This can be accomplished by use of Server Side Includes (SSI) wherever possible.
This will be maintained in any level. If the user is taken out of the site as in
an external link, this will be done in a new window. This allows the user to cancel
the new window and come back into the frameset.
[-07/27/01-] revised
Searching and finding Information
Navigation for accessibility shall be addressed at this level by using consistent content
and links that work from wherever one is located. From LEVEL (0) to LEVEL (3) shall
provide the user with the same feel as if he/she was within the site. This will help
improve the overall appearance and consistency within the site. Easily displayed at
LEVEL (1) is the Search Engine at the top of the main
page, clearly visible. A user can always return home to use the search utility
and either search, within the site, or external to the entire web. On a consistent
basis the web site is submitted to the search engine server that maintains the index and
listings of all the URL's that are contained within a database on that server. As
pages are added, the web site is spider ed by the search engine and re-indexed to provide
an update on the lastest listings.&bnsp; The site map is located at LEVEL (1) and is
updated each time new pages are added to the site.
Extensive use of graphics in LEVEL (3) will be used to further justify the subject matter
where necessary. The use of audio will be allowed on this level.
At LEVEL (3), pages will not be allowed extend past the viewing window. There will
be instances where double width columns will be used but only within tables to provide
consistency in browsers. There will be no three column wide columns at this level.
As stated in LEVEL (1) and LEVEL (2), all images shall have ALT keys with descriptions of the image, not just "Click Here".
The entire site shall work with Netscape Navigator 4.5,4.7 + and Internet Explorer 5.0 +
versions. As time permits other certifications for the disabled will be examined for possible
implementation on this site. This shall follow the same consistency as all the above LEVEL (0,1,2).
Consistency is very important, since it establishes trust with the user and predictability.
[-07/27/01] revised
Disabled Users
At LEVEL (3), navigation will allow the user to view large images behind thumbnail images
on LEVEL (2). The full size image shall have ALT tags displaying the full size
for textual content.
By using Server Side Includes (SSI), the use of header and footer snippets will be included
to provide consistency and style in pages and images.
Required Topics after initial submission (with due dates
announced in class and in syllabus): (Please use the same numbering
scheme in your template. Keep the text that is below and fill in
your information below each numbered item. If/when you add additional
items, see below for format.)
All images on LEVEL (3) and image maps will provide text equivalent descriptions about content of the images. Cascading Style Sheets (CSS) shall be used consistently throughout the site to provide speed of downloading, structure and ease of readability. This will be an ongoing project due to the large amount of images used on LEVELS (1,2,3). All pages including new pages will be tested with older versions of Netscape(3) IE4.5 +, and current published versions for compatibility and meeting requirements of older browsers, screen size and resolution. Text must be visible if CSS does not work on older browsers. Colors and background combinations must be compatible if someone who has color deficiencies, hence, using safe browser colors and combinations of colors. Site should be readable and clear if viewed in black and white, while still being accessible.
StructureThe structure of LEVEL (3) pages These pages are accessed from LEVEL (2) pages. The LEVEL (3) pages are styled using CSS and provide consistency and format on the entire level regardless of the subject matter. The LEVEL (3) pages are normally full size images of thumbnail images. Some examples are the various models of steam engines such as Bowser, Rivarossis, and Mantua. These LEVEL (3) pages then may point to larger full size images. Other examples are the Kits Gallery, and the forms.html pages for the design services page. |
[-08/04/01-] revised Coding IssuesTo verify that all coding is working correctly to LEVEL (3) and back to any other LEVEL (0,1,& 2) must be validated. I use the web site Search utility on a weekly basis to check any changes in my code as far as links are concerned. The report generated sweeps the entire site and produces a report that identifies which links are not working. This has to be corrected immediately. Secondly within the code, is the issue of consistency in using headers and footers with SSI. All files that are using SSI are saved as *.shtml files. These are stored in the same root directory as the *.html files. The editor HOMESITE by Altaire is used as the primary editor. After a page is finished, the code is validated against the HOMESITE code analyzer for infractions in HTML XHTML, javaScript, ASP and SSL. A style of coding is necessary for continuity for the next designer that might follow behind and have to fix something. Currently, all code is hand-written without the use of external automatic code generators. When testing a new page, it is always best to check it first in Netscape, then Internet Explorer. I test with 3 version of Netscape, version 3.0, 4.7 and 6.0. as well as multiple versions of IE. |
Documentation, Rules, and CollaborationWhen developing web pages, it is necessary to document when using nesting multiple tags, where various tables, forms, and html tags start and end. If a change is made in an HTML page, the date of the change will be noted to reflect the last time a change was made. This is separate from the SSI include statement that looks for a file that has changed since the last time and places that date on the *.shtml page. Comments are very important for remembering and helping some else who might have to modify your code sometime in the future. If something took considerable effort to implement the code, you should document only the essentials that would simply explain the coding. Indentation, and proper spacing are required as well as helpful in reading the code when there is a problem. Since HTML ignores white space, use it for something constructive. These rules are no different that writing software in any other language. If you borrow some code of any kind, it should be documented as to who the original author was, the date it was created, and that you modified the code on a specific date. Remember, anyone can read your code on the Internet. Anything that is not yours needs to be acknowledged and properly documented. The rules for testing and implementing code follow the following requirements. : 1) All development code, forms, and images reside first on the test server, Polaris. There is a mirror image of what is currently on the test server at the Unix Polaris Server. All ideas are first developed on the test server, NT 2000, saved and then ftp to the polaris machine. The directory structure on Polaris is: /*.html ( All html code ) /images/ *.jpg, *.gif (majority of images keep here ) /images/roundhouse/ *.jpg (special image for a specific page ) /documents/ *.html (all documents that are referenced from the web site) The production server is first developed on the NT server in a directory called Hosteam. The actual web server is at Ho Steam Central in Virginia. The file and directory structure is: /*.html ( All html code ) /images/ *.jpg, *.gif (majority of images keep here ) /images/roundhouse/ *.jpg (special image for a specific page ) /documents/ *.html (all documents that are referenced from the web site) Anything that is on the production server must be checked with the various browsers on the Polaris Unix server first, then ported to the Production Server. |
Additional Topics: (To add an additional item, please use
a bullet list with the topic as the list item and your text following below.)
p{font-family: sans-serif; font-weight: 600; face="Veranda,Aerial,Helvetica,sans-serif"}
h1 {color: darkgrey; font-weight: bold; text-align: center;}
h2,{font-family: monoscope; font-style: italic; color: blue;}
h3,{font-family: monoscope; font-family; sans-serif; color: black;}
a {color: blue; font-weight: 600; font-style: italic;}
ul {list-style: square; font-family: sans-serif; color: black;}
li {color: red;}
address {color: aqua; text-align: center;}