Skip navigation

Meet Them: Benefits of Compliance with Web Standards

Before you can get your web page or blog noticed, you have to make sure all the parts fit together and it works properly.

Why? Well, in order to be seen, the page has to work. In other words, all the pieces and parts must be read by the user’s Internet browser, interpreted, and displayed upon the user’s screen. This seems like a simple task, but there is always a wrench thrown in to make it a little more complicated.

Currently, there are about a half dozen popular Internet browsers. Microsoft’s Internet Explorer is the most popular, closely followed by Firefox, Opera, and Safari. An Internet browser is software that interprets a web page’s code (HTML, CSS, PHP, etc.) and visually displays the content so it is easy to view and read. Different browsers feature different ways of interpretation, therefore you need to make sure your site’s coding can be read by the majority of browsers. Let’s look at HTML compliance and how to meet the W3 Organization’s standards and compliance guidelines.

Benefits of Compliance
Only good can come from complying with web design standards.

  • Everyone can read it
  • Viewable by any Internet browser
  • Viewable by any computerized system
  • Viewable by foriegn language-enabled computers
  • Viewable by different types of hardware and software media (cell phones, handheld computers, Web Tv, etc.
  • Avoid lawsuits from non-compliance
  • Search engines adore your pages
  • Faster page loading times
  • Greater odds of visitor return
  • Easier to update, repair, and change in the future

In 1994, a group of web designers and programmers got together to create standards for universal access in web page coding. The World Wide Web was to be the “face” of the Internet, and these people were determined to make all the information available on the Internet open to everyone, no matter what kind of computer or software they were using – and no matter what language they could read. They wanted it open and available, without limits.

This meant that the page not only had to be visually “pretty” for those with eyes, it had to “sound” and work pretty for those who are dependent upon other senses. An accessible web page should work on a computer monitor, with a browser that can’t “see” the graphics, with “reader software” (software that “reads” out loud what is on the screen), braille readers (converts content to a special board that produces braille), and can be used by someone without the use of their arms or hands. With an estimated 20% of all Internet users physically challenged in some way, the need for this kind of access is critical.

Ah, but they didn’t limit the concept of accessibility to only the physically challenged. Millions of people want access to web pages on handheld computers, Web TV, and cell phones. Access for all means access for all.

The W3C created a uniform code for the programing language of the World Wide Web. They set the standards for approval and modification of the code and developed methods of validating that code. Internet browsers slowly caught onto the idea of standardization and today web designers can pretty much design web pages from one set of standard code. This benefits everyone. it’s like everyone speaking the same language at an international meeting – we all understand more.

Part of creating standards for the web is the challenge of compliance. There are no rules that state web page designers have to follow the standards set up by the W3, but if you want to design web pages for everyone, and I mean EVERYONE, then best play by the same rules as everyone else so everyone can access your pages.

Why Validate and Maintain Web Design Standards

There are a lot of reasons to meet web design standards, but one of the biggest reasons is search engine friendliness. The cleaner your code, the more error-free, the happier you make search engines. Google and others actually score points for validated and compliant website code. The easier it is for search engines to crawl through your site, the faster you end up in their database, working on your page rank.

5 Comments

  1. Posted November 14, 2005 at 11:12 am | Permalink

    I visited a leading**cough**cellular telecommunications industry website last week using Firefox. I wish they had tried to meet web standards–they would have earned US$400 plus a two-year contract…

  2. Posted November 14, 2005 at 11:41 am | Permalink

    Oh, very good point. I’ve had a horrible time even accessing documents and information on the IRS and other US Government pages that are not accessible or even Firefox capable. I have to run IE in order to get them to work. Very, very bad form.

    In England, all government websites are required to meet accessibility standards, which should include viewability and function no matter which browser is being used. The fines are huge. Hopefully, they all have complied, but the US, as in most things nowadays, though the propoganda says otherwise, is WAY behind the times.

  3. Posted November 26, 2005 at 11:14 am | Permalink

    Sure, web standards are really cool and stuff, I always code in XHTML 1.0 Strict, and your article was very helpful, but I just wanted to say one thing: coding valid doesn’t mean browser compliance. It happens often enough that you write valid code but that it ends up messy in Internet Explorer. Luckily, there are also browsers such as Firefox :D

  4. Jonathan Mark
    Posted April 11, 2009 at 8:26 am | Permalink

    Nice article and it really did open up my eyes.Thanks.

  5. Posted August 6, 2009 at 2:42 am | Permalink

    Some times a caompletely valid code may not appear as it should in internet explorer 6 :(

    “at least 60% of the designers time is spent on making it work with ie6″


32 Trackbacks/Pingbacks

  1. [...] Very simple and easy to do. And a requirement to meet the most basic Web Standards. [...]

  2. [...] While the CSS and HTML web standards are in place, they are still a growing and evolving entity. As Internet browsers get more advanced, the codes change with them. Before standards became the norm, a designer would have to design their web pages to accommodate all the different browsers out there and the different ways they handle code. Today, a few designers are still designing for older browsers, but most people have gotten the clue and updated their Internet software. Still, even today’s browsers have some bugs and here are some fixes to deal with the ones in Microsoft Internet Explorer, the most common Internet browser in the world. [...]

  3. [...] Meet Them – Benefits of Compliance with Web Standards [...]

  4. [...] Accessibility is the development of a website or blog to be accessible to everyone. This means that the design must meet web standards and pass a range of validation tests in order to be compliant with many countries accessibility and equal opportunity laws. It also helps the website owner/administrator to have a website that can be viewed and used by the disabled, blind or visually impaired, those using cell phones, handheld computers, web-TV, and older and newer browsers. In other words, accessibility means designing a website that can be seen and used by everyone and anyone. [...]

  5. [...] Search engine optimization (SEO) is not hard. In fact, for WordPress.com users, it’s fairly easy. Most WordPress Themes come SEO ready, with solid validated code and usually meeting web and accessibility standards. The only area you need to worry about is what you put in the post title, post content, and image and link information. [...]

  6. [...] Benefits of Compliance with Web Standards [...]

  7. [...] In order to make the link to the post meet accessibility web standards, we need to add a “title” to the link. Using the same title template tag, we can insert the title of the post into the link to the post. [...]

  8. [...] Which brings me to the reality of the web. So many of us fought for accessibility in web page design, and the development of accessibility-enabled software tools and hardware to help the blind, handicapped, and finger-unabled to use the web. Where are these tools? And why aren’t they available to everyone, not just the disabled? Are they still too expensive? What happened to them? [...]

  9. [...] A robot can spot a well designed page because it can get to the “good stuff” faster. A well-coded and validated site provides information to the search engine’s crawler that can help your site rise in the page ranks. Solid code allows the crawler to move easily through your site, which tells the search engine the site is designed with care and attention to detail and web standards. The easier you make the job for the robot, the more likely they will visit you, and return. [...]

  10. [...] Meet Them: Benefits of Compliance with Web Standards [...]

  11. [...] create an accessible blog and why you should, asked disabled bloggers to share their stories, the benefits of improved search engine optimization and page ranking that comes with compliance with web…, and so much [...]

  12. [...] Lorelle’s Meet Them: Benefits of Compliance with Web Standards [...]

  13. [...] in the Blog Herald announcement of CSS Naked Day, this is also an opportunity to showcase how usable and accessible your web page structure is even without the pretty, reminding the world that it is the law that [...]

  14. [...] in the Blog Herald announcement of CSS Naked Day, this is also an opportunity to showcase how usable and accessible your web page structure is even without the pretty, reminding the world that it is the law that [...]

  15. [...] in the Blog Herald announcement of CSS Naked Day, this is also an opportunity to showcase how usable and accessible your web page structure is even without the pretty, reminding the world that it is the law that [...]

  16. [...] Meet Them – Benefits of Compliance with Web Standards [...]

  17. [...] Many a theme author is more of a designer than a coder, and thus they sometimes hack around until it finally looks the way they want, without bothering to check whether the code they’ve written is actually valid HTML. If it’s not, current or future browsers might have issues rendering the content correctly. You can check whether the code is valid by using the W3C’s validator. Lorelle wrote an excellent article on the benefits of compliance. [...]

  18. [...] W3C’s validator 来检验。Lorelle [...]

  19. [...] Bookmarked a link on Delicious. Meet Them: Benefits of Compliance with Web Standards « Lorelle on WordPress [...]

  20. [...] W3C’s validator 来检验。Lorelle [...]

  21. [...] Review Web Standards [...]

  22. [...] Review Web Standards [...]

  23. […] Meet Them: Benefits of Compliance with Web Standards […]

  24. […] Meet Them: Benefits of Compliance with Web Standards […]

  25. […] Meet Them: Benefits of Compliance with Web Standards […]

  26. […] standards and how to techniques – put your effort where your mouth is and make your own sites meet web standards as an example for […]

  27. […] Meet Them – Benefits of Compliance with Web Standards […]

  28. […] Meet Them: Benefits of Compliance with Web Standards […]

  29. […] To set the off-site location for your tag links, here are some examples (I left the titles off for clearer code, but make sure you put titles back in for compliance with accessibility standards): […]

  30. […] Meet Them: Benefits of Compliance with Web Standards […]

  31. […] – Lorelle VanFossen Benefits of Compliance with Web Standards […]

  32. […] Meet Them: Benefits of Compliance with Web Standards […]

Post a Comment

Follow

Get every new post delivered to your Inbox.

Join 21,176 other followers

%d bloggers like this: