to produce and consume information about types of content for which HTML doesn't yet include nouns. The most prominent of these are WAI-ARIA, Microformats, and Schema.org.
Web crawlers understand some of these side-contracts,
This site is a resource to provide information about which HTML5 user interface features are accessibility supported in browsers, making them usable by people who rely upon assistive technology (AT) to use the web.
"Semantics is one of the most distinctive features of the Web Platform versus other application platforms. Developers usually ignore or de-prioritize such feature but the mastery of it can bring many benefits to our projects."
"There is a tool that came to make our lives as progressive web designers a bit easier: Modernizr. In this short tutorial, learn how to apply this handy script to maximum effect on your sites."
"What if someone signs up for your web app and they type in their email address as susan_smith@gmaoil.com? They don't notice, they never get their confirmation email, they never can log in again, the "forgot password" feature doesn't work, and there is a lot of frustration and finger pointing."
" elements of type number are used to let the user enter a number. They include built-in validation to reject non-numerical entries. The browser may opt to provide stepper arrows to let the user increase and decrease the value using their mouse or by simply tapping with a fingertip."
One element can also have multiple properties (multiple itemprop="" names separated by spaces) with the same value:
<p itemscope><span itemprop="guitar vocals">Chris Askew</span> is so dreamy.</p>
One element can also have multiple properties (multiple itemprop="" names separated by spaces) with the same value:
<p itemscope><span itemprop="guitar vocals">Chris Askew</span> is so dreamy.</p>
One element can also have multiple properties (multiple itemprop="" names separated by spaces) with the same value:
<p itemscope><span itemprop="guitar vocals">Chris Askew</span> is so dreamy.</p>
Once more, the iPhone recognises type="tel", only this time it goes one step further and completely changes the keyboard to the standard phone keyboard, as shown on the left in Figure 6. In addition to the iPhone, some Android devices (such as HTC Desire, shown on the right in Figure 6) also display a numeric keyboard for type="tel". That’s pretty handy, don’t you think? Nice, big keys for entering a phone number help you to get that big, nasty form completed quickly.
In contrast to Opera’s implementation, the iPhone (Figure 8) and some Android devices (such as HTC Desire, shown on the right in Figure 6-13) simply render the field as a standard text box but optimize the keyboard for easy input.
Chris’ technique may soon become absolete though with the introduction of the inputmode attribute. The attribute, recently added to the specification will allow users to specify the type of input mechanism that is most useful for users. When implemented, you will be able to choose between numeric, latin, email, or kana input modes.
To make the iPhone render with the standard telephone keypad as we saw for type="text" Chris Coyier, of CSS Tricks devised a little hoax you can use. Rather than using type=”number”, use a standard type="text" input and add a pattern attribute that accepts only numbers, as shown below. This solution isn’t ideal but if you think it could be useful, Chris has put a short video together showing it in action.
<input type="text" pattern="[0-9]*" name="shoe-size">
There are dedicated keys for the @ and . characters to help you complete the field more efficiently. As we discussed with type="search", there is no downside to using type="email" right now. If a browser doesn’t support it, it will degrade to type="text". And in some browsers, users will get a helping hand.
The url input type, as you might expect, is for web addresses. You can use the multiple attribute to enter more than one URL. Like type="email", a browser will carry out simple validation on these fields and present an error message on form submission. This is likely to include looking for forward slashes, periods, and spaces, and possibly detecting a valid top-level domain (such as .com or .co.uk). Use the url input type like so:
<input type="url" name="url" required>
"Initializr is here to kick-start the development of your new projects. It generates templates based on HTML5 Boilerplate by allowing you to choose which parts you want or don't want from it. A responsive template has also been added to start from a basic design instead of a blank page."
The solution for now is to produce your videos in multiple formats.
Table 1. Browser support by video format
Browser
MP4
WebM
Ogg
Internet Explorer 9
Yes
No
No
Firefox 4.0
No
Yes
Yes
Google Chrome 6
Yes
Yes
Yes
Apple Safari 5
Yes
No
No
Opera 10.6
No
Yes
Yes
Note: For the latest compatibility information, always check the CanIUse website.
A more robust way to create the fallback is to use a JavaScript utility like Modernizr to evaluate the browser's capabilities and then dynamically write the video and source tags or embed the Flash video player using SWFObject.
Tip 3: The source tag should always include the "type" attribute with the correct MIME type value. You may need to add an .htaccess file to your server to define the MIME types as well. Check out the Video for everybody article for more tips on MIME types.
Tip 2: The video tag includes a range of parameters that you can use to configure the video. See the Mozilla article Using HTML5 audio and video for more information.
Tip 1: The Adobe Media Encoder does not currently export video to Ogg or WebM format. You can use the Firefogg add-on for Firefox to encode video to Ogg Theora format, or you can use Miro Video Converter to encode video to WebM or Ogg Theora format.
a third option developed using lessons learned from microformats and RDFa, and designed to be integrated into HTML5 itself: microdata.
“Adding microdata” to your page is a matter of adding a few attributes to the HTML elements you already have.
So where is the real information? It’s in the <dd> element, so that’s where we need to put the itemprop attribute. Which property is it? It’s the name property. Where is the property value? It’s the text within the <dd> element. Does that need to be marked up? the HTML5 microdata data model says no, <dd> elements have no special processing, so the property value is just the text within the element.
This technique is also useful for microdata. There are two distinct pieces of information here: a title and an affiliation. If you wrap each piece in a dummy <span> element, you can declare that each <span> is a separate microdata property.
There are two major classes of applications that consume HTML, and by extension, HTML5 microdata:
Web browsers
Search engines
Google supports microdata as part of their Rich Snippets program.
a handy tool to see how Google “sees” your microdata properties
Just like associating a URL with a Person, you can associate a URL with an Organization. This could be the company’s home page, a contact page, product page, or anything else. If it’s a URL about, from, or belonging to the Organization, mark it up with an itemprop="url" attribute.
To handle edge cases like this, HTML5 provides a way to annotate invisible data. This technique should only be used as a last resort. If there is a way to display or render the data you care about, you should do so. Invisible data that only machines can read tends to “go stale” quickly. That is, someone will come along later and update the visible text but forget to update the invisible data. This happens more often than you think, and it will happen to you too.
itemscope says that this element is the enclosing element for a microdata item with its own vocabulary (given in the itemtype attribute). All the properties within this element are properties of http://data-vocabulary.org/Geo, not the surrounding http://data-vocabulary.org/Organization.
The HTML5 microdata standard includes both HTML markup (primarily for search engines) and a set of DOM functions (primarily for browsers). There’s no harm in including microdata markup in your web pages. It’s nothing more than a few well-placed attributes, and search engines that don’t understand the microdata attributes will just ignore them. But if you need to access or manipulate microdata through the DOM, you’ll need to check whether the browser supports the microdata DOM API.