Main Points

Final Webpage Checklist

Checklist 1: Keyboard and Accessibility

  1. The webpage should be accessible with only a keyboard. (In IE, FF, O, and S)
  2. The webpage should function without apparent defects with CSS and Javascript off. (In IE, FF, O, and S)
  3. Links should work.
    1. If target page is missing -- Create a Holding Page.
    2. -- Add holdingLink class to the link.
  4. Link text should describe accurately where the link goes (What's the topic? What's the format?).
  5. Ideally, the first word of the link should be the topic. However, at least the first letter of the link should be the same as the first letter of the topic.
  6. The webpage should be spell checked.
  7. The webpage should be edited.
  8. The webpage should be linear for text browsers -- the webpage should make sense when starting from the beginning and reading straight through.
  9. The webpage should function without apparent defects with CSS off and Javascript on. (In IE, FF, O, and S)

Checklist 2: Code Checks

  1. The webpage should be properly commented. Espeically special features, code, or unusual syntax.
  2. All variables should be lowerCamelCase for consistency across the major languages and systems.
  3. All alt attributes for images should be descriptive or empty "".
  4. Pages which appear in PageSpecific.css should include their filename as a class in the <body> tag.

Checklist 3: Beauty Pass

  1. The webpage should function without apparent defects with CSS on and Javascript off. (In IE, FF, O, and S)
  2. The webpage design should demonstrate good user interface design. (In IE, FF, O, and S)
  3. The webpage design should be attractive. (In IE, FF, O, and S)
  4. The webpage should appear satisfactory in small or narrow browsers. (In IE, FF, O, and S)
  5. The webpage should list all authors and posting dates.
  6. The special features, if any, should work. (In IE, FF, O, and S)
  7. The webpage should function without apparent defects with CSS and Javascript on. (In IE, FF, O, and S)

Procedure 4: SEO Issues

  1. The webpage should have completed meta tags.
  2. Link text should include the golden keywords for the site.
  3. Link text, headings, content, etc. should include the golden keywords for this page.
  4. Link text should include the golden keywords for the target page.
  5. The subjects for the webpage should be decided.

Uploaded to Server Checks

  1. The webpages should validate on the W3C Validator. Correct all fixable problems.
  2. The links should work.
  3. The link text should match the target.
  4. Any special features should work.

Freeze Demo Pages for EC Beta Posting

  • Freeze CSS

    1. Save a copy of ec.css as *filename*.css.
    2. Paste sepia.css to the end of *filename*.css.
    3. (If relevant) Paste section of PageSpecific.css at the end of *filename*.css.
    4. Change page reference from Chroniclemaster.css to *filename*.css.

  • Freeze Includes

    1. Disable Include Statements (rendering Includes as comments).
      • Delete the # in "#Include"
    2. Insert a couple blanks lines and paste <!-- End of Include Code --> below.
    3. Paste Include code in between the comments.

  • Freeze Javascript

    1. Save a copy of earthchronicle.js as *filename*.js.
    2. Change page reference from earthchronicle.js to *filename*.js.
  • Save all files together in the same folder so they are all together in alphabetical listings.

[chroniclemaster1, 2007/07/10]

Additional Info

  1. Look for opportunities to boost SEO for the keywords History and Online Education. Educational and Resource are secondary keywords for the site in general. The topic of the page is of foremost importance, but don't forget these keywords as Any page is relevant to these keywords. Just don't forget about them, this is the fundamental goal or our site. Search engines won't know that however, if we frequently forget to include them.
  2. The first letter of link text should be the main subject. (It doesn't have to be the first word, though it is preferable. If a link goes to a page on "justice", link text that begins "just check out..." will still alphabetize acceptably.) The first letter of the link text has match the first letter of the topic as this is how JAWS skips through links when pressing a letter in links list.
  3. Alt attribute for all images. Those with alt text should be descriptive, yet clear and concise. e.g. alt="This is an image of the Washington Monument. Cherry trees bloom in the foreground as the obelisk reaches skyward." Images with no alt text value, or that you wish to hide from text browsers should have empty alt text. alt="" Don't use a space and don't omit the alt attribute. Text browsers (including Google bot) experience problems with images that have no alt attribute. However using a space alt=" " registers as a "space" and this is reported to users with text browsers. alt="" is the syntax text browsers best understand to mean that the image is not relevant to the user and should be skipped.
  4. All variable names (Javascript, VB, C#, as well as name="", class="", id="", and internal links href="#name") should be in lowerCamelCase. (e.g. finalWebpageChecklist, section1, aspNet20Development, del, mainPointsBoxout, etc.)
  5. If webpage includes entries in PageSpecific.css, add class="*filename*" to the <body> tag. ALL PageSpecific.css style rules should reference this class in the selector to reduce CSS accidents.
  6. Confirm that any editing is properly cited and dated (e.g. [chroniclemaster1, 2007/07/10])
  7. Check with a supervisor before changing Any filename for Any reason no matter how wonderful. This is the easiest way to break links.
  8. All links should go to a fully functional page, or a holding page. Check with a superviser in ANY case where you intend a third scenario.
  9. Add the holdingLink class to any link which goes to a holding page. As far as a visitor is concerned this is a broken link. No visitor should ever encounter a REAL broken link error, only a holding page.
  10. Apply to a Subject Specialist for the subject categories to your page. (Turn over page to Subject department for categorization? Who will do the actual Page coding, author, editor, or subject specialist?)

[chroniclemaster1, 2007/07/10]

Skip to Main Points