'''Web interoperability''' is producing web pages viewable with nearly every device and [[web browser]]. There have been various projects to improve web interoperability, for example the [[Web Standards Project]], Mozilla's Technology Evangelism<ref>{{cite web |url=https://www.mozilla.org/projects/tech-evangelism/ |title=Mobile/Evangelism - MozillaWiki |author= |date= |publisher= |accessdate=12 August 2016}}</ref> and Web Standards Group,<ref>{{cite web |url=http://webstandardsgroup.org/ |title=Web Standards Group (WSG)|author= |date= |publisher= |accessdate=12 August 2016}}</ref> and the Web Essential Conference.
==History==
The term was first used in the Web Interoperability Pledge,<ref>{{cite web |url=http://www.w3.org/Promotion/WIP/|title=WIP -- Web Interoperability Pledge|author=|date=|publisher= |accessdate=12 August 2016}}</ref> which is a promise to adhere to current [[HTML]] recommendations as promoted by the [[World Wide Web Consortium]] (W3C).<ref>{{Cite web |title=Understanding Website Usability and Conversions |url=https://www.netpaths.net/understanding-website-usability-conversions/ |access-date=2024-03-25 |language=en-US}}</ref> The WIP was not a W3C initiative. but it was started by and has been run by [[ZDNet]] AnchorDesk.
This issue was known as "cross browsing" in the [[Browser wars|browser war]] between [[Internet Explorer]] and [[Netscape]]. Microsoft's Internet Explorer was the dominant browser after that, but modern web browsers such as [[Mozilla Firefox]], [[Opera (web browser)|Opera]] and [[Safari (web browser)|Safari]] have become dominant, and support additional web standards beyond what Internet Explorer supports.<ref>{{Cite web |title=RubyWhat Onare Railsthe Characteristics of a Good DevelopmentWebsite? |url=https://www.trafficrunnershatchandvox.com/servicesweb-design/rubycharacteristics-onof-railsgood-developmentwebsite/ |access-date=20232024-0406-2722 |language=en-GB}}</ref> Because of Internet Explorer's [[backward compatibility|backwards compatibility]], some web pages have continued to use non-standard HTML tags, DOM handling scripts, and platform-specific technologies such as [[ActiveX]], which could potentially be harmful for [[Web accessibility]] and [[device independence]].
