none
EW Reports vs. W3C validation?

    Question

  • How do the EW reports compare to html and css validation at W3C? I checked the reports on my recently rebuilt site, and got no incompatibilities or accessibility errors or warnings. Is that good enough, or should I run it past the Validator? It's for a hospital, albeit a small, rural one, so I want to be sure it is standards-compliant and accessible. Does W3C check for anything that the EW report won't show? Thanks.

    Jim
    Friday, January 30, 2009 10:49 PM

Answers

  • W3C doesn't do accessiblity checking. I'd probably run it through Cynthia Says (google for the url)
    MS MVP Expression http://by-expression.com
    • Marked as answer by fcphdJim Saturday, January 31, 2009 1:04 AM
    Friday, January 30, 2009 11:14 PM
  • I use FF to check everything I do **before** I publish it and check it at W3C, I have yet to have one fail validation using that method.

    Also, if you have used the accessability checker in EW you can be 99% sure it will pass.

     


    FrontPage MVP
    • Marked as answer by fcphdJim Saturday, January 31, 2009 1:03 AM
    Saturday, January 31, 2009 12:41 AM

All replies

  • W3C doesn't do accessiblity checking. I'd probably run it through Cynthia Says (google for the url)
    MS MVP Expression http://by-expression.com
    • Marked as answer by fcphdJim Saturday, January 31, 2009 1:04 AM
    Friday, January 30, 2009 11:14 PM
  • Open the site in Firefox and on the FF toolbar click Tools > Error Console.

    If it shows no errors, you are 99.99% golden.
    I would still chekc accessability as Cheryl says though.

     


    FrontPage MVP
    Friday, January 30, 2009 11:37 PM
  • Steve Easton said:

    Open the site in Firefox and on the FF toolbar click Tools > Error Console.

    If it shows no errors, you are 99.99% golden.
    I would still chekc accessability as Cheryl says though.


    FrontPage MVP

    Good point, but I would add that when you do, be sure to clear the console before loading your page if you came from this forum. The number of errors reported for this place is truly phenomenal!  ;-)

    But then again, so does Adobe's Community forum, here: http://community.adobe.com/help/search.html?q=shadow%20on%20path&hl=en_US&lr=en_US&l=illustrator_product_adobelr

    cheers,
    scott

    "Do as I say, not as I do."  ;-)
    Friday, January 30, 2009 11:47 PM
  • Sweet! 26 web pages later, the error console showed nothing. You guys have been a great help with my learning curve. I've picked up so much helpful information just lurking here. 

    Cheryl, that looks like a great resource for checking accessibility. I'll have to test it out as soon as I get my new site online. Steve, I hadn't even thought of FF. How does the error console compare to EW Reports? Is it more thorough? Scott, fortunately I am on the forum in Safari, so FF didn't overload on errors. I can imagine how that would look, as often as I have problems with this site!

    Regarding the W3C, is there any real reason to use their Validator, or is it just extra work in order to display a compliance logo? I'm just trying to determine what lengths I should go to. Thanks again.

    Jim
    Saturday, January 31, 2009 12:30 AM
  • I use FF to check everything I do **before** I publish it and check it at W3C, I have yet to have one fail validation using that method.

    Also, if you have used the accessability checker in EW you can be 99% sure it will pass.

     


    FrontPage MVP
    • Marked as answer by fcphdJim Saturday, January 31, 2009 1:03 AM
    Saturday, January 31, 2009 12:41 AM
  • Jim,

    When it comes to accessibility a few more resources for you:

    Remember that while I consider Cynthia Says to be the best of the automated checkers no automated checker can fully determine if your site is accessible. There are things you will have to manually check yourself such as the suitability of the alt attirubtes you used.


    MS MVP Expression http://by-expression.com
    Saturday, January 31, 2009 6:33 PM

  • I check mine in EW, do you have the code error icons setup btw?


    the day on Sunday  1st Feb - $22 - HALF our launch price
    http://www.frontpage-to-expression.com/ebook.html

     




    Tina Clarke http://any-expression.com/ http://www.expression-web.net/
    Sunday, February 01, 2009 3:07 AM
  • Thanks for the extra links Cheryl. I'll definitely be doing a little more checking on accessibility, but I think I've got it pretty well straightened out now. 
    Tina, I do have the error icons, and I watch for them religiously now. EW does really help with finding problems (although the error explanations can be pretty cryptic sometimes). 
    Thanks again for all the help. I hope to have my new, improved site online in a couple of days.

    Jim
    Monday, February 02, 2009 4:19 PM
  • Jim,

    If you have trouble figuring out what an Expression Web error means post a link to the page and where you are seeing the error. We'll try to help you figure it out.
    MS MVP Expression http://by-expression.com
    Monday, February 02, 2009 7:39 PM