W3C Internationalization Checker
Is your page world ready?
W3C Internationalization Checker
Is your page world ready?
| Character encoding | Code | |
|---|---|---|
| HTTP Content-Type | iso-8859-1 |
Content-Type: text/html; charset=iso-8859-1 |
| Byte order mark (BOM) | No | |
| Meta tag | None found | |
| Language | Code | |
| HTML tag | None |
<html> |
| HTTP Content-Language | None found | |
| All language tags | None found | |
| Text direction | Code | |
| Default direction | LTR (by default) | |
| Unicode control codes | None found | |
| Markup | Code | |
| Non-ascii class or id names | None | |
| Non-NFC class or id names | None | |
| Notable attributes | None found | |
| Notable elements | None found | |
| Request headers | Code | |
| Accept-Language | None found | |
| Accept-Charset | None found |
The align attribute is used In the following tag or tags the align attribute was used:
<p align="right"><img align="left" alt="W3C" border="0" src="/Icons/WWW/w3c_home" width="72" height="48"/><h1 align="center"><h3 align="center"><img src="ex1.gif" align="MIDDLE" alt="[diagram]"/><tr align="LEFT"><td align="RIGHT" valign="BASELINE"><td align="CENTER" valign="BASELINE"><td align="LEFT" valign="BASELINE"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT"><td align="RIGHT">This attribute should no longer be used in HTML. In addition to being obsoleted by the HTML specification, embedding its values of left and right into the markup causes difficulties when translating into languages using right-to-left scripts, because the values need to be painstakingly reversed one by one. It is much better to handle this using CSS, since CSS makes it easy to propagate changes throughout this document, and indeed the site (and will in the future make life even easier as the start and end property values become more widely supported).
Remove the align attribute and use CSS to achieve the same effect.
Non-UTF-8 character encoding declared The page currently uses the following non-UTF-8 character encoding declaration(s):
Content-Type: text/html; charset=iso-8859-1UTF-8 is based on Unicode. A Unicode character encoding makes it easier to use a wide range of characters, from the registered trademark symbol to characters in multiple languages. It also simplifies the use of scripts and databases for multilingual sites, and allows you to more easily expand your site to cover new languages, when needed. Using non-UTF-8 encodings can also have unexpected results on form submission and URL encodings, which use the document's character encoding by default. The HTML5 specification and the Encoding specification recommend its use in the strongest terms.
(UTF-16 is also a character encoding based on Unicode, but is little used on the Web, and you should not use it.)
Set your authoring tool to save your content as UTF-8, and change the encoding declarations.
Non-preferred name used for legacy character encoding The page currently declares the character encoding using a non-preferred name:
ISO-8859-1The preferred encoding name is:
WINDOWS-1252A wider range of browsers will support your page if you use the preferred encoding name. However, it is strongly recommended that you convert your page to use the UTF-8 character encoding.
Preferably, set your authoring tool to save your content as UTF-8, and change the encoding declarations. Otherwise, change the name of the encoding for your page to the preferred name. (Legacy encoding names are listed in the Encoding specification, in the left column of the table in the section Names and labels.)
Encoding declared only in HTTP header A character encoding is specified in the HTTP header (Content-Type: text/html; charset=iso-8859-1), but there was no matching encoding declaration in the page. This may lead to problems later if there is a chance that the document will be read from or saved to disk, CD, etc.
In addition, the W3C Internationalization (i18n) Group recommends to always include a visible encoding declaration in a document, because it helps developers, testers, or translation production managers to check the encoding of a document visually.
Add information to indicate the character encoding of the page inside the page itself.
The html tag has no language attribute There is no language attribute in the html tag.
<html>A language attribute on the html tag sets the default natural language for the page. This information is used for processing the content in various ways, including such things as spell-checking, accessibility, data formatting, hyphenation, default fonts and line-breaking, case conversion, and various other features for rendering the page. Every page should have the correct default language specified.
Add a lang attribute to the html tag that indicates the default language of your page.
Example: <html lang='de'>
b tags found with no class attribute One or more b tags that don't use a class attribute were found in the source code for this page. These tags may cause problems for localization if the content for which they are used has more than one semantic value.
Total number of b tags: 28.
Number of b tags without a class attribute: 28.
You should not use b tags if there is a more descriptive and relevant tag available. If you do use them, it is usually better to add class attributes that describe the intended meaning of the markup, so that you can distinguish one use from another.
i tags found with no class attribute One or more i tags that don't use a class attribute were found in the source code for this page. These tags may cause problems for localization if the content for which they are used has more than one semantic value.
Total number of i tags: 44.
Number of i tags without a class attribute: 44.
You should not use i tags if there is a more descriptive and relevant tag available. If you do use them, it is usually better to add class attributes that describe the intended meaning of the markup, so that you can distinguish one use from another.
Interested in “developing” your developer skills? In W3Cx’s hands-on Professional Certificate Program, learn how to code the right way by creating Web sites and apps that use the latest Web standards. Find out more!
Donate and help us build better tools for a better web.
