XHTML Basic 1.1, a mobile web markup language recommended by W3C

XHTML Basic 1.1, a mobile web markup language recommended by W3C

W3C recently released two standards, namely " XHTML Basic1.1 " and " Mobile Web Best Practices 1.0 ". Both standards are targeted at the mobile Web, with XHTML Basic 1.1 being the W3C's recommended markup language for the mobile Web.
XHTML Basic 1.1
There are many branches of mobile markup language. The release of XHTML Basic 1.1 provides a standard for mobile markup language. XHTML Basic 1.1 includes the following new features:
    Added XHTML form. Added built-in event. Added value attribute to li object. Added target attribute. Added style object. Added style attribute. Added XHTML display module. Added inputmode attribute.

W3C summarizes 10 basic rules from " Mobile Web Best Practices" :
Design web pages consistently for multiple devices. When designing mobile web pages, various devices must be taken into consideration to reduce costs and increase flexibility.
    Rely on Web Standards: In a market with a variety of devices, Web standards can ensure compatibility between different devices. Avoid some common problems with mobile devices: for example, no pop-up windows, no nested tables, and no Frames. Be aware of the limitations of mobile devices: Mobile devices generally do not support technologies such as Cookies and Javascript. Optimize navigation: Use a clear, concise, and minimal navigation system. Check graphics and colors: Don’t use high-resolution images. Check graphics based on the likely screen size, resolution, and supported colors and contrast of the mobile device to make sure they display properly. Small: Page display size, file size, and CSS size should be as small as possible. Save bandwidth: Do not use automatic refresh, redirection and other techniques. Don't reference external resources too much and make good use of page cache. Make input convenient for users: The input method of mobile devices is not easy to use, so provide convenient assistance for user input as much as possible. Consider busy users: Busy users have limited time, so the information provided by mobile Web should be concise and clear.
You can verify your mobile Web at mobileOK checker to test whether it is mobile device friendly.
International sources of this article:
http://www.cmswire.com/cms/web-publishing/xhtml-11-released-mobile-best-practices-proclaimed-002984.php;
http://www.w3.org/2007/02/mwbp_flip_cards

<<:  Detailed explanation of docker version es, milvus, minio startup commands

>>:  Implementation of a simplified version of JSON.stringify and its six major features explained in detail

Recommend

Solution to the problem of null column in NOT IN filling pit in MySQL

Some time ago, when I was working on a small func...

Detailed example code of mysql batch insert loop

background A few days ago, when I was doing pagin...

Detailed explanation of keepAlive usage in Vue front-end development

Table of contents Preface keep-avlive hook functi...

Manjaro installation CUDA implementation tutorial analysis

At the end of last year, I replaced the opensuse ...

Summary of things to pay attention to in the footer of a web page

Lots of links You’ve no doubt seen a lot of sites ...

Future-oriented all-round web design: progressive enhancement

<br />Original: Understanding Progressive En...

Does MySql need to commit?

Whether MySQL needs to commit when performing ope...

Vue uses the video tag to implement video playback

This article shares the specific code of Vue usin...

How to optimize a website to increase access speed update

Recently, the company has begun to evaluate all s...

Examples of using Docker and Docker-Compose

Docker is an open source container engine that he...