1. Project Overview

The purpose of this contest is update LFMS website to be compatible with IBM W3 Designs and Standards.

2. Competition Task Overview

We need to convert this to V17 format. It consists of the WebContent/userguide directory. We are deleting the userguide.html.

So all we need to modify for this is: userguide.jsp

This assembly should update this page to V17 standard directly, we don't have V17 UI prototype for this page but we have many other V17 pages of this project for reference.

Under the Table maintenance section of the help text, there is a table of table names. This table should be converted to a ul bullet list.

Notes:

For V17
Site Secured link is to be removed.

3. Specific HTML/CSS/Javascript Requirements

HTML/CSS Requirements:

• ***** Fields should not be using class="ibm-styled" ***** 
• ***** Forms should not be using class="ibm-styled-form" ***** 
• We should only use the w3.css (no other external css files), if it can't meet the requirement, you can use inline css but it must be reviewed and checked as we have to use it at a minimum.
• Remove calls in code to lfms*.css files.
• Update all the application web pages with the latest look and feel of  IBM W3 V17 web standards. All elements on the pages should be following the IBM W3 V17 web standards put forth by IBM. Pages should also follow the WAI-ARIA accessibility standard. IBM follows IBM Accessibility checklist version 5.2. Misc, Browser,  HTML authoring, and other ST&G standards would be followed. Created pages should be tested by the latest browsers: Firefox 17 ESR, IE 8 & above, and Chrome, as well as using Freedom Scientific JAWS version 12 or above (using Firefox and IE).  Firefox 17 ESR can be downloaded at: http://www.mozilla.org/en-US/firefox/organizations/all.html
• Your HTML code must be XHTML 1.0 Transitional compliant
• Validate your code - reviewers may accept minor validation errors, but please comment your reason for any validation errors. Use the validators listed in the scorecard.
• Use CSS to space out objects, not clear/transparent images (GIFs or PNGs) and use proper structural CSS to lay out your page. Only use table tags for tables of data/information and not for page layout.
• Use semantically correct tags - use H tags for headers, etc. Use strong and em tags instead of bold and italic tags.
• Element and Attribute names should be in lowercase and use a "-" or camel naming to separate multiple-word classes (i.e.. "main-content", or "mainContent
• Label all CSS, Javascript, or HTML hacks with explanations so others will understand.
• Your code must render properly in all browsers listed in the scorecard in both Mac and PC environments.

Final Submission Guidelines

• Source Code
• Deployment Guide