Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 886227
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T13:02:03+00:00 2026-05-15T13:02:03+00:00

I was wondering if it it too early to use HTML5 for a production

  • 0

I was wondering if it it too early to use HTML5 for a production site. Should I rather wait 6-12 months until users have updated to compatible html5 browsers?
This leads me to, how far back does the browsers support HTML5?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T13:02:03+00:00Added an answer on May 15, 2026 at 1:02 pm

    http://caniuse.com/ has an excellent overview of which features are available, on which browsers – and information on available Javascript/Flash workarounds.

    http://www.modernizr.com/ is an excellent library to detect which features are supported on the client browser.

    As for HTML5 itself, the term has become a portmanteau for a lot of specifications – new markup, CSS3, canvas…

    You have to ask yourself the right questions:

    • Who are you making this site for?
      • What kind of IE6 support does your client want? In particular, can you make a site that will have some more features on “non-IE6 browsers”, at the cost of nearly no development time?
    • What features do you want to use?
      • Some features bring semantic sugar but are not really worth the hassle – even when “supported”. (<article>, <date>…)
      • Some features bring (mostly) eye-candy, but absence of support won’t usually break your site. (CSS3 corners, HTML5 forms)
      • Some features can become the cornerstone of your site (<canvas>, <video>), especially if you want your site to be accessible from smartphones. (Even with Android getting Flash, I suspect many users won’t activate it if not forced in order to spare battery life)
    • What features can you afford to use?
      • Some features degrade extremely gracefully – that is, you don’t have any work to do when the browser offers no support, and people with non-supporting browsers won’t even notice that they are missing on something (HTML5 forms)
      • Most useful features have relatively widespread workarounds for non-supporting browsers (mostly IE), generally implemented in Javascript or Flash. (HTML5 stylable markup, CSS3 corners, <video>, <canvas>) – but it will come at a price in site performance and design time.

    Short answer: As a hobbyist web designer (so don’t take that advice as more than a barely informed piece of opinion), I do not think it is too early – if your website needs to be accessible on the iPhone and iPad, it will need HTML5 for some features. If your website needs to be accessible from people who are on IE6, then of course the set of available HTML5 functionality is quite limited (Heck IE6 barely supports CSS2.1) – but the most important bits (<video>, <canvas>) have workarounds available.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Just wondering... I find using escape characters too distracting. I'd rather do something like
Just wondering if it is too early to migrate to .net fw beta 2.
Im just wondering if I am pushing JSON too far? and if anyone has
I'm just wondering if anyone has had any problems having too many subscribers for
After a quick Google I couldn’t find anything too promising so I was wondering
Wondering if someone could help me. I have next to no knowledge with Ajax,
I'm sitting here wondering wheather this php contact form solution is too simple to
I'm new to Objective-C, so please don't judge me too much. I was wondering:
Just wondering why this is too strict, I can send very simplified emails to
Not too sure if I'm barking up the right tree, so I'm wondering if

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.