WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: trying to get a page to validate to AAA

for

From: Sandy
Date: Jul 14, 2010 8:12AM

Andrew, thank you for taking the time to look at this for me. And thanks
for mentioning that it's important to check the page how the document is
"served" up in the live environment - I've suspected this for a while,
and it's good to have it confirmed.

I've just been reading about Character Encoding
http://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116/#C_9

"When delivering the document from a server" that would be anything I
post, right? When would I not be delivering the document from a server?
I think just when I am checking it locally, but is that it?

Is there a "content-type for dummies" tutorial somewhere? I need a basic
introduction.

thanks,
Sandy


> 99% positive that's an error (as in what you have is correct but the
> validator is wrong). You are serving the right content content type and
> charset for your code and it validates happily through the W3C own
> validator. I don't think you are going to hit any problems there.
>
> If you do hit issues then consider if the content application driven /
> using XML etc. If not then you can most likely use:
>
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
>
> as defined in:
>
> http://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116/#C_9
>
> ...but there are restrictions: "In general, this media type is *NOT*
> suitable for XHTML except when the XHTML is conforms to the guidelines
> in Appendix A
> <http://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116/#compatGuidelines>;."
> (e.g. you can't add elements and attributes from foreign namespaces,
> such as XHTML+MathML).
>
>
> Testing locally is okay, but also validate remotely as it is important
> to check how the document is "served" up in the live environment - there
> is a difference.
>
> Regards
>
>