WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Illinois Functional Web Accessibility Evaluator/One Last Comment

for

From: Jon Gunderson
Date: Jan 24, 2007 9:10PM

Character encoding issues are somewhat complex issues since there can be conflicting information provided by META tags and the HTTP headers. Many content developers may not control the web server settings for http headers and/or maybe unaware of how to set them.

Probably the most likely scenario for FAE is to only warn people if the META or XML tag is missing, since another potential source of author character encoding information is the XML tag in xhtml document:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">


Jon


---- Original message ----
>Date: Wed, 24 Jan 2007 17:29:45 -0500
>From: "Robert Yonaitis" < <EMAIL REMOVED> >
>Subject: Re: [WebAIM] Illinois Functional Web Accessibility Evaluator/One Last Comment
>To: "WebAIM Discussion List" < <EMAIL REMOVED> >
>Cc: Nick Hoyt < <EMAIL REMOVED> >, Dan Linder < <EMAIL REMOVED> >
>
>Jon:
>
>Might help the users and the people on the list.
>
>It would seem the method you are requiring is NOT the primary method
>mentioned by the validator
>
>
>Help for The W3C Markup Validation Service. Retrieved January
> 24, 2007, from W3C Web site: http://validator.w3.org/
> docs/help.html#faq-charset
>
>
>An HTML document should be served along with its character encoding.
>
>Specifying a character encoding is "typically done by the web server
>configuration," by the scripts that put together pages, and inside the
>document itself. IANA maintains the list of official names for character
>encodings (called charsets in this context). You can choose from a
>number of encodings, though we recommend UTF-8 as particularly useful.
>
>
>Cheers,
>rob
>
>
>
>
>