Hi Egg.

You can replace charset declaration as explained in feature 9 here: http://www.talkgraphics.com/showthre...anced-features

You still get #1 probably because the encoding meta element is not the first element in the head section. You can only change this by editing exported file. But you can ignore it. This warning means that if there is some other elements prior to this one, that contain encoding sensitive content, it may not be interpreted correctly. This is not the case for Xara generated page however. All the elements prior to encoding meta are either not encoding sensitive or irrelevant for browsers. So all the content that does rely on declared encoding is safely placed after it's declaration.

The W3C mobileOK Checker is relatively simple set of rules of thumb that make sure your content is safe for most mobile browsers. However, since it lacks any intellect, it can not actually make a correct decision if any of these rules is redundant for a particular page code. So it takes a safe side by overkill recommendations just to not miss anything that might be dangerous in some cases. And that's why these encoding warnings have a "medium" severity.

My suggestion is to simply ignore them.