W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2009

Re: Best way to markup standards compliant symbols

From: Harry Loots <harry.loots@ieee.org>
Date: Fri, 20 Mar 2009 11:34:44 +0100
To: w3c-wai-ig@w3.org
Message-Id: <20090320103444.M56487@ieee.org>

Characters outside the seven-bit ASCII range should be encoded. If characters
are not encoded then it may lead to mis-representation in the host browser -
thus an inter-operability failure. 

It is not irrelevant to accessibility as lack of inter-operability may lead to
inaccessible pages. 

  You can find more information here:

Warm regards

 We do not inherit the Earth from our Parents-
 We are simply Borrowing it from our Children!

 Join 'Consumer Resistance Against Packaging' at

---------- Original Message -----------
From: David Dorward <david@dorward.me.uk>
To: w3c-wai-ig@w3.org
Sent: Fri, 20 Mar 2009 10:06:51 +0000
Subject: Re: Best way to markup standards compliant symbols

> Mery Richard wrote:
> > I am wondering which would be the most and best way to achieve 
> > standards compliant symbols such as commas and apostrophes?
> >  
> > I.e. &amp; &gt; etc,
> >  
> > Do they have to be coded characters or can they be regular text?
> The only characters that need to be represented using a character 
> reference are those which would otherwise have special meaning in 
> (such as < in a place where a tag can be started or " inside an 
> attribute value that is delimited with strings).
> If you are using a non-Unicode encoding (don't do that), then you 
> also need to use character references to represent characters that 
> don't exist in the encoding being used.
> This is all very low level stuff and irrelevant to accessibility - 
> the only reason people might have problems (assuming the author 
> hasn't made a mistake) is if they are using a truly broken tool to 
> parse the HTML.
> -- 
> David Dorward
> http://dorward.me.uk/
------- End of Original Message -------
Received on Friday, 20 March 2009 10:35:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:38 UTC