accesskey _ mod _ content

Use of HTML 5

Yes, it is possible to use a web HTML5 and that this continues to be accessible. This will include those features of HTML5 que are widely supported in the present time. It is possible to use advanced features and less supported provided it does not depend on them. That is, as long as you may access the page with a browser without support and do not miss important content or functionality.

For example, it can use the new types of INPUT to take advantage of the automatic validation in your browser or the widget (interface) shown in certain areas. However, in browsers without interpreting support such fields as normal text fields must be possible to use the form without losing content or basic functionality. For example, the validation of the fields can be duplicated in the server.

HTML5 elements H1 to H6 sections represent headers. There are No differences on earlier versions of HTML. The led H1 is the highest-ranking and header H6 the.

As in HTML 4, the elements H1 - H6 create new content sections implicitly. From these sections are form the outline or map contents of the page that reflects its structure.

The sections of a page you can create implicitly through the elements of previous header or explicitly through elements of HTML5 content section ( SECTION, ARTICLE, ASIDE, NAV ). These sections also used to define the outline or map contents.

As a novelty in HTML 5, the first headed a section with some of these elements can be level H1, regardless of the level of the last headed used earlier. This facilitates the contribution of contents of third parties, or the inclusion of content by managers of content, because there is no need to worry of headed nesting provided that such contents are included within a section created specifically for some of these elements ( SECTION, ARTICLE, ASIDE, NAV ).

In the HTML5 specification. (Opens in new window) available detailed information on the use of headings, sections and generation of the outline of the document.

Allows you to include HTML5, audio and video natively without having to rely on external plugins, through the new elements VIDEO and AUDIO respectively.

However, not all browsers support codecs the same video, audio and there is no universal standard format, so that it is now necessary to provide several versions of multimedia file in different formats. For this you must use the element SOURCE within the elements VIDEO and AUDIO to specify each alternative. Moreover, to provide subtitles you can use the WebVTT format and the element TRACK also within the elements of VIDEO and AUDIO .

As HTML5 is not yet completely supported on all browsers, it was necessary to use any HTML5 que player support elements VIDEO, AUDIO and TRACK feature in those browsers that do not have native support JavaScript, usually through, for example, MediaElement.js (Opens in new window) . On the web page VideoSWS (Opens in new window) you can find a comparative analysis of video players to Feature.

In any case, to ensure that users can access the multimedia content, it is recommended to provide a link to download the video or audio.

For more information on the multimedia content in HTML 5, see specification of HTML 5 (currently in status of Candidate Recommendation) or the “ accessibility guide for Multimedia Content ” available in the section in the area of documentation.

If, it is possible. Despite the current support of the new elements in the form of HTML5 is still limited, it is possible to use these elements in a browser-compatible without support.

The browsers that do not support the new types of INPUT the construed and displayed as items of type text ( INPUT type text ) Will be lost new HTML5 features as the automatic validation, but always be carried out through JavaScript or through validation in the server, as if they serve HTML4 forms.

Other elements, such as PROGRESS or METER, to provide alternative content in text form showing the browsers that do not carry.

Browsers without they act as support so far with HTML4 forms, while modern browsers will take advantage of the advantages of the new features of the forms feature.

Optionally, and while HTML5 is not widely supported, it could be used any JavaScript library (e.g. Modernizr ) which are based on the detection of the characteristics of HTML 5, and in using alternatives to equivalent browsers that do not support.

The metadata required to be included along all documents of portals are: TITLE, description, keywords and encoding .

The element TITLE to be uniquely identify each document, indicating the name of the website and the name of the current page “ [name of the website], [the current page] ”.

The metadata keywords should include a list of keywords to summarize the content of the document or section to which it belongs.

The metadata description should include a general description of the contents of the section in which the document is found, though it is recommended that this description could be at the page.

The metadata encoding should include the character encoding of documents.