HTML Coding Errors

  • 1
  • Problem
  • Updated 5 years ago
I have just checked my website with an HTML validation service, the report came back with 27 errors. As I cannot access the code I am unable to repair the problems. These errors - a: leave the website vulnerable to hacking (unlikely but possible) and b: may render it difficult to read by search engines thus reducing my SEO. What can you do to help me with this?
Photo of Al Doughty

Al Doughty

  • 1 Post
  • 0 Reply Likes
  • frustrated

Posted 5 years ago

  • 1
Photo of the_pete

the_pete

  • 65 Posts
  • 16 Reply Likes
Hey Al

We're very sorry about the HTML validation errors in our generated code - we do try to only generate valid HTML. However, there are a few challenges in the way of that goal.

- The contentEditable API provided by the browser that we use for text editing generates wildly different HTML depending on which browser you edited in - lots of it is invalid.
- We've had to make concessions in our widget code to support multiple browsers as well as dynamic widths (one widget has to work in all styles).
- The combinations of widgets and different content is very large and hard enough to test visually cross browser - so it has taken a lower priority.

The reason we haven't raised the priority is because based on what we understand, a lot of the W3C compliance issues we introduce don't have real world consequences. For example...

- I'm almost certain html validation issues will never result in a higher likelihood of hacking.
- The effects on SEO are negligible in that search engines prioritize errors that will effect rendering - and we make very few of those (and try are hardest to make none).
- The effects on rendering can be bad - but we do extensive testing to make sure we never cross a line that will cause rendering issues.

Thanks for pointing out the issues we have in this area.