Visually to my opinion and taste is very-very beautiful and pleasing.
I checked the home page and found following problems:
HTML & CSS Markup
Line 13? <table width="780" border="0" align="center" cellpadding="0" cellspacing="0">.
This table doesn't appear to have the same number of cells in each of its 3 rows. Number of cells in each row, starting with the first row: 1, 3, 3. Note that for the purposes of this message, a table cell with a "colspan" or "rowspan" value greater than 1 is considered to be multiple cells.
Line 15? <table width="780" border="0" align="center" cellpadding="0" cellspacing="0">
This table doesn't appear to have the same number of cells in each of its 2 rows. Number of cells in each row, starting with the first row: 2, 3. Note that for the purposes of this message, a table cell with a "colspan" or "rowspan" value greater than 1 is considered to be multiple cells.
Line 141: <td colspan="3" align="left"><table width="100%" border="0" cellspacing="0" cellpadding="0">
This table contains 2 "tr" tags but has 3 rows. Something is wrong with the table structure. Perhaps "rowspan" has been used to specify more rows than there are "tr" tags, so please check your "rowspan" attributes.
And this table doesn't appear to have the same number of cells in each of its 3 rows. Number of cells in each row, starting with the first row: 3, 3, 1. Note that for the purposes of this message, a table cell with a "colspan" or "rowspan" value greater than 1 is considered to be multiple cells.
Line 73? “How does LifeStation Medical Alert works”
Replace invalid character code!
CSS Style sheets code is incorrect:
Line: 326: .padleft
See:
http://jigsaw.w3.org/css-validator/v...usermedium=all
Accessibility:
1. Section 508 The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also using the "longdesc" attribute to specify the URI to an extended description of the image. [Section 1194.22 (a)]
Also according to W3C/WAI you must provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. [Priority 1]
2. Style sheets should be used to control layout and presentation [P2, 3.3]. The element you've used ("u") is a presentational element. Presentational elements include "font", "b", "i", "big", "small", and others. For presentation, consider using style sheets (CSS) instead. Use HTML elements only for content and structure and not for layout and presentation. Use the "em" and "strong" elements for structural emphasis.
3. Line 17, 24? Adjacent links should include non-link, printable characters (surrounded by spaces) between them [P3, 10.5]. Do not place two links next to each other without non-linked, printable characters between them because the two links may be rendered as a single link in some user agents.
4. Line 80? <td height="5"></td>
Use relative rather than absolute units in markup language attribute values and style sheet property values. [Checkpoint 3.4 / Priority 2]
Tables and Table Cells with attributes like " heigth and width " are highlighted. Verify that the values for those attributes are expressed in percentages, not in absolute measures.
5. Line 143? <td height="4" colspan="2"></td>
Use relative rather than absolute units in markup language attribute values and style sheet property values. [Checkpoint 3.4 / Priority 2]
Tables and Table Cells with attributes like " heigth and width " are highlighted. Verify that the values for those attributes are expressed in percentages, not in absolute measures.
6. Headers (h1-h6): No headers are used.
Use header elements to convey document structure and use them according to specification. [Checkpoint 3.5 / Priority 2]
It should exist at least one main title and levels should not be aleatorily mix because of the different font sizes.
7. a. Obsolete elements: 3 obsolete HTML tags used.
Elements considered in disuse in HTML 4.01.
b. Obsolete Attributes: 39 obsolete attributes in HTML 4.01 are used.
Elements considered in disuse in HTML 4.01 are used.
Avoid deprecated features of W3C technologies. [Checkpoint 11.2 / Priority 2]
8. Blocks of information: It doesn't exists any header nor paragraph or lists that allow to create a minimal structure of the page. Divide large blocks of information into more manageable groups where natural and appropriate. [Checkpoint 12.3 / Priority 2]
The too long blocks of information difficult their understanding, especially to some people with cognitivas deficiencies. For this reason and for simple logic, it's preferable to structure the documents by creating appropriate blocks of information, by means of the markup of paragraph, lists, titles and subtitles, etc.
9. Document main language is not indicated.
Identify the primary natural language of a document. [Checkpoint 4.3 / Priority 3].
<html> tag is identified. Verify if the main language of the document is indicated through the " lang " attribute. If the document is XHTML , it should be verified that xml:lang= is also used.
10. No keyboard shortcuts provided.
Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. [Checkpoint 9.5 / Priority 3]
11. Adjacent links: There are 2 cases of adjacent linkage that do not contain printable characters not connected between them.
Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. [Priority 3]
12. Consider using a "summary" attribute with this "table" tag to provide a summary of the entire table's purpose and structure for user agents rendering to non-visual media such as speech and braille. Note that this attribute may not be widely supported and that the summary text is not displayed on the screen. This is the last time that this message will be generated. There may be other tables without "summary" attributes. [Checkpoint 10.5, Priority 3]
13. Avoid using white backround color. Better use colors as: #fafafa or #fdfcfc.
Usability
1. Accessibility is important for Usability.
2. Don't underline texts if they are not links, as done here:
24 hours a day, 7 days a week.
For such cases, you can emphasize texts with the tag [i]. This is also important for accessibility.
About
SEO, I will have a look later. I must go to bed now.
I hope all above helps.