Web Compatibility Test for Mobile Browsers | |
Url: | www.w3.org/2008/06/mobile-test/ |
Commercial: | no |
Type: | Web standards test |
Language: | English |
Registration: | none |
Owner: | The World Wide Web Consortium |
Author: | Dominique Hazael-Massieux, Wilhelm Joys Andersen, Kai Hendry |
Launch Date: | 16 April 2008 |
Current Status: | online |
Web Compatibility Test for Mobile Browsers, often called the Mobile Acid test,[1] despite not being a true Acid test,[2] is a test page published and promoted by the World Wide Web Consortium (W3C) to expose web page rendering flaws in mobile web browsers and other applications that render HTML.[3] It was developed in the spirit of the Acid test by the Web Standards Project to test the relevant parts that a mobile browser needs to support. The browser has to accomplish 16 different subtests indicated by a 4 x 4 image of green or red squares.
A second version of the Web Compatibility Test for Mobile Browsers was released in January 2010, this time testing HTML5 elements.[4] The second test does not have an official explanation page, only a direct link to the test is available.
The mobile Acid test tests a variety of web standards published by the World Wide Web Consortium and the Internet Engineering Task Force.Specifically, the mobile Acid test tests:[5]
The second version of the test tests the following elements:[6]
A green square indicates that the browser fully supports its assigned feature. A square colored red or a different color indicates that the feature is not fully supported.[7] The second test shows a percentage bar indicating the percent of elements supported.
Due to the wide variety of web engines used at the time for mobile browsers, results varied between browsers used.[8] Safari on iOS 3 received a 15/16 score on the first test and the Palm Pre web browser scored a 13/16 in revision 1.47 of the first test.[9] In 2010, Firefox Mobile for Android scored a 75% while Safari scored a 67%. By 2012, versions of Chrome, Safari, and Firefox had scores of 80% or over on the second test. The most common failure on the second test was , with a 61.45% failure rate.[10]