![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
| I would like to receive some constructive critique for this site in terms of proper browser rendering, layout, user interface & navigation, clear unambigious content, ease of use ... etc. http://www.big-discount-hosting.com |
#4
| |||
| |||
|
|
Tony Cortese <bigdiscounthosting@gmaildotcom> wrote: http://www.big-discount-hosting.com 100 errors, some severe. http://validator.w3.org/check?uri=ht....big-discount- hosting.com%2F FOR EXAMPLE: end tag for element "TR" which is not open <- SEVERE ERROR The visual design is every bit as bad due to the poor font choices and misspellings. You desperately need both a spellchecker and a page validator. |
#5
| |||
| |||
|
|
Tony Cortese <bigdiscounthosting@gmaildotcom> wrote: http://www.big-discount-hosting.com 100 errors, some severe. http://validator.w3.org/check?uri=ht....big-discount- hosting.com%2F FOR EXAMPLE: end tag for element "TR" which is not open <- SEVERE ERROR The visual design is every bit as bad due to the poor font choices and misspellings. |
#6
| |||
| |||
|
|
I am more interested in the user experience and what a human eye sees. I will fix the html stuff later. |
|
What's wrong with the font choices? |
#7
| |||
| |||
|
|
On Thu, 19 Aug 2004 10:45:38 -0700, Tony Cortese bigdiscounthosting@gmaildotcom> wrote: I am more interested in the user experience and what a human eye sees. I will fix the html stuff later. The "html stuff" affects what the user sees, hmm? Some of the errors can cause your site to fail for some users. Some reduce usability. Really, start there. There's no sense in painting a broken chair. Fix the chair first, then we make it pretty. Function before form. |
#8
| |||
| |||
|
|
On Thu, 19 Aug 2004 07:07:00 -0700, Tony Cortese bigdiscounthosting@gmaildotcom> wrote: I would like to receive some constructive critique for this site in terms of proper browser rendering, layout, user interface & navigation, clear unambigious content, ease of use ... etc. http://www.big-discount-hosting.com See http://validator.w3.org/check?uri=ht...hosting.com%2F . You need to fix 100 errors before anyone can meaningfully check your code. |
#9
| |||
| |||
|
|
On Thu, 19 Aug 2004 14:01:37 -0400, Neal <neal413 (AT) yahoo (DOT) com> wrote: On Thu, 19 Aug 2004 10:45:38 -0700, Tony Cortese bigdiscounthosting@gmaildotcom> wrote: I am more interested in the user experience and what a human eye sees. I will fix the html stuff later. The "html stuff" affects what the user sees, hmm? Some of the errors can cause your site to fail for some users. Some reduce usability. Really, start there. There's no sense in painting a broken chair. Fix the chair first, then we make it pretty. Function before form. I forget to add: you specifically requested advice on "proper browser rendering". Invalid HTML will cause rendering problems, so it's always wise to correct that first. |
#10
| |||
| |||
|
|
What you suggest is valid but I came across situations where a valid html caused the page to render differently and sometimes very broken. |
|
Sometimes you need to twist an html to make it render well on many browsers. I would rather have some broken html that renders well everywhere than valid html that doesn't render well everywhere.. in situations where it can't be fixed other way. |
![]() |
| Thread Tools | |
| Display Modes | |
| |