Return to Answer

Other items to consider:

• Place JavaScript at the bottom (before the closing body tag).
• Find other ways to avoid the flash of unstyled content.
• Avoid hard-coding text (e.g., "DeepFlow", "System") with an eye to internationalization.
• Use CSS to change layout, not multiple <br /> tags.
• Leave "style='display:none'" in CSS; change the class instead.
• Accessibility and its corresponding mark-up.
• Use tools like JSLint, CSSLint, in addition to the W3C validation tool.
• Good use of unique id attributes.
• Wrap input fields with label elements when possible; this allows users to click the label associated with the input field to give that field focus.
• "logo" should probably be "Qosmos Logo".
• Technically, you don't need © and the word Copyright.
• Add a body tag to help ensure consistency across all browsers.

Other items to consider:

• Place JavaScript at the bottom (before the closing body tag).
• Find other ways to avoid the flash of unstyled content.
• Avoid hard-coding text (e.g., "DeepFlow", "System") with an eye to internationalization.
• Use CSS to change layout, not multiple <br /> tags.
• Leave "style='display:none'" in CSS; change the class instead.
• Accessibility and its corresponding mark-up.
• Use tools like JSLint, CSSLint, in addition to the W3C validation tool.
• Good use of unique id attributes.
• Wrap input fields with label elements when possible; this allows users to click the label associated with the input field to give that field focus.
• "logo" should probably be "Qosmos Logo".
• Technically, you don't need © and the word Copyright.
• Add a body tag to help ensure consistency across all browsers.

Other items to consider:

• Place JavaScript at the bottom (before the closing body tag).
• Find other ways to avoid the flash of unstyled content.
• Avoid hard-coding text (e.g., "DeepFlow", "System") with an eye to internationalization.
• Use CSS to change layout, not multiple <br /> tags.
• Leave "style='display:none'" in CSS; change the class instead.
• Accessibility and its corresponding mark-up.
• Use tools like JSLint, CSSLint, in addition to the W3C validation tool.
• Good use of unique id attributes.
• Wrap input fields with label elements when possible; this allows users to click the label associated with the input field to give that field focus.
• "logo" should probably be "Qosmos Logo".
• Technically, you don't need © and the word Copyright.
• Add a body tag to help ensure consistency across all browsers.
• Provide more information in the DOCTYPE tag to ensure more predictable cross-browser behaviour.

Other items to consider:

• Place JavaScript at the bottom (before the closing body tag).
• Find other ways to avoid the flash of unstyled content.
• Avoid hard-coding text (e.g., "DeepFlow", "System") with an eye to internationalization.
• Use CSS to change layout, not multiple <br /> tags.
• Leave "style='display:none'" in CSS; change the class instead.
• Accessibility and its corresponding mark-up.
• Use tools like JSLint, CSSLint, in addition to the W3C validation tool.
• Good use of unique id attributes.
• Wrap input fields with label elements when possible; this allows users to click the label associated with the input field to give that field focus.
• "logo" should probably be "Qosmos Logo".
• Technically, you don't need © and the word Copyright.
• Add a body tag to help ensure consistency across all browsers.

Other items to consider:

• Place JavaScript at the bottom (before the closing body tag).
• Find other ways to avoid the flash of unstyled content.
• Avoid hard-coding text (e.g., "DeepFlow", "System") with an eye to internationalization.
• Use CSS to change layout, not multiple <br /> tags.
• Leave "style='display:none'" in CSS; change the class instead.
• Accessibility and its corresponding mark-up.
• Use tools like JSLint, CSSLint, in addition to the W3C validation tool.
• Good use of unique id attributes.
• Wrap input fields with label elements when possible; this allows users to click the label associated with the input field to give that field focus.
• "logo" should probably be "Qosmos Logo".
• Technically, you don't need © and the word Copyright.

Other items to consider:

• Place JavaScript at the bottom (before the closing body tag).
• Find other ways to avoid the flash of unstyled content.
• Avoid hard-coding text (e.g., "DeepFlow", "System") with an eye to internationalization.
• Use CSS to change layout, not multiple <br /> tags.
• Leave "style='display:none'" in CSS; change the class instead.
• Accessibility and its corresponding mark-up.
• Use tools like JSLint, CSSLint, in addition to the W3C validation tool.
• Good use of unique id attributes.
• Wrap input fields with label elements when possible; this allows users to click the label associated with the input field to give that field focus.
• "logo" should probably be "Qosmos Logo".
• Technically, you don't need © and the word Copyright.
• Add a body tag to help ensure consistency across all browsers.
• Provide more information in the DOCTYPE tag to ensure more predictable cross-browser behaviour.