The Acid test is a test web page of the WaSP (Web standard Project) to the examination of Internetbrowsern and HTML editors on conformity for the standard of the W3C.

Principal reason for the development of this test was the increasing lack of support of the W3C-Standards by the different manufacturers, which finally led to higher costs with the development of web pages or which user of alternative Browsern the representation of the web pages made more difficult, made partially even impossible. Although some prominent manufacturers faced the unjustified demand of the WaSP first sceptically, gradually a back meditation takes place since the year 2000.

The original Acid test originates from the year 1997 and meanwhile by the current version Acid2 was replaced.

Task of the test is the statement of representation and Render errors by web pages. The test uses the principles of HTML, mainly however CSS abilities was tested, there these at present the development (April 2005) by most Browsern supported only insufficiently. The main intention is it here to emphasize the problems with the Browser which does not exist the test. All Browser, whose HTML and CSS implementations are compatible to the specifications of the W3C, should not have difficulties during the representation.

The Browser existed the test, if it is able to indicate a smiley face error free. When the test was published, there was however still no Browser, which could represent the web page correctly. Only since December 2005 there are some implementations, which exist the test.

• Safari starting from version 2.0.2 (was contained in the update to Mac OS X 10.4.3) (first, which could represent the side correctly)
• Konqueror, in KDE 3,5 (safari and Konqueror come of to the same base of code, KHTML, which became corrections to safari for the Konqueror reused)
• iCab, starting from version iCab 3.0.
• Prince XML, a XML after PDF converter of YesLogic
• Opera exists the test since a test version for the final version 9.0 from March 2006.

Although the Internet Explorer works meanwhile even on better CSS compatibility, the developer Microsoft has admits given that the correct representation of Acid2 will not be their principal purpose and that also the next version, will not exist Internet Explorer 7, the test.

The programmers von Mozilla make progress likewise gradual, what concerns the support of the Acid2-Tests, but it is not clear yet, when the Browser really exists the test - at the earliest in Firefox 3,0, since the same Rendering engine uses 2,0 as 1,5.

Related links

• The Acid2-Test
• Web operational readiness level '' of the Web standard Project ''

Articles in category "Acid2"

We found here 10 articles.

Related Websites

We found here 6 related websites.

• Acid2 - Wikipedia, the free encyclopedia
  The optimal result for Acid2. Note that in the real test, the nose will ... The Acid2 test should render correctly on any browser that follows the W3C HTML ...


• Acid2 Browser Test - The Web Standards Project
  The Web Standards Project is a grassroots coalition fighting for standards which ensure simple, affordable access to web technologies for all.


• Acid2: The Guided Tour - The Web Standards Project
  The Web Standards Project is a grassroots coalition fighting for standards which ensure simple, affordable access to web technologies for all.


• Surfin' Safari
  KHTML developers respond to my posting of the WebCore Acid2 patches here and ... The Acid2 test has been updated to version 1.1 in order to fix the bug I ...


• The Acid2 challenge to Microsoft | Perspectives | CNET News.com
  The Acid2 challenge to Microsoft | Opera Software CTO Hakon Wium Lie throws down the gauntlet--but will Microsoft pick it up | March 16, 2005, 4:00 AM PT ...


• The Second Acid Test
  Standards compliant Take The Acid2 Test and compare it to the reference rendering. Hello World! ERROR.