Hot answers tagged html5
37
I agree that your decision obviously should reflect the business realities and audience of your particular website.
That said, large companies officially dropping support for IE6 is still significant. It raises the general perception that it is finally OK to leave a 10 year old browser behind. It also adds ammunition to any case you wish to make to the ...
32
HTML5 is huge, but also awesome.
In my view, it is mostly about interoperability. The spec goes and specifies even edge cases to try and make sure that all browsers read the markup the same way.
In second place, HTML5 has video and audio, which do exactly what the name says it does. If you want to include video or audio, HTML5 should reduce your plugin ...
17
To keep track of features and specifications support you can check When can I use. It includes HTML5 and CSS3 features and things like SVG, PNG, CSS2.1 and CSS2. It also tracks their status of approval (Recommendation, Proposed Recommendation, Candidate Recommendation, Working Draft, IETF standard). FindMeByIP maintains matrices of supported CSS3 features ...
15
Give HTML5 some time to mature and gain wide acceptance and you might have some specific guidelines for SEO, but I don't think it will differ much from what's currently considered good practice. Either way, I think it's a little too early.
In general, if it's good for your users, it will be good for SEO. Make your site accessible and usable. Use a good ...
12
HTML5 is supported by all browsers now, even IE5!(if you use the html5shiv script). I highly recommend reading http://diveintohtml5.org It is one of the best HTML5 resources out there.
As for CSS3, if you do use it, make sure to use vendor predix too, on top of the regular syntax. e.g.
border-radius
-moz-border-radius
-webkit-border-radius
I believe in ...
12
The three big search engines, Google, Bing and Yahoo (and more recently, Yandex), have agreed to understand 1 single microdata vocabulary. This is Schema.org, which has examples of placement.
This formats your results as Rich Snippets, the search engine results which have pictures and fivestar ratings, etc, displayed on the search result page. While this ...
12
Assume:
JavaScript will be turned off
CSS3 will not be supported
Images will be disabled
The users connection will be slow
I know that's not what you want to hear but as web designers and developers this is the reality we face. Not only will there be users using older browsers but some of them will alter the settings on their browser to change its ...
12
Add Google Analytics to your site and track your users
The only way to find out is to collect a reasonable sample of statistics about your user base. Anything short of that is just a baseless assumption.
Fortunately, Google Analytics tracks absolutely everything about the browser, screen size, enabled capabilities, etc...
Target Internet Explorer as the ...
10
Probably.
There are parts of HTML5 that you can use right now, today. Forms for example. If you have <input type="email"> in a browser that doesn't support HTML5 (yes, even IE6) you will simply see the same thing you'd see if you used <input type="text">. Yet on a browser that supports HTML5 form elements, you gain the advantages of the email ...
10
According to Matt Cutts, Google doesn't penalize sites just for having multiple H1 tags. It's possible that their indexers may be programmed to detect egregious overuse of H1 — like, say, having all your text inside H1 tags — and to penalize such pages, but I've seen no direct confirmation of that. It is very likely that their human staff, if ...
9
To speculate (because I think that's all you can do on this question without rigorous testing in an essentially uncontrollable environment) I personally doubt that there are yet ANY ranking factors associated with HTML5, for the same reason that Google doesn't assign quality points for valid HTML. There aren't enough sites using these structured elements ...
8
According to the HTML5 spec, "nav" is a "section" and a section "is content that defines the scope of headings and footers." The W3C example for the nav section shows h tags in the the nav.
http://www.w3.org/TR/html5/sections.html#the-nav-element
8
To answer your question: yes, your current DTD is fine.
But it's also the wrong question. Standards don't work like this.
It's not about making sure you're always using the latest one, and they don't really "expire" in the way that your question seems to suggest. They're about picking one and following its rules.
Even if your site were using HTML 4 and ...
8
Google doesn't favour HTML5 over HTML4 per se. However, HTML5 does allow more semantic mark-up, which will make it easier for Google to figure out what's what on any given page. This allows Google to be more precise when it comes to ranking what is and what isn't important on a page.
For example, the nav element indicates very clearly to Google (or any ...
7
Modernizr is used to check the availability of HTML5 features in different rendering engines. It includes a script like Html5Shiv, which (only) enables HTML5 tags on Microsoft Internet Explorer (prior to version 9, which knew HTML5). See also "How to get HTML5 working in IE and Firefox 2".
If you just want to enable HTML5 for IE < 9, then Html5Shiv would ...
7
I am a product manager about to spend 40 MD supporting IE6 for a single customer. We sell software into call centers, an unfortunately IE6 is the default platform for many big organizations.
My point is it depends, if I was building consumer web software I would have been off IE6 a long time ago, but as long as we have clients using IE6 we have to support ...
7
It's generally accepted best practice to have only a single H1 on a page, or only 1 H1 in a section for HTML 5. Google will not penalise you for meeting the HTML standards, nor will it penalize you for having multiple H1's - it may penalise you for having ONLY H1's though.
The important point is that it's about the requirements of the content and the ...
6
It's wise to use autofocus with a JavaScript fallback for browsers that don't support it. From Mark Pilgrim's Dive into HTML5 Forms:
What’s that? You say you want your
autofocus fields to work in all
browsers, not just these fancy-pants
HTML5 browsers? You can keep your
current autofocus script. Just make
two small changes:
Add the ...
6
According to HTML5 Reference, xmlns is relevant for XHTML but not for html5.
DOCTYPE is cas insensitive :
In HTML, the DOCTYPE is case insensitive, except for the quoted string "about:legacy-compat", which must be written in lower case.
6
Make sure that at the very least your home page works fine on every environment you can reasonably support. If specific pages require technologies not widely supported, state it clearly in the links that lead to them (don't need to use anything obnoxious, title and alt texts on links and images might suffice) and in the pages themselves (for instance, adding ...
6
[What specifically happens as far as search engines' interpretations of these things is always going to be up for speculation. But:]
The text might be seen as slightly less important. Remember, though, that it's still within an H* tag, so we'd be talking slightly less starting from that context. That would be correct as it's intended to represent "fine ...
5
You want to use <article> for Blog posts. Mark Pilgrim has a really good explanation of how to use each tag. He also explains how to mark-up the article just below the list of definitions on his site. This is a fantastic book for learning HTML 5 and CSS.
"The article element represents a component of a page that consists of a self-contained ...
5
Use whatever technology suits your needs most.
Eric Meyer wrote a nice article about why starting to use vendor-specific prefixes on CSS rules isn't lame like using css filter hacks used to be.
I think the same applies to HTML5. If you can check browser support for different features, why not use it. So long as the site degrades gracefully, live it up.
5
WAV files are pretty large in size. Especially when compared to mp3s which are ~90% smaller in size. Ogg Vorbis should also be much smaller. Naturally the smaller file size is ideal for the web. Unfortunately support for different formats is varied amongst browsers.
Fortunately you can work around this by specifying multiple files and letting the browser ...
5
If you need to jump users to in-page links, you can set the id attribute (which is used for more than just in-page links) on any element. Then use the usual # in the URL of a href attribute of an a element. Here's an example:
<body>
<p>Despite the many
<a href="#gum-benefits">benefits</a>
you may experience while ...
5
Typically, in the root directory of your application, you'll have 3 files:
index.html (<html manifest="app.manifest">...</html>).
This can also be auto-generated with a server-side language such as php, jsp, Ruby ...
app.manifest (CACHE MANIFEST ...)
.htaccess (AddType text/cache-manifest .manifest)
5
If you're going to allow content that isn't in a valid email address format then you'll want to use <input type="text" ...> like you said. Although someone may enter a whole email address, it isn't exclusive to that field so using <input type="email" ...> would not be appropriate.
You can also turn off form validation if you don't want the ...
5
So, is it still advisable to use html tidy just to get a "cleaner"
source code, or should I provide HTML5-Support. (I would still have to
use tidy for user-input like the description of our products).
It's possible to do both, either by configuring HTML Tidy to process HTML5 (see this question and specifically this answer) or by using another ...
5
Aptana Studio 2 does what you want in the menu Edit > Format. I've used it and it formats html, css and javascript.
The WYSIWYG editor BlueGriffon also can also format html when you open a file.
Both solutions are free and open-source, but Aptana might be better. I'm not sure if BG keeps all the code unchanged, probably not.
Notes:
Aptana 2 needs to be ...
5
rel=translation has been proposed but not adopted by the W3C (it's not in the HTML5 working document).
If the words on the pages are different then Google won't penalize you for duplicate content (several people say this in the Webmaster forums). There's lots of advice on multi-language sites in this blog post.
Only top voted, non community-wiki answers of a minimum length are eligible
