W3C mobileOK Checker

Size	Type	URI
34.8KB	image	http://www.google.com/images/srpr/nav_logo80.png
10.6KB	document	Resource under test
7.2KB	image	http://www.google.com/intl/en_ALL/images/srpr/logo1w.png

Type	URI
document	Resource under test
image	http://www.google.com/images/srpr/nav_logo80.png
image	http://www.google.com/intl/en_ALL/images/srpr/logo1w.png

Detailed report

The label of each of the following failure messages contains its severity, its category, and a short description of the failure completed by the underlying best practice that triggered the failure.

Severity: ; category: ; description: Table contains less than two tr elements ; Best Practice: TABLES LAYOUT
Why?

A table with only one row is either the sign that the table is used:

to represent a list of items horizontally

to control the relative position of various sections of the page

Both uses imply a layout based on tables. While most mobile devices support basic tables, they are rendered quite differently by different mobile browsers, and cannot be reliably used for layout. The table element should only be used - with care - to represent tabular data.
How?

Use CSS techniques to control the layout of the page. For instance, if you were trying to render a list of items horizontally, consider:

<ul> <li>Item 1</li> <li>Item 2</li> </ul> in the markup of the page

ul li { display: inline; } in the CSS style sheet to force the items of the list to be rendered on the same line
Where?

Triggered by the resource under test:

Line 12

… <table cellpadding="0" cellspacing="0"><tr valign="top">
More information

Severity: severe

Most mobile devices should render the page but the user experience is strongly impacted.

Category: Stay away from known hazards

Thoughtful design can help reduce usability problems due to small screens and keyboards, and other features of mobile devices.

Best practice: TABLES_LAYOUT

Do not use tables for layout.

Top
Severity: ; category: ; description: A length property uses an absolute unit ; Best Practice: MEASURES
Why?

Using absolute measures in CSS creates layouts that do not adapt to the screen dimensions.

How?

Use em or percentage based values in CSS.
Where?

Triggered 16 times by the resource under test. 10 first occurrences:

Line 9

… font-size:13px

Line 9

… height:22px

Line 9

… font-size:1px

Line 9

… line-height:17px

Line 9

… height:25px

Line 9

… width:496px

Line 9

… font:18px arial,sans-serif

Line 9

… font:18px arial,sans-serif

Line 9

… font:17px arial,sans-serif

Line 9

… height:30px
More information

Severity: low

Useful improvements are possible.

Category: Check graphics and colors

Images, colors, and style brighten content, but require care: devices may have low-contrast screens or may not support some formats.

Best practice: MEASURES

Do not use pixel measures and do not use absolute units in markup language attribute values and style sheet property values.

Top
Severity: ; category: ; description: The total size of the page (52.5KB) exceeds 20 kilobytes (Primary document: 10.6KB, Images: 41.9KB, Style sheets: 0) ; Best Practice: PAGE SIZE LIMIT

Why?

Big pages require a possibly high cost and a long waiting time in many mobile networks. For instance, on many mobile networks, downloading 100KB worth of data takes as long as 1 minute.

How?

Focus on the piece of information that you want to deliver. Scale down images to a reasonable size. Remove images that are not essential to the layout of the page. Make sure to separate CSS styles defined for screen and handheld media types so that only relevant CSS styles are downloaded by most devices.

Where?

Triggered by the resource under test.

More information

Severity: low

Useful improvements are possible.

Category: Keep it small

Smaller sites make users happier by costing less in time and money.

Best practice: PAGE_SIZE_LIMIT

Ensure that the overall size of page is appropriate to the memory limitations of the device.

Top
Severity: ; category: ; description: The document does not validate against XHTML Basic 1.1 or MP 1.2. ; Best Practice: VALID MARKUP
Why?

The document is invalid XHTML or uses elements or structures that are not allowed in the XHTML Basic 1.1 specification. This is likely to be problematic for mobile browsers who are more sensitive to the structure of the content than desktop browsers.

How?

Check the page with the W3C Markup Validator
While unknown elements are likely to be ignored by browsers, a simple syntax error may invalidate the document to the point where browsers cannot render it anymore. Also bear in mind that checks were run against a tidied version of the document. The tidying process may have modified the structure and semantics of the original document and may have either created new problems or fixed existing ones.
Where?

Triggered 5 times by the resource under test:

Line 1, Column 175 — Attribute "itemscope" is not allowed for element type "html".

Line 1, Column 175 — Attribute "itemtype" is not allowed for element type "html".

Line 1, Column 476 — Attribute "itemprop" is not allowed for element type "meta".

Line 1, Column 505 — Attribute "type" is required and must be specified for element type "script".

Line 2, Column 75 — The entity name must immediately follow the '&' in the entity reference.
More information

Severity: low

Useful improvements are possible.

Category: Rely on Web standards

In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

Best practice: VALID_MARKUP

Create documents that validate to published formal grammars.

Top
Severity: ; category: ; description: The embedded image or object is not of type image/gif or image/jpeg (image/png) ; Best Practice: CONTENT FORMAT SUPPORT
Why?

The document contains images that are not in GIF or JPEG format, or are not correctly served by the Web server. Images in formats other than GIF or JPEG may not work on some mobile browsers.
How?

Convert with an image editor the said images either to GIF or to JPEG, depending on the type of images;

Either update the links to these new versions, or use Content Negotiation to have both versions available and served depending on the browser capabilities.
Where?

Triggered by http://www.google.com/images/srpr/nav_logo80.png.

Triggered by http://www.google.com/intl/en_ALL/images/srpr/logo1w.png.

More information

Severity: low

Useful improvements are possible.

Category: Rely on Web standards

In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

Best practice: CONTENT_FORMAT_SUPPORT

Send content in a format that is known to be supported by the device.

Top
Severity: ; category: ; description: The HTTP Content-Type header specifies a character encoding other than UTF-8 ; Best Practice: CHARACTER ENCODING SUPPORT

Why?

The page under test uses a character encoding other than UTF-8. Given the number of character encodings used across the world, sending UTF-8 encoded content to browsers that request it increases significantly the chances of properly displaying a page.

How?

See how to set the charset information in Apache and learn more about Unicode and UTF-8.

Where?

Triggered by the resource under test.

More information

Severity: low

Useful improvements are possible.

Category: Rely on Web standards

In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

Best practice: CHARACTER_ENCODING_SUPPORT

Ensure that content is encoded using a character encoding that is known to be supported by the device.

Top
Severity: ; category: ; description: The size of the document's markup (10.6KB) exceeds 10 kilobytes ; Best Practice: PAGE SIZE LIMIT

Why?

Mobile devices have limited screens. Long pages on small screens are confusing, because users can't see the big picture and feel lost. Some mobile devices with limited memory still can't handle pages that are more than a few Kb but, in essence, the 10Kb limit was set for usability reasons. Some screens may be big enough to display pages with more content. The 10Kb limit ensures that the page is still usable on devices with small screens.

How?

Focus on the piece of information that you want to deliver, and build the page around it.

Where?

Triggered by the resource under test.

More information

Severity: low

Useful improvements are possible.

Category: Keep it small

Smaller sites make users happier by costing less in time and money.

Best practice: PAGE_SIZE_LIMIT

Ensure that the overall size of page is appropriate to the memory limitations of the device.

Top
Severity: ; category: ; description: The document contains one of basefont, bdo, center, del, dir, font, ins, menu, s, strike or u elements ; Best Practice: STYLE SHEETS USE
Why?

Elements that have an impact on layout are not supported by most mobile devices.

How?

Use CSS style sheets to control the layout of the page.
Where?

Triggered 2 times by the resource under test:

Line 12

… <u>More</u> »

Line 12

… <center><br clear="all" id="lgpd" /></br><div id="lga">
More information

Severity: low

Useful improvements are possible.

Category: Rely on Web standards

In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

Best practice: STYLE_SHEETS_USE

Use style sheets to control layout and presentation, unless the device is known not to support them.

Top
Severity: ; category: ; description: The document uses scripting ; Best Practice: OBJECTS OR SCRIPT
Why?

Scripting can be used, but shouldn't be relied upon, since many mobile devices do not support or hardly support scripting. The page should still be usable when scripting is not enabled.

How?

Use scripting to enhance your page, but degrade gracefully when scripting is not supported.
Where?

Triggered 5 times by the resource under test:

Line 1

… <script>(function(){ window.google={kEI:"GcufUYTvO

Line 9

… <script /></script>

Line 9

… <script>(function(){var src='/images/srpr/nav_logo

Line 12

… <script>if(google.y)google.y.first=[];(function(){

Line 13

… <script>(function(){var b,c,d,e;function g(a,f){a.
More information

Severity: informational

An informational message is a lightweight warning that alerts authors on a point that may have an impact on the user experience on mobile devices if it is not handled with care. For instance, using scripting is not discouraged but authors should check that the page remains usable without scripting. Informational messages do not affect the score of the page.

Category: Be cautious of device limitations

When choosing to use a particular Web technology, consider that mobile devices vary greatly in capability.

Best practice: OBJECTS_OR_SCRIPT

Do not rely on embedded objects or script.

Top
Severity: ; category: ; description: An element uses an event attribute ; Best Practice: OBJECTS OR SCRIPT
Why?

Using event attributes means that scripts and content are mixed in the page.

How?

Register the events listeners in the script, separated from the content of the page.
Where?

Triggered 2 times by the resource under test:

Line 12

… <img alt="Google" height="95" id="hplogo" onload="window.lol&&lol()" src="/intl/en_ALL/images/srpr/logo1w.png" style="padding:28px 0 14px" width="275" />

Line 12

… <input class="lsb" name="btnI" onclick="if(this.form.q.value)this.checked=1; else top.location='/doodles/'" type="submit" value="I'm Feeling Lucky" />
More information

Severity: warning

A warning alerts authors on a point that may have an impact on the user experience on mobile devices and that may be worth checking. A warning does not necessarily mean that something needs to be fixed in the page. Warnings do not affect the score of the page.

Category: Be cautious of device limitations

When choosing to use a particular Web technology, consider that mobile devices vary greatly in capability.

Best practice: OBJECTS_OR_SCRIPT

Do not rely on embedded objects or script.

Top
Severity: ; category: ; description: A Table element exists ; Best Practice: TABLES ALTERNATIVES
Why?

Most mobile devices support basic tables. Use tables with care. In particular, if the width of the table is likely to be larger than the width of the mobile device's screen, the result may not be usable for users: rows may be wrapped on multiple lines with no clear way to distinguish between rows and continuation of rows, or the browser may zoom out so that users see the whole table, resulting in words written in too tiny characters to be read.
Using tables to control the layout of the page rather than to display tabular data is a bad practice in all cases (mobile or not). Mobile browsers in particular are unlikely to render them as they would be on a big screen.

How?

Consider converting tables to a linear layout, e.g. using definition lists (dl, dt and dd elements). Instead of a table-based layout, use CSS techniques instead. See a tutorial on table-less layout.
Where?

Triggered by the resource under test:

Line 12

… <table cellpadding="0" cellspacing="0"><tr valign="top">
More information

Severity: informational

An informational message is a lightweight warning that alerts authors on a point that may have an impact on the user experience on mobile devices if it is not handled with care. For instance, using scripting is not discouraged but authors should check that the page remains usable without scripting. Informational messages do not affect the score of the page.

Category: Be cautious of device limitations

When choosing to use a particular Web technology, consider that mobile devices vary greatly in capability.

Best practice: TABLES_ALTERNATIVES

Where possible, use an alternative to tabular presentation.

Top
Severity: ; category: ; description: The CSS style sheet contains rules referencing the position, display or float properties ; Best Practice: STYLE SHEETS SUPPORT
Why?

Support for CSS style sheets varies from one device to the other, and cannot be entirely relied upon, especially to position the elements precisely. Floating and absolutely positioned elements should also be avoided on limited screens for usability reason since they may trigger scrolling in two directions.
Where?

Triggered 9 times by the resource under test:

Line 9

… position:absolute

Line 9

… float:left

Line 9

… display:inline-box

Line 9

… display: inline-block

Line 9

… display:block

Line 9

… display:block

Line 9

… display:inline-block

Line 9

… display:inline-block

Line 12

… display:none
More information

Severity: warning

A warning alerts authors on a point that may have an impact on the user experience on mobile devices and that may be worth checking. A warning does not necessarily mean that something needs to be fixed in the page. Warnings do not affect the score of the page.

Category: Be cautious of device limitations

When choosing to use a particular Web technology, consider that mobile devices vary greatly in capability.

Best practice: STYLE_SHEETS_SUPPORT

Organize documents so that if necessary they may be read without style sheets.

Top
Severity: ; category: ; description: HTTP status code 3xx (Redirection) received and the HTTP Location header targets a relative URI ; Best Practice:

Why?

Redirections should be avoided because of the usually high latency of mobile networks. Since the final URI of the resource is on the same server, server-based redirection may be possible and would save a round-trip between the server and the end user

Where?

Triggered by http://www.google.com/language_tools?hl=en&authuser=0.

More information

Severity: warning

A warning alerts authors on a point that may have an impact on the user experience on mobile devices and that may be worth checking. A warning does not necessarily mean that something needs to be fixed in the page. Warnings do not affect the score of the page.

Category: HTTP errors

The mobileOK Checker could not retrieve some of the resources required to run the tests or has found broken links.

Top
Severity: ; category: ; description: The linked resource character encoding may not be appropriate for mobile devices ; Best Practice: LINK TARGET FORMAT
Why?

The mobileOK Checker checked the HTTP Content-Type header returned in response to the linked resource and found out that:

the character encoding of the resource was not specified at that level. In this case, please note that the mobileOK Checker did not check whether the character encoding was specified at the content level (in the XML declaration or in a meta element) for performance reasons. Please check each resource individually to determine whether its character encoding is properly specified.

or that a character encoding different from UTF-8 was specified at the HTTP level. Given the number of character encodings used across the world, sending UTF-8 encoded content to browsers that requests it increases significantly the chances of properly displaying a page.
How?

Learn more about declaration of character encoding.
Where?

Triggered by http://maps.google.com/maps?hl=en&tab=wl:

character encoding iso-8859-1

Triggered by http://www.google.com/?source=classic:

character encoding iso-8859-1

Triggered by http://www.google.com/advanced_search?hl=en&authuser=0:

character encoding iso-8859-1

Triggered by http://www.google.com/history/optout?hl=en:

character encoding iso-8859-1

Triggered by http://www.google.com/imghp?hl=en&tab=wi:

character encoding iso-8859-1

Triggered by http://www.google.com/intl/en/about.html:

no character encoding found in the Content-Type HTTP header

Triggered by http://www.google.com/intl/en/ads/:

no character encoding found in the Content-Type HTTP header

Triggered by http://www.google.com/intl/en/options/:

no character encoding found in the Content-Type HTTP header

Triggered by http://www.google.com/intl/en/policies/:

no character encoding found in the Content-Type HTTP header

Triggered by http://www.google.com/preferences?hl=en:

character encoding iso-8859-1

Triggered by http://www.google.com/services/:

no character encoding found in the Content-Type HTTP header
More information

Severity: informational

An informational message is a lightweight warning that alerts authors on a point that may have an impact on the user experience on mobile devices if it is not handled with care. For instance, using scripting is not discouraged but authors should check that the page remains usable without scripting. Informational messages do not affect the score of the page.

Category: Optimize navigation

Simple navigation and typing become critical when using a small screen and keyboard, and limited bandwidth.

Best practice: LINK_TARGET_FORMAT

Note the target file's format unless you know the device supports it.

Top
Severity: ; category: ; description: "Cache-Control" HTTP header is present and contains value "no-cache", or contains value "max-age=0" ; Best Practice: CACHING

Why?

A no-cache (or max-age=0) directive prevents browsers from caching the content, and thus requires them to retrieve it through the network every time.

How?

If the resource needs to be revalidated each time it is queried, consider using the Last-Modified and/or ETag HTTP headers to limit the complete retrieval of the resource to the cases where the resource has changed. See Mark Nottingham's tutorial on caching to learn more about these techniques.

Where?

Triggered by the resource under test.

More information

Severity: warning

A warning alerts authors on a point that may have an impact on the user experience on mobile devices and that may be worth checking. A warning does not necessarily mean that something needs to be fixed in the page. Warnings do not affect the score of the page.

Category: Use the network sparingly

Web protocol features can help improve the user experience by reducing the impact of network bottlenecks and latencies.

Best practice: CACHING

Provide caching information in HTTP responses.

Top
Severity: ; category: ; description: A cache related header or a meta http-equiv value contains an invalid value ; Best Practice: CACHING
Why?

An unknown value in a caching directive may be the result of a typo, and could prevent browsers from properly handling the caching information.
Where?

Triggered by the resource under test:

Invalid value "-1" in "Expires" header
More information

Severity: warning

A warning alerts authors on a point that may have an impact on the user experience on mobile devices and that may be worth checking. A warning does not necessarily mean that something needs to be fixed in the page. Warnings do not affect the score of the page.

Category: Use the network sparingly

Web protocol features can help improve the user experience by reducing the impact of network bottlenecks and latencies.

Best practice: CACHING

Provide caching information in HTTP responses.

Top
Severity: ; category: ; description: The document is not served as "application/xhtml+xml" ; Best Practice: CONTENT FORMAT SUPPORT
Why?

The recommended media type for serving XHTML is application/xhtml+xml. More browsers are likely to support that media type, and optimize the rendering for it. application/vnd.wap.xhtml+xml is widely used and supported in mobile networks as well but is unlikely to be supported by non-mobile browsers.

How?

See how to properly configure server mime types. If the page under test uses a non-XML version of HTML, you should first consider switching to XHTML. In any case, do not serve a non-XML version of HTML with an application/xhtml+xml media type.
Beware: some browsers have no support for application/xhtml+xml (e.g. Internet Explorer) and prompt users to download pages served as such. You should not serve XHTML content to browsers that do not support it. Use Content Negotiation to match the browser's capabilities. See the XHTML Media Types - Second Edition W3C note for more information and in particular the Compatibility Guidelines to follow to have XHTML documents rendered on both XHTML-aware and HTML-only user agents.
Where?

Triggered by the resource under test:

served as text/html
More information

Severity: informational

An informational message is a lightweight warning that alerts authors on a point that may have an impact on the user experience on mobile devices if it is not handled with care. For instance, using scripting is not discouraged but authors should check that the page remains usable without scripting. Informational messages do not affect the score of the page.

Category: Rely on Web standards

In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

Best practice: CONTENT_FORMAT_SUPPORT

Send content in a format that is known to be supported by the device.

Top
Severity: ; category: ; description: The document uses a non-XML doctype (no DTD found or doctype declaration invalid) ; Best Practice: CONTENT FORMAT SUPPORT

Why?

The document uses a doctype that is not recognized as an XHTML doctype. Mobile browsers can optimize the parsing and rendering of pages with an XHTML doctype.

How?

Switch to XHTML if you are using a non-XML version of HTML; or pick a well-known XHTML doctype otherwise.

Where?

Triggered by the resource under test.

More information

Severity: warning

A warning alerts authors on a point that may have an impact on the user experience on mobile devices and that may be worth checking. A warning does not necessarily mean that something needs to be fixed in the page. Warnings do not affect the score of the page.

Category: Rely on Web standards

In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

Best practice: CONTENT_FORMAT_SUPPORT

Send content in a format that is known to be supported by the device.

Top
Severity: ; category: ; description: The documents uses one of b, big, i, small, sub, sup or tt elements ; Best Practice: STYLE SHEETS USE
Why?

Presentation effects should be defined separately from the content, in a CSS style sheet that can be re-used and cached across pages.

How?

Use CSS style sheets to control the layout of the page.
Where?

Triggered by the resource under test:

Line 12

… <b class="gb1">Search</b> <a class="gb1" href="http://www.google.com/imghp?hl=en&tab=wi">
More information

Severity: warning

A warning alerts authors on a point that may have an impact on the user experience on mobile devices and that may be worth checking. A warning does not necessarily mean that something needs to be fixed in the page. Warnings do not affect the score of the page.

Category: Rely on Web standards

In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

Best practice: STYLE_SHEETS_USE

Use style sheets to control layout and presentation, unless the device is known not to support them.

Top
Severity: ; category: ; description: The style attribute is used ; Best Practice: STYLE SHEETS USE
Why?

The style attribute is deprecated in XHTML Basic 1.1. As a generic rule, content and layout should be separated, and styles defined in an appropriate embedded or external CSS style sheet. This also favors re-use and caching of the different styles.
Where?

Triggered 13 times by the resource under test. 10 first occurrences:

Line 12

… <textarea id="csi" style="display:none" /></textarea>

Line 12

… <a class="gb1" href="http://www.google.com/intl/en/options/" style="text-decoration:none">

Line 12

… <div class="gbh" style="left:0" /></div><div class="gbh" style="right:0" />

Line 12

… <div class="gbh" style="right:0" /></div>

Line 12

… <img alt="Google" height="95" id="hplogo" onload="window.lol&&lol()" src="/intl/en_ALL/images/srpr/logo1w.png" style="padding:28px 0 14px" width="275" />

Line 12

… <div class="ds" style="height:32px;margin:4px 0"><input autocomplete="off" class="lst" maxlength="2048" name="q" size="57" style="color:#000;margin:0;padding:5px 8px 0 6px;vertical-align:top" title="Google Search" value="" />

Line 12

… <input autocomplete="off" class="lst" maxlength="2048" name="q" size="57" style="color:#000;margin:0;padding:5px 8px 0 6px;vertical-align:top" title="Google Search" value="" />

Line 12

… <br style="line-height:0" /></br><span class="ds"><span class="lsbb">

Line 12

… <div style="font-size:83%;min-height:3.5em"><br />

Line 12

… <a href="/?source=classic" style="margin:0">Mobile
More information

Severity: warning

A warning alerts authors on a point that may have an impact on the user experience on mobile devices and that may be worth checking. A warning does not necessarily mean that something needs to be fixed in the page. Warnings do not affect the score of the page.

Category: Rely on Web standards

In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

Best practice: STYLE_SHEETS_USE

Use style sheets to control layout and presentation, unless the device is known not to support them.

Top
Severity: ; category: ; description: The CSS Style contains at-rules, properties, or values that may not be supported ; Best Practice: STYLE SHEETS USE
Why?

Support for CSS varies from one device to the other. It is relatively safe to assume that mobile devices that support CSS support the CSS Level 1 grammar along with the @media attribute.
Where?

Triggered 20 times by the resource under test. 10 first occurrences:

Line 9 — Property position doesn't exist in CSS level 1 but exists in [css2, css21, css3]

Line 9 — Property top doesn't exist in CSS level 1 but exists in [css2, css21, css3]

Line 9 — only 0 can be a length. You must put a unit after your number

Line 9 — Property overflow-y doesn't exist in CSS level 1 but exists in [css3]

Line 9 — Property border-collapse doesn't exist in CSS level 1 but exists in [css2, css21, css3]

Line 9 — inline-box is not a display value

Line 9 — inline-block is not a display value

Line 9 — Value inherit does not exist for CSS1

Line 9 — Unknown pseudo-element or pseudo-class :hover

Line 9 — Unknown pseudo-element or pseudo-class :hover
More information

Severity: informational

An informational message is a lightweight warning that alerts authors on a point that may have an impact on the user experience on mobile devices if it is not handled with care. For instance, using scripting is not discouraged but authors should check that the page remains usable without scripting. Informational messages do not affect the score of the page.

Category: Rely on Web standards

In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

Best practice: STYLE_SHEETS_USE

Use style sheets to control layout and presentation, unless the device is known not to support them.

Top
Severity: ; category: ; description: Consider adding an inputmode attribute to this input element. ; Best Practice: DEFAULT INPUT MODE
Why?

If the expected text entry uses a well-defined subset of characters (e.g. numbers), identifying that set using the inputmode attribute of the input element can help mobile browsers uses the most adapted input mode on the device (e.g. numeric keyboard vs alphabetic).

How?

Add an inputmode attribute to the input element, with one of the well-known inputmode values.
Where?

Triggered by the resource under test:

Line 12

… <input autocomplete="off" class="lst" maxlength="2048" name="q" size="57" style="color:#000;margin:0;padding:5px 8px 0 6px;vertical-align:top" title="Google Search" value="" />
More information

Severity: informational

An informational message is a lightweight warning that alerts authors on a point that may have an impact on the user experience on mobile devices if it is not handled with care. For instance, using scripting is not discouraged but authors should check that the page remains usable without scripting. Informational messages do not affect the score of the page.

Category: Help and guide user input

Keyboards and other input methods on mobile devices can be tedious to use, so effective designs minimize the need for them.

Best practice: DEFAULT_INPUT_MODE

Specify a default text entry mode, language and/or input format, if the device is known to support it.

Top
Severity: ; category: ; description: Consider adding an inputmode attribute to this textarea element. ; Best Practice: DEFAULT INPUT MODE
Why?

If the expected text entry uses a well-defined subset of characters (e.g. numbers), identifying that set using the inputmode attribute of the textarea element can help mobile browsers uses the most adapted input mode on the device (e.g. numeric keyboard vs alphabetic).

How?

Add an inputmode attribute to the textarea element, with one of the well-known inputmode values.
Where?

Triggered by the resource under test:

Line 12

… <textarea id="csi" style="display:none" />
More information

Severity: informational

An informational message is a lightweight warning that alerts authors on a point that may have an impact on the user experience on mobile devices if it is not handled with care. For instance, using scripting is not discouraged but authors should check that the page remains usable without scripting. Informational messages do not affect the score of the page.

Category: Help and guide user input

Keyboards and other input methods on mobile devices can be tedious to use, so effective designs minimize the need for them.

Best practice: DEFAULT_INPUT_MODE

Specify a default text entry mode, language and/or input format, if the device is known to support it.

Top

The W3C mobileOK Checker follows the W3C mobileOK Basic Tests 1.0 standard and uses specific HTTP headers to retrieve resources as if it were a mobile device. As a result, tests may not be run against the content one may see when the resource is viewed on a regular desktop browser.

Source listing of the resource under test
1. <!doctype html><html itemscope="itemscope" itemtype="http://schema.org/WebPage"><head><meta content="Search the world's information, including webpages, images, videos and more. Google has many special features to help you find exactly what you're looking for." name="description"><meta content="noodp" name="robots"><meta itemprop="image" content="/images/google_favicon_128.png"><title>Google</title><script>(function(){
2. window.google={kEI:"GcufUYTvO4Xe8wS5rYDoBg",getEI:function(a){for(var b;a&&(!a.getAttribute||!(b=a.getAttribute("eid")));)a=a.parentNode;return b||google.kEI},https:function(){return"https:"==window.location.protocol},kEXPI:"17259,140438,4000116,4001350,4001948,4002463,4002855,4003242,4003714,4003881,4003921,4004320,4004334,4004702,4004788,4004844,4004949,4004972,4005031,4005155,4005198,4005318,4005335,4005874,4006192,4006374,4006426,4006442,4006541,4006578,4006609,4006727,4006806,4007007,4007009,4007020,4007055,4007060,4007077,4007080,4007117,4007118,4007140,4007158,4007217,4007335",kCSI:{e:"17259,140438,4000116,4001350,4001948,4002463,4002855,4003242,4003714,4003881,4003921,4004320,4004334,4004702,4004788,4004844,4004949,4004972,4005031,4005155,4005198,4005318,4005335,4005874,4006192,4006374,4006426,4006442,4006541,4006578,4006609,4006727,4006806,4007007,4007009,4007020,4007055,4007060,4007077,4007080,4007117,4007118,4007140,4007158,4007217,4007335",ei:"GcufUYTvO4Xe8wS5rYDoBg"},authuser:0,ml:function(){},kHL:"en",time:function(){return(new Date).getTime()},log:function(a,b,c,h){var d=new Image,f=google.lc,e=google.li,g="";d.onerror=d.onload=
3. d.onabort=function(){delete f[e]};f[e]=d;!c&&-1==b.search("&ei=")&&(g="&ei="+google.getEI(h));c=c||"/gen_204?atyp=i&ct="+a+"&cad="+b+g+"&zx="+google.time();a=/^http:/i;
4. a.test(c)&&google.https()?(google.ml(Error("GLMM"),!1,{src:c}),delete f[e]):(d.src=c,google.li=e+1)},lc:[],li:0,Toolbelt:{},y:{},x:function(a,b){google.y[a.id]=[a,b];return!1},load:function(a,b){google.x({id:a+k++},function(){google.load(a,b)})}};var k=0;})();
5. (function(){var d=!1;google.sn="webhp";google.timers={};google.startTick=function(a,b){google.timers[a]={t:{start:google.time()},bfr:!!b}};google.tick=function(a,b,h){google.timers[a]||google.startTick(a);google.timers[a].t[b]=h||google.time()};google.startTick("load",!0);
6. try{}catch(e){}})();
7. var _gjwl=location;function _gjuc(){var a=_gjwl.href.indexOf("#");if(0<=a&&(a=_gjwl.href.substring(a),0<a.indexOf("&q=")||0<=a.indexOf("#q=")))if(a=a.substring(1),-1==a.indexOf("#")){for(var d=0;d<a.length;){var b=d;"&"==a.charAt(b)&&++b;var c=a.indexOf("&",b);-1==c&&(c=a.length);b=a.substring(b,c);if(0==b.indexOf("fp="))a=a.substring(0,d)+a.substring(c,a.length),c=d;else if("cad=h"==b)return 0;d=c}_gjwl.href="/search?"+a+"&cad=h";return 1}return 0}
8. function _gjp(){(!window._gjwl.hash||!window._gjuc())&&setTimeout(_gjp,500)};
9. window._gjp&&_gjp();</script><style>#gbar,#guser{font-size:13px;padding-top:1px !important;}#gbar{height:22px}#guser{padding-bottom:7px !important;text-align:right}.gbh,.gbd{border-top:1px solid #c9d7f1;font-size:1px}.gbh{height:0;position:absolute;top:24px;width:100%}@media all{.gb1{height:22;margin-right:.5em;vertical-align:top}#gbar{float:left}}a.gb1,a.gb4{text-decoration:underline !important}a.gb1,a.gb4{color:#00c !important}.gbi .gb4{color:#dd8e27 !important}.gbf .gb4{color:#900 !important}</style><style>.h{font-family:arial,sans-serif}body{font-family:arial,sans-serif}td{font-family:arial,sans-serif}a{font-family:arial,sans-serif}p{font-family:arial,sans-serif}body{margin:0;overflow-y:scroll}#gog{padding:3px 8px 0}.h{color:#36c}.q{color:#00c}.ts{border-collapse:collapse}td{line-height:.8em}.gac_m td{line-height:17px}form{margin-bottom:20px}.ts td{padding:0}em{font-weight:bold;font-style:normal}.lst{height:25px;width:496px;font:18px arial,sans-serif}.gsfi{font:18px arial,sans-serif}.gsfs{font:17px arial,sans-serif}.ds{display:inline-box;display: inline-block;margin:3px 0 4px;margin-left:4px}input{font-family:inherit}body{background:#fff;color:black}a.gb1{color:#11c !important}a.gb2{color:#11c !important}a.gb3{color:#11c !important}a.gb4{color:#11c !important}.sblc{padding-top:5px}.lsbb{background:#eee;border:solid 1px;border-color:#ccc #999 #999 #ccc;height:30px}a{color:#11c;text-decoration:none}a:hover{text-decoration:underline}a:active{text-decoration:underline}.fl a{color:#36c}a:visited{color:#551a8b}a.gb1{text-decoration:underline}a.gb4{text-decoration:underline}a.gb3:hover{text-decoration:none}.sblc a{display:block;margin:2px 0;margin-left:13px;font-size:11px}#ghead a.gb2:hover{color:#fff !important}.lsbb{display:block}.ftl{display:inline-block;margin:0 12px}.lsb{background:url(/images/srpr/nav_logo80.png) 0 -258px repeat-x;border:none;color:#000;cursor:pointer;height:30px;margin:0;outline:0;font:15px arial,sans-serif;vertical-align:top}#fll a{display:inline-block;margin:0 12px}.lsb:active{background:#ccc}.lst:focus{outline:none}#addlang a{padding:0 3px}</style><script></script> </head><body bgcolor="#fff"><script>(function(){var src='/images/srpr/nav_logo80.png';var iesg=false;document.body.onload = function(){window.n && window.n();if (document.images){new Image().src=src;}
10. if (!iesg){document.f&&document.f.q.focus();document.gbqf&&document.gbqf.q.focus();}
11. }
12. })();</script><textarea id="csi" style="display:none"></textarea><div id="mngb"><div id=gbar><nobr><b class=gb1>Search</b> <a class=gb1 href="http://www.google.com/imghp?hl=en&tab=wi">Images</a> <a class=gb1 href="http://maps.google.com/maps?hl=en&tab=wl">Maps</a> <a class=gb1 href="https://play.google.com/?hl=en&tab=w8">Play</a> <a class=gb1 href="http://www.youtube.com/?tab=w1">YouTube</a> <a class=gb1 href="http://news.google.com/nwshp?hl=en&tab=wn">News</a> <a class=gb1 href="https://mail.google.com/mail/?tab=wm">Gmail</a> <a class=gb1 href="https://drive.google.com/?tab=wo">Drive</a> <a class=gb1 style="text-decoration:none" href="http://www.google.com/intl/en/options/"><u>More</u> »</a></nobr></div><div id=guser width=100%><nobr><span id=gbn class=gbi></span><span id=gbf class=gbf></span><span id=gbe></span><a href="http://www.google.com/history/optout?hl=en" class=gb4>Web History</a> | <a href="/preferences?hl=en" class=gb4>Settings</a> | <a target=_top id=gb_70 href="https://accounts.google.com/ServiceLogin?hl=en&continue=http://www.google.com/" class=gb4>Sign in</a></nobr></div><div class=gbh style=left:0></div><div class=gbh style=right:0></div></div><center><br clear="all" id="lgpd"><div id="lga"><img alt="Google" height="95" src="/intl/en_ALL/images/srpr/logo1w.png" width="275" id="hplogo" onload="window.lol&&lol()" style="padding:28px 0 14px"><br><br></div><form action="/search" name="f"><table cellpadding="0" cellspacing="0"><tr valign="top"><td width="25%"> </td><td align="center" nowrap="nowrap"><input name="ie" value="ISO-8859-1" type="hidden"><input value="en" name="hl" type="hidden"><input name="source" type="hidden" value="hp"><div class="ds" style="height:32px;margin:4px 0"><input autocomplete="off" class="lst" value="" title="Google Search" maxlength="2048" name="q" size="57" style="color:#000;margin:0;padding:5px 8px 0 6px;vertical-align:top"></div><br style="line-height:0"><span class="ds"><span class="lsbb"><input class="lsb" value="Google Search" name="btnG" type="submit"></span></span><span class="ds"><span class="lsbb"><input class="lsb" value="I'm Feeling Lucky" name="btnI" type="submit" onclick="if(this.form.q.value)this.checked=1; else top.location='/doodles/'"></span></span></td><td class="fl sblc" align="left" nowrap="nowrap" width="25%"><a href="/advanced_search?hl=en&authuser=0">Advanced search</a><a href="/language_tools?hl=en&authuser=0">Language tools</a></td></tr></table><input type="hidden" id="gbv" name="gbv" value="1"></form><div id="gac_scont"></div><div style="font-size:83%;min-height:3.5em"><br></div><span id="footer"><p><span>View Google in:</span> <a href="/?source=classic" style="margin:0">Mobile</a> | <strong>Classic</strong></p><div style="font-size:10pt"><div id="fll" style="margin:19px auto;text-align:center"><a href="/intl/en/ads/">Advertising Programs</a><a href="/services/">Business Solutions</a><a href="https://plus.google.com/116899029375914044550" rel="publisher">+Google</a><a href="/intl/en/about.html">About Google</a></div></div><p style="color:#767676;font-size:8pt">© 2013 - <a href="/intl/en/policies/">Privacy & Terms</a></p></span></center><div id=xjsd></div><div id=xjsi><script>if(google.y)google.y.first=[];(function(){function b(a){window.setTimeout(function(){var c=document.createElement("script");c.src=a;document.getElementById("xjsd").appendChild(c)},0)}google.dljp=function(a){google.xjsi||(google.xjsu=a,b(a))};google.dlj=b;})();
13. if(!google.xjs){window._=window._||{};window._._DumpException=function(e){throw e};if(google.timers&&google.timers.load.t){google.timers.load.t.xjsls=new Date().getTime();}google.dljp('/xjs/_/js/k\x3dzdjq4QYQllA.en_US./m\x3dsb_he,pcc/rt\x3dj/d\x3d1/sv\x3d1/rs\x3dAItRSTMVdlNFCZI4zrhWO7iqMZCDTe3_jw');google.xjs=1;}google.pmc={"sb":{"agen":true,"cgen":true,"client":"heirloom-hp","dh":true,"ds":"","eqch":true,"fl":true,"host":"google.com","jsonp":true,"msgs":{"lcky":"I\u0026#39;m Feeling Lucky","lml":"Learn more","oskt":"Input tools","psrc":"This search was removed from your \u003Ca href=\"/history\"\u003EWeb History\u003C/a\u003E","psrl":"Remove","sbit":"Search by image","srch":"Google Search"},"ovr":{"l":1,"ms":1},"pq":"","qcpw":false,"scd":10,"sce":5,"stok":"48RBF7GejV3UK3csrrnnYf0tUME"},"hp":{},"pcc":{}};google.y.first.push(function(){if(google.med){google.med('init');google.initHistory();google.med('history');}google.History&&google.History.initialize('/');google.hs&&google.hs.init&&google.hs.init()});if(google.j&&google.j.en&&google.j.xi){window.setTimeout(google.j.xi,0);}</script></div><script>(function(){var b,c,d,e;function g(a,f){a.removeEventListener?(a.removeEventListener("load",f,!1),a.removeEventListener("error",f,!1)):(a.detachEvent("onload",f),a.detachEvent("onerror",f))}function h(a){e=(new Date).getTime();++c;a=a||window.event;a=a.target||a.srcElement;g(a,h)}var k=document.getElementsByTagName("img");b=k.length;
14. for(var l=c=0,m;l<b;++l)m=k[l],m.complete||"string"!=typeof m.src||!m.src?++c:m.addEventListener?(m.addEventListener("load",h,!1),m.addEventListener("error",h,!1)):(m.attachEvent("onload",h),m.attachEvent("onerror",h));d=b-c;
15. function n(){if(google.timers.load.t){google.timers.load.t.ol=(new Date).getTime();google.timers.load.t.iml=e;google.kCSI.imc=c;google.kCSI.imn=b;google.kCSI.imp=d;void 0!==google.stt&&(google.kCSI.stt=google.stt);google.csiReport&&google.csiReport()}}window.addEventListener?window.addEventListener("load",n,!1):window.attachEvent&&window.attachEvent("onload",n);google.timers.load.t.prt=e=(new Date).getTime();})();
16. </script></body></html>

Top

W3C Mobile Web Initiative sponsored by MobiWeb 2.0 FP7 EU project

Validators donation program

This is the W3C mobileOK Checker v1.4.2
This work is part of the MobiWeb 2.0 project supported by the European Union's 7th Research Framework Programme (FP7).
The checker is based on the open source mobileOK checker library developed by the Mobile Web Best Practices working group.

Copyright © 1994-2010 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.

W3C mobileOK Checker

Report summary

Address: http://www.google.com/

Result: 69%

Failures per severity

Failures per category

Page Size: 52.5KB

Network usage: 3 requests

Detailed report

Source listing

Navigation menu