HTML5 Fundamentals

The development of HTML5 was initiated by the Web Hypertext Application Technology Working Group (WHATWG) in 2004. The World Wide Web Consortium (W3C) later joined the effort to adopt and co-develop it. W3Schools and WYSIWYG editors are unrelated to its creation, making WHATWG and W3C correct.

HTML5 provides both audio and video elements for media playback. The

Although modern web browsers have exceptionally high compatibility with HTML5, none implement 100% of all HTML5 specifications, experimental features, and peripheral APIs. Therefore, the statement remains true, as full, comprehensive compliance across every detail has not been fully achieved by any single browser.

HTML5 standardizes support for three audio formats in the <audio> element: MP3, Wav, and Ogg. While AAC is supported by many modern browsers, MP3 and Wav are the officially recognized standard options listed here, whereas AIFF is not standard. Thus, MP3 and Wav are correct.

HTML5 officially supports three video formats for the <video> element: MP4 (MPEG 4 with H.264 video and AAC audio), WebM (with VP8/VP9 video and Vorbis/Opus audio), and Ogg (with Theora video and Vorbis audio). The claim that HTML5 lacks video elements is false.

HTML5 introduced Web Storage API with sessionStorage (data cleared when session ends) and localStorage (persists until deleted). Cookies are an older mechanism with size limitations, and dataStorage is not a valid HTML5 storage object.

The element in HTML5 generates a public/private key pair for secure user authentication. This allows browsers to create key pairs for certificate-based authentication without requiring plugins.

HTML5 became an official W3C Recommendation in October 2014. The statement is false because HTML5 is indeed a W3C recommendation - it completed the standardization process and is now a formal web standard.

The ondragenter event fires as soon as a dragged element enters the boundaries of a valid drop target. The ondragover event, by contrast, fires continuously while the element is being dragged over the target. Other options describe the start (ondragstart) or end (ondragend) of the drag operation.

The <canvas> element is only a container for graphics and has no drawing capabilities of its own. It requires JavaScript to access the rendering context and perform drawing operations like rendering shapes, paths, text, or images. Therefore, the statement is true.

Data stored in localStorage persists across browser sessions with no expiration time limit. It remains available until explicitly deleted by the user or the application code. This distinguishes it from sessionStorage, which expires when the page session ends, and cookies, which have configurable expiration dates.